Company filings U.S. SEC
SEC EDGAR APIs (data.sec.gov)
Retrieve official US company submission records and reported XBRL financial facts from SEC data services.
Source review: 2026-10-18 · Imported: 1 November 2026
A practical starting point
What could you build?
A company research assistant can find a recent filing and trace a reported figure to its source.
Before you connect
Send the required User-Agent and respect SEC access limits. Distinguish reported facts from calculations made by your application.
Capabilities & requirements
Dated specifications from the licensed source dataset. “Not published” indicates missing information, rather than confirmed absence.
| Capability | Details and source |
|---|---|
| Status | Not published The SEC gives no stage label; the API page was last reviewed Apr 8, 2025. Source (external) · Not published by vendor: checked 2026-10-18 on https://www.sec.gov/search-filings/edgar-application-programming-interfaces |
| API key required | No key; User-Agent required With a contact User-Agent we got 200; with none or curl’s default, 403. Source (external) · Verified 2026-10-18 by test request to https://data.sec.gov/api/xbrl/companyconcept/CIK0000320193/us-gaap/AccountsPayableCurrent.json |
| Free tier | Free The SEC says the APIs need no authentication or API keys. Source (external) · Verified 2026-10-18 on https://www.sec.gov/search-filings/edgar-application-programming-interfaces |
| Rate limit | 10 requests/second per user Across all your machines; the SEC may block IPs that exceed it. Source (external) · Verified 2026-10-18 on https://www.sec.gov/about/developer-resources |
| Official MCP server | No official MCP server The SEC developer pages list REST APIs, RSS feeds and bulk files only. Source (external) · Verified 2026-10-18 on https://www.sec.gov/about/developer-resources |
| Official SDK | Plain JSON over HTTPS No SEC client library is published. Source (external) · Verified 2026-10-18 on https://www.sec.gov/about/developer-resources |
| Data license / terms | Not published The API pages publish no data license; access must follow SEC.gov’s Privacy and Security Policy and fair-access rules. Source (external) · Not published by vendor: checked 2026-10-18 on https://www.sec.gov/search-filings/edgar-application-programming-interfaces |
| Commercial use allowed | Not published The SEC does not state rules for commercial reuse on its API pages. Source (external) · Not published by vendor: checked 2026-10-18 on https://www.sec.gov/search-filings/edgar-application-programming-interfaces |
| CORS / browser use | Not supported (per SEC) GET returned Access-Control-Allow-Origin: *, but our OPTIONS preflight got 403 and the SEC says CORS is unsupported. Source (external) · Verified 2026-10-18 on https://www.sec.gov/search-filings/edgar-application-programming-interfaces |
| Freshness / coverage | Real time; bulk ZIPs nightly Submissions under a second, XBRL under a minute after dissemination; ZIPs around 3:00 a.m. ET. Source (external) · Verified 2026-10-18 on https://www.sec.gov/search-filings/edgar-application-programming-interfaces |
Operational reference
Additional facts and qualifications retained from AgentAPIList’s CC BY 4.0 dataset, with provider references.
Price
Free. The SEC says the data.sec.gov APIs need no authentication or API keys.
Provider reference (external)API key / auth
No key, but send a descriptive User-Agent (name and contact email). On 2026-10-18 our request with a contact User-Agent returned HTTP 200; with no User-Agent, or curl’s default, it returned HTTP 403.
Provider reference (external)Rate limit
No more than 10 requests per second per user in total, regardless of how many machines you use. The SEC may block IPs that send excessive requests and does not allow unclassified bots.
Provider reference (external)Terms
Automated access must follow SEC.gov’s Privacy and Security Policy and fair-access rules. The API pages publish no separate data license.
Provider reference (external)Freshness
Submissions update with a typical delay under a second and XBRL APIs under a minute after dissemination (longer at peak times). Bulk ZIPs are rebuilt nightly around 3:00 a.m. ET.
Provider reference (external)CORS
The SEC says data.sec.gov does not support CORS. Our GET with an Origin header did return Access-Control-Allow-Origin: *, but an OPTIONS preflight got HTTP 403, so plan on calling it from a server.
Provider reference (external)Setup references
HTTP request example
Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.
curl -sS "https://data.sec.gov/api/xbrl/companyconcept/CIK0000320193/us-gaap/AccountsPayableCurrent.json" \
-A "YourApp research you@example.com"Agent connection example
Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.
// Minimal agent tool (OpenAI/Anthropic function-calling style)
{
"name": "sec_company_concept",
"description": "Reported XBRL values for one company and one us-gaap tag from SEC EDGAR (data.sec.gov).",
"input_schema": {
"type": "object",
"properties": {
"cik": { "type": "string", "description": "10-digit CIK with leading zeros, e.g. 0000320193" },
"tag": { "type": "string", "description": "us-gaap tag, e.g. AccountsPayableCurrent" }
},
"required": ["cik", "tag"]
}
}
// Implementation: GET https://data.sec.gov/api/xbrl/companyconcept/CIK{cik}/us-gaap/{tag}.json
// with header User-Agent: "<app> <contact email>"A tool schema needs an HTTP implementation; it does not by itself install an MCP server. Keep credentials out of browser code.
Other connections to explore
- FinancialFilings MCP (external)
- OpenFIGI API (external)
- DexPaprika API (external)
- NPPES NPI Registry API (external)
- TED Search API (external)
- BLS Public Data API (external)
Source & reuse
Download the complete licensed source snapshot (JSON), including the original source’s caveats, alternative notes and examples.