SEC filings & holdings API

What you can query

• Filings & headers — submissions, filing headers, parse/download telemetry under filings / sec domains.
• Ownership — holdings and related ownership resources for institutional research workflows (including 13F-oriented paths).
• Provenance — catalogue metadata via /api/v1/resources so agents and apps discover live paths and P0 vs research coverage flags.

Example request

Authenticated REST read (replace the token). Exact resource names come from the live catalogue — do not hard-code paths you have not verified.

curl -sS -H "Authorization: Bearer $FINUTIES_TOKEN" \
  "https://data.finuties.com/api/v1/filings/<resource>?limit=5"

Typical response shape (illustrative):

{
  "data": [{ "accession": "…", "form": "10-K", "filed_at": "2026-07-01T…" }],
  "meta": { "domain": "filings", "resource": "…", "count": 5 }
}

Cost headers such as X-Request-Tokens and X-Request-Cost-EUR appear on metered reads. See pricing.

Freshness & provenance

• P0 filings freshness target: within 24 hours of upstream EDGAR availability (operator SLO; not a guarantee of every form type).
• Use MCP get_resource_freshness or REST status surfaces to inspect observed timestamps and content clocks before relying on a print.
• Upstream SEC terms still apply to end use; FinUties provides governed access, not investment advice.

How teams integrate

1. Register for a FinUties account and API credentials.
2. Browse GET /api/v1/resources for filings, sec, and ownership resources.
3. Call REST GET /api/v1/{domain}/{resource} or MCP query with the same domain/resource pair.
4. Meter usage with response cost headers; see pricing.