Skip to content

Agents

SEC API for AI

Give your coding agent grounded SEC and public-market data in one paste. 72 hosted MCP tools, 200+ generated OpenAPI operations, four typed SDKs, installable agent skills, and a persona prompt library — all on the same provenance-first contract model.

72 hosted MCP tools over the same contracts as REST, SDK, and CLI
Freshness, provenance, and trace metadata travel with every result
Bootstrap auth and billing-aware guardrails keep agent usage in bounds

Capabilities

Everything your agent needs, on one contract model.

The same primitives behind the API are exposed to agents directly: hosted MCP, installable skills, typed SDKs, and bootstrap auth.

Connect in one paste

Add SEC API for AI to your agent.

Pick your client, copy the config, and your agent has 72 grounded SEC tools. Then hand it the bootstrap prompt below.

Claude Code
claude mcp add --transport http secapi https://api.secapi.ai/mcp \
  --header "x-api-key: YOUR_API_KEY"

Give this prompt to your agent

Paste this once so your agent knows how to authenticate, resolve entities first, preserve provenance, cite filings, and stay inside plan limits.

You are using SEC API (secapi.ai) as your system of record for SEC and public-market data.

Base URLs:
- REST API: https://api.secapi.ai
- Hosted MCP: https://api.secapi.ai/mcp
- Docs: https://docs.secapi.ai

Rules:
- Authenticate with the `x-api-key` header. Never send the API key as `Authorization: Bearer`.
- Resolve entities (ticker, CIK, CUSIP, ISIN, FIGI) before querying, and pass the resolved CIK downstream.
- Prefer structured SEC API endpoints and MCP tools over raw filing text.
- Carry freshness, provenance, requestId, and trace metadata through to every answer.
- When a number comes from a filing, cite the accession number and the filing page.
- Check GET /v1/billing and GET /v1/limits before expensive or repeated workflows, and stop if the server signals a budget cap or an approval requirement.

Or wire it yourself

Prefer code? Same contracts, four SDKs.

REST, JavaScript, Python, Go, Rust, and hosted MCP all share one contract model.

What agents do with it

The loops your agent can run on day one.

Agent skills

A skill library across research, filings, markets, modeling, and ops.

Skills route your agent into repeatable investor workflows instead of guessing the whole job each turn.

Research skills

Skills that help SEC API Agent build context around one company, one theme, or one peer set quickly.

Built for safe agent usage

Bootstrap auth and billing-aware guardrails.

Agents authenticate with a scoped bootstrap flow and stay inside plan limits with predictable rate limiting and usage attribution. The contract keeps source references, request IDs, and freshness close to the answer.

  • Bootstrap auth: scoped, ephemeral credentials provisioned for agent sessions.
  • Billing-aware guardrails: per-key quotas, budget checks, and usage attribution before expensive loops.
  • Provenance on every result: accession references, source URLs, freshness, and trace IDs stay close to the payload.

Next

Point your agent at the SEC.

Connect your client, hand it the prompt, and start shipping grounded investor workflows.