Getting Started
The shortest useful path
Get one issuer, one filing, and one structured statement working first. Do that before you chase a broader integration. If you are connecting an MCP-aware client, start with the hosted MCP metadata below. For REST and SDK work, start with your API key.Before you make a request
- Export
SECAPI_API_KEY - Verify health at
https://api.secapi.ai/healthz - Verify readiness at
https://api.secapi.ai/readyz - Decide whether you are starting with REST, SDK, CLI, or MCP
- Pick one identifier you already trust such as ticker, CIK, FIGI, ISIN, or CUSIP
REST quickstart
JavaScript quickstart
Python quickstart
CLI quickstart
Install the CLI via Homebrew or npm:Trace hydration quickstart
When a filing-derived response includes trace references, hydrate them by trace id.MCP quickstart
- MCP server:
https://api.secapi.ai/mcp - Protected resource metadata:
https://api.secapi.ai/.well-known/oauth-protected-resource - Authorization server metadata:
https://api.secapi.ai/.well-known/oauth-authorization-server
First MCP tools to call
entities.resolvefilings.lateststatements.get
What to keep from your first success
- the
Request-Id - the exact endpoint or tool you called
- the provenance, freshness, and trace metadata from the response