> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# SEC API documentation

> Make a source-backed SEC request, verify the result, and choose an integration and billing path that fits your workflow

Use SEC API to turn an SEC research question into a request your team can inspect and repeat. Start by resolving one issuer, retrieve one filing-backed result, and retain the identifiers that explain it.

<CardGroup cols={3}>
  <Card title="Make your first request" icon="rocket" href="/try-it">
    Resolve an issuer with an API key and confirm the returned identity.
  </Card>

  <Card title="Build a filing workflow" icon="route" href="/first-request-flows">
    Retrieve a filing, section, or statement and keep the source context.
  </Card>

  <Card title="Check the contract" icon="square-terminal" href="/api-reference">
    Confirm parameters, response fields, and route-specific limits before scaling.
  </Card>
</CardGroup>

## Start with evidence

For a filing-backed workflow, save the returned accession number, form, filing date, filing URL, and `requestId` when present. A latest-filing request can change as new filings arrive, so use the returned filing identity rather than assuming a fixed record.

<CardGroup cols={3}>
  <Card title="Search filings" icon="search" href="/products/filing-search">
    Find a filing by issuer, form, date, or query before extracting from it.
  </Card>

  <Card title="Work with statements" icon="table-properties" href="/api-reference/statements">
    Retrieve normalized annual or quarterly statement data.
  </Card>

  <Card title="Use MCP" icon="bot" href="/mcp-install">
    Connect a compatible client to documented SEC API tools.
  </Card>
</CardGroup>

## Choose the interface that fits the job

| Interface | Use it when                                              | Start here                                  |
| --------- | -------------------------------------------------------- | ------------------------------------------- |
| REST      | You need the exact HTTP request and response contract.   | [First request flows](/first-request-flows) |
| SDK       | You are building in JavaScript, Python, Go, or Rust.     | [Libraries and SDKs](/libraries-and-sdks)   |
| CLI       | You need a terminal check or shell automation.           | [CLI](/cli)                                 |
| MCP       | Your client should discover and call SEC research tools. | [Install MCP](/mcp-install)                 |

## Price before broad usage

Your API key identifies the organization whose limits and billing state apply. Before a watchlist, backfill, or agent loop, inspect that account and quote the actual request path. A quote is an estimate, not a reservation.

<CardGroup cols={3}>
  <Card title="Authentication and billing" icon="key-round" href="/auth-and-pricing">
    Send API keys correctly and separate machine access from dashboard actions.
  </Card>

  <Card title="Evaluate pricing and limits" icon="clipboard-check" href="/evaluate/pricing-and-limits">
    Price a bounded workload from the current account contract.
  </Card>

  <Card title="Commercial boundaries" icon="building-2" href="/plans-and-pricing">
    Check whether your use is internal or needs redistribution rights.
  </Card>
</CardGroup>