Dataset catalog
Explore 23 datasets from SEC filings, congressional disclosures and official releases. Each catalog entry lists its source, coverage, update cadence, access and available interfaces.
1.8B+ rows under management and 409 GiB of structured data (all tables, one copy, including intermediate tables; uncompressed) · 410M+ rows in the serving tables (per replica, including projections) · measured 2026-09-25
13F since Q2 2013 · Form 4 since 2006 · Congress since 2014 · FTD since 2017 · counts measured Sep 24, 2026 · How the data is built
23 datasets: 22 available, 1 in development
Ownership and insiders
Who owns what, and who is buying or selling their own stock, from SEC ownership filings.
Corporate and governance
Buybacks, fundamentals, large beneficial ownership stakes and executive pay.
Market structure and government
Congressional trades, settlement failures and Reg SHO threshold lists.
Macro and economic
Rates, the curve, the Fed balance sheet, inflation, positioning, banks and energy.
Row counts as of Sep 24, 2026, measured in production: a dated snapshot, not live totals. Coverage start dates measured Jun 3, 2026; open-ended windows run to the latest release. Live samples are real responses from https://api.ko.io. Signed-out requests use the keyless demo, which covers Free-plan endpoints only.
How the data is built
Each dataset is parsed from a public filing or release, normalized, and tested before it is published.
- SourceEDGAR filingThe original SEC document
- IdentifierForm, period, filerWhich filing a row came from
- StructureParsed rowNormalized, linked fields
- DeliveryWeb · REST · MCPSame row everywhere
- Source-traced
- SEC datasets are parsed from public EDGAR filings. 13F, Form 4 and similar rows don't carry accession numbers; the filings endpoints return each filer's source documents. Reported values and calculated measures are labeled separately.
- Normalized
- Share classes (GOOGL + GOOG) are consolidated, and a manager's linked filing entities are combined into one continuous portfolio where the mapping exists.
- 13F publication checks
- 400+ automated data tests are defined across the datasets. For 13F serving tables a failed test blocks the publish, so the API keeps serving the last good version; 13F holdings are also reconciled to each filing's cover totals.
- One source of truth
- The Terminal, the REST API and the MCP server read the same tables, so a number matches wherever you see it.
Query it yourself
Every available dataset has a REST endpoint; most have an MCP tool. Start on the Free plan.

