Skip to main content
Build one useful result before designing a larger integration. Resolve an issuer, retrieve a current filing or statement, and keep the identifiers that let an analyst or reviewer trace the output back to its source.

​
Make one traceable request

  1. Create an API key and resolve an issuer.
  2. Retrieve the issuer’s latest matching filing.
  3. Save the returned filing identity and request context with any derived output.
For a latest 10-K, the response can include an accession number, filing date, filing URL, and requestId. New filings change what “latest” means, so read those values from the response each time.

Try a live request

Resolve an issuer with a small authenticated request.

Build the filing flow

Resolve an issuer, retrieve a filing, and read a specific section.

​
Select an integration surface

REST is the public HTTPS contract. SDKs, the CLI, and hosted MCP offer other ways to use documented API capabilities.

​
Carry the context needed for review

For filing-backed output, retain the accession number, form, filing date, filing URL, and requestId when returned. Some routes also return provenance, freshness, materialization, warning, or trace fields. Those are route-specific: use the reference page for the fields a particular route guarantees.

​
Set the operating boundary

A working request is not evidence that a repeated workflow fits the account, budget, or commercial rights boundary. Before a repeated job, read GET /v1/billing and GET /v1/limits with the same API key, then use POST /v1/billing/quote for the paths and units you expect to run. Quotes do not reserve usage.

Pricing and limits

Price a bounded proof using current account context.

Agent billing

Add a preflight and stop rule before an automated run.

API conventions

Handle response metadata, retries, and errors correctly.