InsightTerminal X · market & regulatory data agents

Your analysts research. The agents collect.

For portfolio managers, brokers and research desks. Agents collect SEBI portfolio-manager filings, PMS performance, ETF liquidity and index changes the moment they’re published — cleaned, versioned and exported the same way every month.

  • 4 agents on public market and regulatory sources
  • Every registered portfolio manager, every month
  • Full lineage on every record
AgentsHistoryExports
SEBIPMR portalAPMIPMS returnsNSEETF dataNIFTYIndicesAGENTSextract · cleanvalidate · versionHISTORYEXCELAPI · ALERTSmodels · dashboards
Illustrative, anonymised data. Public sources only; your own sources are added as custom agents.

WhySound familiar?

Three things we hear in every first conversation.

From research heads at portfolio managers, brokers and wealth desks. Composite quotes from discovery calls — the problems are real; the names are left out.

Terminal X: The problem, before Terminal X
The first week of the month on a research desk
  1. “Two analysts lose the first week of every month to copy-paste.”

    Every manager, eight sub-reports each, one page at a time — then cleaning the merged cells before anyone can analyse a thing.

    Head of research40+ analyst hours a month

  2. “We only track the managers we have time for.”

    The full universe is too big to collect by hand, so the competitive view is the same twenty-five names every month.

    Product & distribution headMost of the market unseen

  3. “The merge broke and nobody noticed for a month.”

    A portal renamed a column. The lookup returned blanks, the sheet still looked fine, and the model ran on it.

    Quant analystDecisions on silently bad data

HowWhat changes with Terminal X

The same three problems, on the screens that solve them.

Product screens with illustrative, anonymised data. In your walkthrough we run the agents on the sources your team uses.

01Copy-paste week

Every manager’s filing, collected in one run.

  • Parallel windows work through the whole list, with a live count of done, pending, errors and “no data filed”
  • Errors retry on their own; the export is ready when the run ends

The first week of the month back

Terminal X screen: Every manager’s filing, collected in one run.

02Partial coverage

The whole universe, ranked the way you ask.

  • Every strategy’s 1M–3Y returns, stored as numbers, with the gap to Nifty 50 or Nifty 500
  • Month-by-month history since April 2023, so trends are a filter, not a project

Every strategy, every month

Terminal X screen: The whole universe, ranked the way you ask.

03Silent breaks

Layout changes reported — never swallowed.

  • Every run logs what it collected, how long it took and what changed at the source
  • Every record keeps its source, fetch time, run and previous version

Trust the number in the export

Terminal X screen: Layout changes reported — never swallowed.

FieldTerminal X in the field

The people, the phone, the place.

The workplace it runs in, the person who uses it on a phone, the team at the desk and the detail it reads.

Terminal X: Where Terminal X runs
Where Terminal X runs
Terminal X: On the phone, where the work happens
On the phone, where the work happens
Terminal X: The team at the Terminal X desk
The team at the Terminal X desk
Terminal X: The detail Terminal X reads
The detail Terminal X reads

Photographs are illustrative — real customer sites are not shown.

  • 2,000+Page loads a monthSEBI PMR alone, now an agent’s job
  • 40+ hrsAnalyst time a monthtypical manual collection, returned
  • 8Sub-reports per managerAUM to complaints
  • Apr 2023PMS history frommonth by month, queryable
  • 0Silent failureslayout changes are reported
  • 12Screensagents · delivery · trust

01Open Terminal X

Watch a month of filings collect itself. Then export it.

Click through it. A SEBI PMR run works through every manager in parallel, PMS returns line up against the benchmark you choose, ETFs get flagged for premiums, index changes appear, and the Excel reconciles its own scheme counts.

autowhat · Terminal X / SEBI PMR · run Illustrative data

Illustrative and anonymised — managers, strategies, ETFs and constituents are labelled by code, not by name. Figures are not market data.

02Four agents

Each one replaces a job an analyst does by hand.

The sources are public. The work of collecting them is not small. Each agent runs on a schedule, stores every record with its history, and hands back the same export every time.

  • Agent 01 · Regulatory

    SEBI Portfolio Manager Monthly Report

    Every registered portfolio manager, every month: AUM by service, clients by category, inflows and outflows, turnover, transactions, schemes and complaints.

    By handClick through each manager and eight sub-reports — 2,000+ page loads. Most teams settle for 20–30 managers.
    With the agentThe full universe in one run, with a live progress panel, auto-retry and a two-sheet Excel.
  • Agent 02 · PMS intelligence

    PMS performance (APMI)

    1M to 3Y returns for every PMS strategy, discretionary and non-discretionary, against Nifty 50 or Nifty 500 — archived month by month.

    By handApply filters one at a time, wait for the table, copy row by row; each pull overwrites the last.
    With the agentAll providers and dates collected, returns normalised, gap to benchmark calculated, history kept.
  • Agent 03 · Market data

    NSE ETF liquidity

    Price, NAV, premium or discount, traded value and 52-week range for every listed ETF, archived every session.

    By handTwo downloads from two portals, a VLOOKUP on names that don’t match, and a merge that breaks when a column is renamed.
    With the agentOne session table matched by ISIN, liquidity tiers, premium flags and calendar-aligned exports.
  • Agent 04 · Index tracking

    Nifty strategy indices

    Listings and constituent files for every strategy index, with added, removed and re-weighted names tracked across runs.

    By handDownload each constituent file and compare it with last month’s by eye.
    With the agentDated snapshots and a change log per index — “what changed this week” in one screen.

03Source to spreadsheet

Eight steps. None of them copy and paste.

The same pipeline runs behind every agent — so a new source is a new agent, not a new project.

  1. 01

    Watch the source

    Schedule or new-data trigger

    Daily, after market close, monthly — or the moment a regulator publishes a new month.

  2. 02

    Open the portal

    Real browser, parallel windows

    The agent works the portal the way an analyst would: filters, dropdowns, pages, downloads.

  3. 03

    Extract everything

    All rows, all sub-reports

    Every manager, every strategy, every ETF — not the twenty an analyst has time for.

  4. 04

    Normalise

    Numbers as numbers

    “12.4%”, “(3.2)” and “--” become 12.4, −3.2 and blank. Names matched by registration number or ISIN.

  5. 05

    Validate

    Checks before storage

    Scheme counts reconciled, duplicates removed, empty filings marked as “no data”, not zero.

  6. 06

    Version

    Change detection

    Each run is compared with the last; what was added, removed or revised is kept.

  7. 07

    Store with lineage

    Source · time · run · version

    Every record knows where it came from and when — years of history, queryable.

  8. 08

    Deliver

    Excel · API · alerts

    The same export every month, a REST endpoint for your models, an alert when something moves.

04Built for research teams

Your sources too. Built to spec, in weeks.

The four agents are the standard layer. Other exchanges, regulators, company filings or your own vendor portals become custom agents in the same terminal, with the same exports, API and audit trail.

Agents · 4

  • SEBI PMR · run & progress
  • PMS performance matrix
  • ETF liquidity session
  • Strategy-index changes

Delivery · 4

  • Excel exports
  • REST API
  • Alerts on new data
  • Search & filters

Trust · 4

  • Run log
  • Record lineage
  • Schema-change detection
  • Configurable schedules
  • Auditable

    Exports match what is on screen, and every record keeps its source and time.

  • Resilient

    Errors retry, empty filings are marked, layout changes are reported.

  • Analyst-friendly

    Predictable sheets, consistent columns, numbers as numbers.

  • Your deployment

    Managed cloud, your own infrastructure, or both.

FAQQuestions we get about Terminal X

Straight answers, before the call.

Terminal X is an Autowhat AI product for research heads at portfolio managers, brokers and wealth desks. Short, factual answers for buyers, procurement and the assistants people ask first.

In short. Terminal X is an Autowhat AI product for research heads at portfolio managers, brokers and wealth desks. It is built for research heads at portfolio managers, brokers and wealth desks. It exists to remove the problems those teams describe in almost every first conversation: forty-plus analyst hours a month of copy-paste; a competitive view limited to the same twenty-five names; and models running on silently broken lookups. With Terminal X, teams get every filing collected in one run, with a live count of done, pending and errors, the whole universe ranked the way you ask, stored as numbers, and every run logged: what was collected, how long it took, what changed. It connects to Browser agents, Versioned datasets, Excel / CSV export and Change alerts, is used by Research · product · compliance, and runs on desktop cockpit. Like every Autowhat AI product, Terminal X goes live on one site, lane or process first, usually within weeks, on managed cloud, in your own VPC or on-premises, and shares one operational record with the other products, so the second deployment reuses the data and integrations of the first.

Who is Terminal X for?

Research heads at portfolio managers, brokers and wealth desks. Agents that collect regulatory filings, portfolio returns, ETF liquidity and index changes across the whole universe — cleaned, versioned and exported — and report every layout change at the source instead of swallowing it.

What problems does Terminal X remove?

forty-plus analyst hours a month of copy-paste; a competitive view limited to the same twenty-five names; models running on silently broken lookups.

What do we get with Terminal X?

every filing collected in one run, with a live count of done, pending and errors; the whole universe ranked the way you ask, stored as numbers; every run logged: what was collected, how long it took, what changed.

What does Terminal X connect to, and who uses it?

It connects to Browser agents, Versioned datasets, Excel / CSV export, Change alerts. Users: Research · product · compliance. Channel: Desktop cockpit.

How do we start with Terminal X?

With a 30-minute working session on your own data — an engineer from the relevant sector, not a sales queue. The first wave is scoped in that call; most products go live on one site, lane or process within weeks and then scale.

Where does Terminal X run, and who owns the data?

On managed cloud, in your own VPC (AWS, Azure or GCP) or on-premises, with your keys. SOC 2 Type II and ISO 27001 controls, India data residency when required, and local or open-weight models when policy demands it. The data stays yours.

05Walkthrough

Tell us which reports your team builds by hand. We’ll show you them collecting themselves.

A working session with the engineers who build it: a live SEBI PMR run, your export format, and a plan for the sources only your team uses.