Private beta · Connect route · manual review

US public-company filings

Retrieve the relevant filing section without losing company, period, form, or amendment context. Access is manually approved and configured for a bounded source, jurisdiction, and workflow scope.

What this page claims, and where the proof is

  1. The source boundary and exclusions are defined.Stated1
  2. Named authorities are identified.Stated2
  3. A public retrieval benchmark for this scope.Not yet published1

Stated evidence is quoted as written. Nothing on this page is a service level.

Delivery route
Connect
Jurisdictions
United States
Languages
English source filings
Activation
Manual review

Exhibit A · Illustrative · not live

One request. Bounded evidence.

Private-beta interface preview. Access is manually configured for the approved source and workflow scope.

QueryIllustrative · not live

How did this company describe its principal supply-chain risks in its latest annual filing?

companyformfiscal_period

No live result is shown. An approved collection must return bounded passages with citations, source metadata, and one immutable version.

Exhibit B · Coverage perimeter

Built for a retrieval problem, not a document dump.1

Evidence, coverage boundaries, and update targets define this private beta. They are not completeness or service-level promises.

In scope · Intended source scope

  • Official public filings
  • Amendments and filing metadata
  • Deterministic document sections

Out of scope · Explicitly outside scope

  • Market predictions
  • Proprietary analyst research
  • Investment recommendations
Core source. Annual filings · Quarterly filings · Current reports, English source filingsJurisdiction scope, configured per workflow. United StatesOutside. Market predictions; Proprietary analyst research
Jurisdictions
United States
Languages
English source filings
Source types
Annual filings, Quarterly filings, Current reports
Coverage window

A selected company, sector, form, or event set. A full EDGAR mirror is not assumed.

Exhibit C · Versions and updates

No version history is published for this scope yet.

Research target: monitor selected filing feeds during SEC publication windows and reconcile daily archives.

  1. 01Detect

    Compare the approved official source against its sealed snapshot.

  2. 02Review

    Verify the source change, rights boundary, structure, metadata, and lineage.

  3. 03Evaluate

    Rebuild the candidate and run the corpus-specific retrieval fixtures.

  4. 04Activate

    Switch versions only with a tested rollback path and customer notice.

Limit
Update targets are not completeness or service-level promises.

Exhibit D · Evaluation

No public benchmark for this knowledge base yet.1

The published evidence pages currently cover the EU AI Act. The current evidence for this scope is stated below as written, without derived scores.

Official SEC access paths and required filing lineage are mapped. Existing specialist API competition is already strong.

Current evidence, as stated on the catalogue record1
Limit
Evidence, coverage boundaries, and update targets define this private beta. They are not completeness or service-level promises.

Intended retrieval contract

Filter the request. Keep the citation boundary in the response.

Private-beta interface preview. The intended contract returns retrieval context for your application. It does not make the decision your workflow owns.

Example

POST /v1/retrieve · illustrative, not live

query: How did this company describe its principal supply-chain risks in its latest annual filing?
filters: company, form, fiscal_period, filed_at, version

Limit
The intended contract returns retrieval context only.

The bounded job

Who this coverage is for.

How the private beta is intended to be used and delivered.

  • Audience

    Financial research, due-diligence, and company-intelligence products

  • Primary use

    Filing research, change comparison, and evidence-backed company profiles

  • Intended delivery

    Customer-authorized source connection or maintained public collection

  • Private-beta coverage

    Source-linked SEC filings configured by company, sector, form, fiscal period, or event.

Shape the roadmap · Private beta · manual approval

Would this source boundary remove real work for your team?

Tell us the workflow, required sources, freshness, filters, and rights that would make it useful.

What the status means
Access is manually approved and configured for a bounded source, jurisdiction, and workflow scope.
Access boundary
Access is configured around a selected company, sector, form, or event where provenance and change handling matter to the workflow.

Provenance notes

  1. Catalogue record
    Status
    Private beta
    Current evidence
    Official SEC access paths and required filing lineage are mapped. Existing specialist API competition is already strong.
    Publication
    Stated evidence only. No reviewed benchmark or trace is published for this scope.
    Knowledge base catalogue