Data catalogue
Find datasets, series, publications and extracts across the marketplace.
- Warehouse rows
- 6.17B
- Structured DB
- 1,711.35 GB
- Live data store
- 189.73 GB
- Data tables
- 1,03,091
- Publications & data products
- 1,749
About these figures
BigQuery reports 6,167,191,751 physical rows across 89 native base tables in 9 catalogue warehouses, measured on . Structured DB measures logical bytes across the same tables. The headline excludes 22 verified staging and backup tables with 365,935,268 rows and 57.49 GB of logical storage. Separate publisher editions can contain overlapping observations.
The earlier 40-MCP inventory reported 1,115,017,091 records across warehouses, files and upstream sources, including 811,051,329 upstream survey records from MoSPI NADA.
Live data store measures 189.73 GB of live catalogue objects across 39 Cloud Storage buckets, measured on .
UNCTAD ingestion files account for 153.97 GB of additional live storage. Retained soft-deleted objects account for 109.84 GB. Raw publisher archives and their corresponding BigQuery tables are measured in their respective storage layers.
Data tables counts 1,03,091 publisher tables held across the marketplace MCPs, measured in each MCP's own store on 2026-11-10: one table, sheet, dataflow, report section or API dataset in one edition counts once, the way data.gov.in counts resources. Raw copies, backups and archive duplicates are not counted twice. They belong to 1,749 publications and data products — six Economic Survey reports are one publication — which hold 10,664 editions, 8,62,701 series and 19,717 documents. India Intelligence and Survey chapter packs are built from these MCPs and are not added. Geo-Spatial can also reach 2,36,742 data.gov.in resources live; they are not held and not counted.
The search index includes 18,933 datasets (tables, survey studies and map layers) and 493 individually indexed series. Separate live and archived access routes can have their own entries. These figures apply across the catalogue, regardless of filters.
Insight Generation
41 results
Coverage unknown. Your data and a question in, a researched article out — patterns found by code, causes tested against the web and other MCPs, every number and claim traced.
cancel article job
Cancel an active background job, retaining data/evidence and drafts for inspection. Repeated calls return its terminal status. Interrupted jobs can be resumed stepwise.
check data artifacts
Before researching causes, rule out artifacts: base effects, seasonal repeats, reverting spikes, unit/scale jumps, near-zero bases. Defaults to kept findings.
check research evidence
Dry-run the same evidence gate as submit_research_result without changing evidence, brief status or coverage. Returns each rejection reason for repair.
compute metrics
Period-on-period and YoY change (pp for rates, % for levels), 4-period moving average, CAGR and summary for one series. `filters` picks dimension levels, e.g. {"segment": "BFSI"}.
correlate
Correlation between two series at lags 0..max_lag (a leading b). Series are selectors {table, measure, filters}. on='changes' (default) or 'levels'. Stored as a citable fact (A-id).
decompose change
What drove a change between two periods. Without `weight`: contribution of each dimension level. With `weight` (e.g. revenue when measure is a margin): mix vs rate effects. The result is stored as a citable fact (A-id).
define scope
Create the Research Charter every later stage is keyed to: core question, sub-questions SQ1..n, in/out of scope, completion rule. Pass `charter` to set or edit it directly (same shape as returned) instead of having Claude derive it from `query`. Works before any data is ingested (the Charter then comes from the question alone). create_if_missing=True creates the session under `session_id` if it do
detect patterns
Run pattern detection on some series without writing findings: unusual moves vs history, step changes beyond trend, sustained trends, inflections, outliers, mix shifts.
discover sources
Connect to registered sources, list their tools and infer capabilities. With from_registry=True, also list candidate MCP servers from INSIGHT_MCP_REGISTRY_URL (candidates are not enabled until register_source).
draft article
Write the article from the outline, using only fact-sheet numbers and cited evidence.
finish insight article
Resume after research (e.g. host-mode): explanations → coverage → outline → draft → verify → render. follow_ups=True runs server-side follow-up briefs for gaps.
generate findings
Scan every series, score patterns by materiality × surprise × recency, and store the top ones as findings F1..Fn — each with the computation that produced it.
generate insight article
End to end, in one call: ingest → findings → Charter → select → artifact checks → plan → research → explanations → coverage → outline → draft → verify (+1 revision) → render. Takes 5-10 minutes in server mode — clients with short HTTP timeouts should use start_insight_article + get_article_job instead.
get article artifact
Read draft.md, verification.json, final.md, final.html or charts/<id>.json remotely. Final artifacts are withheld when verification has become stale.
get article job
Status of a start_insight_article job: status (running | done | failed), current stage, progress 0-1, and — when done — the result with the article Markdown. Long-polls: waits up to wait_seconds (max 150) for the job to finish or change stage before answering, so an agent can simply call this again after each reply instead of sleeping. Pass wait_seconds=0 for an immediate snapshot.
get research briefs
Host-orchestrated mode: briefs with a ready-to-use sub-agent prompt, the evidence item schema and capability hints, so you can spawn your own sub-agents with your own MCPs. Return their results via submit_research_result.
get session
Session state: stages run, counts, article files, and the Charter.
ingest data
Load data and documents into a session (creating one unless session_id is given).
insight readiness
Check provider, storage and source credential configuration without provider calls. Configuration checks do not prove that a key, model or upstream is reachable; use discover_sources to probe upstream MCP connections.
inspect insight state
Read a persisted workflow artifact: findings, charter, hypotheses, briefs, explanations, coverage, outline, profile, tables, analyses or artifact_checks.
Inventory snapshot 15 Nov 2026. Publisher dates and individual source checks can differ.