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,941 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.
Reference & capabilities
128 results
PIB
PIB ["pib.gov.in"]
POWER
POWER ["powermin.gov.in", "cea.nic.in"]
RBI
RBI ["rbi.org.in", "dbie.rbi.org.in"]
regulator
regulator "regulator"
rescue extract
Final-rung rescue extraction when native strategies fail. Use this when browser/API/file-based rungs cannot yield the target data: - repeated `blocked` / CDN wall - `auth_wall` / login gate - brittle JS controls with no replayable endpoint - source page reachable but required period/data remains unavailable Executes Kryptos single-URL flow: POST /api/jobs POST /api/jobs/{jobId}/start GET /api/prog
rescue fetch
Fetch one file for an existing rescue extraction job from GCS. Expected object prefix: gs://<bucket>/<prefix_root>/<job_name>/ Use this when: - you already know the target artifact path under a rescue job - you want that single artifact downloaded locally for follow-up tools
rescue wait
Wait for a rescue extraction job to complete, then fetch synced files. Polls Kryptos: GET /api/progress/{jobId} every `poll_interval_s` (default 10s) until status is terminal (completed/failed/cancelled), then polls GCS up to `gcs_wait_timeout_s` (default 60s) to absorb post-completion sync lag. Default is metadata-only. Includes `last_event_text` when present. Use `rescue_fetch` for file contents
REUTERS
REUTERS ["reuters.com"]
SEBI
SEBI ["sebi.gov.in"]
SEC
SEC ["sec.gov"]
SEC_EDGAR
SEC_EDGAR ["sec.gov/edgar"]
SIAM
SIAM ["siamindia.com"]
sitemap probe
Read a site's robots.txt + sitemap(s) and surface its URL inventory — the CHEAPEST discovery step, run BEFORE driving a page. robots.txt and sitemap.xml frequently hand you the stable data URLs directly: a `data_like_urls` list of .json/.csv/.xlsx/.xml/.pdf and /api endpoints you can `download_file` or `call_api` straight away, skipping the browser entirely. Also returns the disallow list (where a
smart fetch
Playbook-aware fetch — the one-call "do the right thing" entry point. Consults the URL's playbook and ACTS on it instead of blindly rendering: - `api` recipe present → replays the endpoint via call_api (templating the params, e.g. the fiscal year, from `focus`), then structures the JSON. - `open_data` mirror present → download_file's it (the open CSV/PDF — the pivot for auth-walled or JS-dropdown
SP
SP ["spglobal.com"]
statistics
statistics "statistics"
strategy
Return the browser-research DECISION PROCEDURE — the escalation ladder (static fetch → visit → act → inspect_network/call_api → download_file → pivot), the signal→action table (what `blocked`, `auth_wall`, `file_links`, `observed_api`, a timed-out select, etc. each mean and what to do), and the core principles (look before you assert, probe before you build, prefer API over DOM over OCR, escalate
today
Return the SERVER'S CURRENT DATE (UTC). Call this FIRST whenever the user mentions a temporal phrase like "latest", "current", "today", "this quarter", "this year" — your training-data cutoff is NOT a reliable anchor. Use the returned `iso_date` (YYYY-MM-DD) and `year`. Returns: {iso_date, iso_datetime, year, month, day, weekday, quarter, fiscal_year_in: "FY26", note}
today
Return the SERVER'S CURRENT DATE (IST, Asia/Kolkata). Call this FIRST whenever the user mentions a temporal phrase like "latest", "current", "today", "yesterday", "this quarter", "this year" — your training-data cutoff is NOT a reliable anchor. Use the returned `iso_date` and `financial_year_in` to construct concrete queries you pass to the other tools.
TRAI
TRAI ["trai.gov.in"]
Inventory snapshot 16 Nov 2026. Publisher dates and individual source checks can differ.