--- source_url: "https://secapi.ai/?utm_source=openai" title: "SEC API for AI | Filing Data With the Source Attached" mirrored_at: 2026-09-01T03:02:26.504Z host: secapi.ai cited_in_42a: true mirror_canonical: "https://index.42a.ai/secapi.ai/index__q__utm_source_openai" --- > **Original source:** https://secapi.ai/?utm_source=openai SEC data for investment work ## The filing is the evidence. Keep it attached. Resolve the issuer, retrieve the filing or fact, and keep the accession number and SEC link beside the result. SEC API gives software and agents a structured way into EDGAR through REST, four SDKs, the CLI, and hosted MCP. [Create an API key](https://secapi.ai/signup)[Inspect the API](https://secapi.ai/apis) 18.6M searchable filing manifests, with coverage back to 1993 200+ public REST operations across filings, facts, ownership, and search 106 hosted MCP tools for agent clients The public record, made queryable 18.6M Searchable filing manifests EDGAR coverage back to 1993 · production count dated July 1, 2026 200+ Public REST operations Filings, sections, facts, ownership, search, events, and more 106 Hosted MCP tools The same product domains, exposed for agent clients The first useful loop ## From issuer to evidence. Start with the company identifier. Search the filing record, retrieve the narrow section or fact, and retain the source fields the route returns. The point is a result another analyst, service, or agent can inspect. [ REST and SDKs ### Build directly against the API Use REST or typed JavaScript, Python, Go, and Rust clients for filings, facts, ownership, search, and event data. ](https://docs.secapi.ai/libraries-and-sdks)[ CLI ### Inspect a result from the shell Resolve an issuer, search filings, or print a compact response before you put the request into a service or research job. ](https://docs.secapi.ai/libraries-and-sdks)[ Hosted MCP ### Give an agent structured SEC tools Connect once and expose 106 hosted tools for issuer resolution, filing search, sections, facts, ownership, and related workflows. ](https://secapi.ai/agents) A real request path ## Find the filing. Pull the evidence. The examples use NVIDIA's 2026 10-K and show selected fields. Live results change as filings arrive; use the returned accession number and SEC URL to check the underlying record. [Browse the API catalog](https://secapi.ai/apis)[Read the docs](https://docs.secapi.ai/) Commercial control ## Know the cost before the loop runs. Begin with a bounded task. When it becomes a service, monitor, or agent loop, use the published meter families and account limits to keep usage deliberate. Due diligence ## Test the request you intend to repeat. A productive evaluation resolves an issuer, returns the record you need, and verifies the identifiers and source fields that matter downstream. Do that before building around an assumption. [ ### Compare SEC APIs for agents Compare interfaces, filing coverage, response controls, source fields, implementation effort, and public pricing against the workflow you need. ](https://secapi.ai/compare/best-sec-api-for-ai-agents)[ ### Run a filing-search proof Resolve an issuer, find its latest filing, retrieve one section, and inspect the accession and source fields returned by those routes. ](https://docs.secapi.ai/evaluate/sec-filing-search-api)[ ### Check pricing before fanout Quote the workflow by meter family before a monitor, RAG job, or agent loop starts calling the API repeatedly. ](https://docs.secapi.ai/evaluate/pricing-and-limits) Performance ## Measured, dated, and scoped. This snapshot records p50 latency and payload size for selected entity-resolution, filing-search, and structured-facts requests. Captured March 18, 2026; it is a workload comparison, not a general SLA. latency ### Entity resolve p50 latency Resolve a public issuer by ticker or identifier with normalized metadata and provenance. Provider Value Notes SEC API 33.98 ms — Typical SEC API 231.46 ms — Captured 2026-03-18. Measured against typical SEC data APIs on identical issuer and filing workflows. latency ### Filing search p50 latency Search recent SEC filings with compact, source-cited metadata and a small response contract. Provider Value Notes SEC API 37.62 ms — Typical SEC API 265.23 ms — Captured 2026-03-18. Measured against typical SEC data APIs on identical issuer and filing workflows. latency ### Structured facts p50 latency Return normalized financial facts instead of a giant filing payload. Provider Value Notes SEC API 34.45 ms — Typical SEC API 400.53 ms — Captured 2026-03-18. Measured against typical SEC data APIs on identical issuer and filing workflows. payload ### Structured facts payload size Average bytes returned for the structured-facts workflow in the dated benchmark suite. Provider Value Notes SEC API 1,522 bytes — Typical SEC API 1,426,498 bytes — Captured 2026-03-18. Measured against typical SEC data APIs on identical issuer and filing workflows. [Benchmark methodology](https://docs.secapi.ai/benchmark-workflows) Start with evidence ## Make one request worth keeping. Create a key, resolve a company, and retrieve the latest filing or a specific section. Then select the interface that belongs in your research or production workflow. [Create an API key](https://secapi.ai/signup)[Follow the quickstart](https://docs.secapi.ai/getting-started)[See pricing](https://secapi.ai/pricing)