Developers
Pick a surface. Ship a workflow.
SEC API for AI gives developers a public-market intelligence layer with exact docs, contracts, prompts, and SDKs. The first workflow should be small, source-backed, and easy to verify.
Choose your path
Use the surface that fits the job.
REST API
Use wire-level control when you want exact requests, exact retries, and exact responses.
JavaScript SDK
The native path for web apps, backend services, and TypeScript-heavy teams.
Python SDK
A clean fit for notebooks, research jobs, and data-heavy services.
Go SDK
A lightweight path for typed backend integrations and infra-oriented services.
Rust SDK
For async-heavy or performance-sensitive services that still want the SEC API contract directly.
Hosted MCP
Give coding agents direct access to grounded investor workflows without inventing a glue layer first.
The shortest path
A fast first success beats a sprawling integration plan.
Step 1
Set auth
Export `SECAPI_API_KEY` and verify health before you do anything more ambitious.
Step 2
Run one real workflow
Resolve one issuer, pull one filing, then fetch one structured statement, ownership, or governance workflow.
Step 3
Preserve the metadata
Keep request IDs, freshness, provenance, materialization metadata, and trace references in logs or downstream artifacts.
Agent handoff
Yes, you can give this to your coding agent.
The docs are written to be useful to both humans and coding agents. Prompt blocks are treated as first-class integration artifacts, not a novelty bolted on at the end.
Why teams switch
Less payload drag. More source context.
The win is speed with provenance and cleaner contracts for downstream agent use.
latency
Filing search p50 latency
Search recent SEC filings with agent-ready metadata and a compact response contract.
| Provider | Value | Notes |
|---|---|---|
| SEC API | 37.62 ms | — |
| sec-api.io | 265.23 ms | — |
latency
Structured facts p50 latency
Return normalized financial facts instead of a giant filing payload.
| Provider | Value | Notes |
|---|---|---|
| SEC API | 34.45 ms | — |
| sec-api.io | 400.53 ms | — |
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 | — |
| sec-api.io | 1,426,498 bytes | — |