The coverage object
Cursor-based dataset responses carry acoverage block beside data:
Some datasets add fields —
notes[] for caveats, staleness for how old the current
snapshot is.
Several datasets are backfilled backwards — newest first, reaching further into the
past over time — so their start date moves. Always read
coverage.available_from from
the response rather than hard-coding a date from this page: an empty result for an
older date range usually means “before this feed’s start”, not “the company did
nothing”.The status endpoint
GET /v1/_status is free to call and returns per-dataset coverage and freshness in one
place:
Freshness by dataset
A summary of where each dataset’s history starts and how often it moves. Entries marked moving are backfilled backwards — checkcoverage.available_from for the
current floor.
Coverage is per-dimension, not per-company
A company appearing in the registry does not mean every dataset covers it. Short interest is US-only; foreign ownership and monthly revenue are Taiwan-only; insider trades are US Form 4 filers; a company found in the registry may have no SEC filings at all. When you filter a cross-company query on a dimension, you also restrict results to the companies that dimension covers. The free vocabulary endpoints (listed in Plans and credits) let you enumerate each dataset’s universe — tickers, CIKs, facets, families — before spending credits on it.Related pages
Company identifiers
How companies are identified across datasets with different footprints.
Plans and credits
The free discovery endpoints for probing coverage before you spend.