Overview

Data Coverage

The corpus is built from US public-company earnings-call transcripts — semantically indexed and continuously updated.

Coverage is a single, system-wide corpus of public market data — roughly 4,600 documents across about 303,000 indexed segments today, and growing as new calls land. It’s shared across all accounts; there is no per-customer or private data in the service.

Earnings-call transcripts#

Quarterly earnings calls, speaker-segmented (prepared remarks and Q&A), so retrieval can return exactly what management or an analyst said. Coverage spans the major US indices and an expanding watchlist universe:

  • S&P 500
  • Nasdaq 100
  • Dow Jones Industrial Average
  • Plus additional tickers added by demand

Filings#

Coming soon
SEC filings (10-K, 10-Q, 8-K, and more — with section-level access) are on the roadmap as the next data category. They aren’t in the corpus yet, so retrieval currently returns earnings-call transcripts only. The API is built to span multiple source types — the source_types filter and the documentType / filingType fields already exist for this — so adding filings won’t change the contract. Tell us if filings coverage would unblock your use case and we’ll prioritize it.
Primary sources only
Everything in the corpus traces to a primary document — the call transcript. Each returned chunk carries a sourceUrl back to that document, so your users can verify the original.

Filterable metadata#

Every document is tagged with metadata you can scope retrieval by (via the Retrieve endpoint’s filters) and that comes back on every chunk’s source:

  • ticker — company symbol (e.g. NVDA)
  • year and quarter — fiscal period
  • documentType — currently earnings_call; you can scope by it with the source_types array, e.g. ["earnings_call"]
  • filingType — reserved for future filing types (e.g. 10-K); null for transcripts
  • pageNumbers — where the passage appears, for paginated source types (omitted for transcripts)

Freshness#

New transcripts are ingested on an ongoing basis. If you query a period that hasn’t been ingested yet, the API serves the nearest prior period and flags it in meta.periodMismatch rather than returning nothing — see Period fallback.

Need a ticker we don't cover?
The watchlist universe grows by demand. If a company you need isn’t covered, let us know and we can prioritize ingesting it.