Skip to main content
Corpus makes the path from source material to API response explicit. For SEC-derived data, Corpus collects directly from EDGAR and, as each accession is processed, archives source submissions and serves normalized records with filing accessions and acceptance timestamps. For market, document, news, and court datasets outside EDGAR, Corpus identifies the public or licensed source and preserves the strongest source identity available.
Primary source is a specific claim. Corpus uses it for data collected directly from SEC EDGAR. Stooq, Accord Fintech, publisher RSS feeds, curated annual-report libraries, and AWS Open Data distributions are identified as third-party, licensed, or public-source collections instead.

Why provenance matters

Research and production systems need to explain an input after the fact. A price, line item, filing section, or judgment should be traceable to a named source, stable identifier, observation date, and the time it became available to the system. Corpus separates those concerns:
  • Source identity tells you where the record originated.
  • Event or report time tells you when the underlying event occurred or period ended.
  • Knowledge time tells you when Corpus could have known the value.
  • Parser and normalization versions identify the transformation applied to source material.
  • Availability state distinguishes a known document from one whose bytes or derived text are ready to serve.

United States sources

SEC JSON endpoints are collected from data.sec.gov; filing bytes and accession components come from sec.gov/Archives. Corpus follows the SEC fair-access policy and archives immutable source bytes before derived records are considered complete.

India sources

China sources

Raw Baostock responses are content-addressed into immutable storage with a manifest before any curated record is derived, so the China panel is re-derivable from raw plus code without refetching from the upstream service. China price data is classified scraped_prohibited — Baostock conveys no exchange redistribution licence — which makes it internal-only and excluded from every resale surface. The authoritative feeds are licensed to non-Mainland entities through China Investment Information Services for Shanghai and Shenzhen Securities Information Co. for Shenzhen; reclassification requires a signed licence.

From source to response

  1. Register the source - transport, legal basis, trust level, cadence, and expected record contract are declared before ingestion.
  2. Archive the artifact - replayable source bytes are stored with a content hash when the source supplies a document or submission.
  3. Parse and normalize - source-specific parsers produce typed records; parser and taxonomy versions identify the transformation.
  4. Record time correctly - report, event, publication, filing, and knowledge timestamps are kept distinct where the source provides them.
  5. Serve through a governed contract - jurisdiction and capability scopes, processing state, and rights decisions determine what a key may read or export.

How to audit a response

Depending on the resource, look for:
  • cik, accession_number, filing_type, filing_datetime, url, and registrants for SEC filings
  • content_hash, parser_version, and source_offsets for filing content and items
  • normalization_version in financial-statement metadata
  • isin, nse_symbol, bse_code, and artifact_id for Indian instruments and annual reports
  • source_id, url, and published_at for news
  • judgment_id, cnr, court, decision_date, has_pdf, and has_text for judgments
  • as_of and record-level knowledge_time for point-in-time analysis
Not every source publishes every field. Corpus returns missing authoritative values as null and availability as an explicit boolean or processing status.

Provenance guarantees and limits

  • Direct EDGAR lineage - SEC-derived records retain an accession-level path to the source filing.
  • Immutable replay - document pipelines use content-addressed artifacts so a parser result can be reproduced and hash-checked.
  • Filing amendments stay visible - amended filings retain separate accession metadata. The serving financial-fact projection is not a lossless accession-and-context ledger and may coalesce same-day concept duplicates.
  • No-look-ahead reads - as_of and knowledge_time support reconstructing the information set available at a historical cutoff.
  • Named non-SEC sources - Corpus does not describe third-party market or document collections as direct exchange or regulator feeds.
  • Rights-aware access - an endpoint in the contract does not grant a user redistribution rights. Access and export permissions remain subject to the provisioned key and source rights.
  • Processing is not hidden - metadata availability does not imply that a PDF, normalized text, filing section, or normalized statement has completed processing.
For dataset scope and dated coverage observations, see Coverage.