SEC EDGAR API comparison
The SEC EDGAR API choice for agent-ready filing data
A practical comparison for teams building on SEC filings. Direct EDGAR access is the primary source. Arkolith is for teams that want normalized filing events and sourced ownership or insider rows an agent can call.
Reviewed 2026-07-09
Pick the provider that can answer the exact query with the least hidden cleanup. For Arkolith, the proof point is not only that an endpoint returns data. It is that the row can be traced to a source filing, an accession, and the data model decision that produced it.
curl -H "Authorization: Bearer $ARKOLITH_KEY" \
"https://arkolith.com/api/v1/insider/transactions?limit=10"Best for
- Agents that need normalized SEC filing data rather than raw filing documents.
- Watchlist workflows where a ticker event needs to resolve to issuer, insider, accession, and source URL.
- Ownership and insider data products built on top of EDGAR filings.
- Teams that need source proof without building parsing and polling infrastructure first.
Not for
- Bulk archival download of every EDGAR document and attachment.
- Forms outside the supported Arkolith normalized surfaces unless the roadmap explicitly covers them.
- Replacing SEC.gov as the legal primary source.
- A full-text legal research product with every exhibit, attachment, and filing narrative.
Comparison table
This table compares provider shapes, not sales claims. Use it to decide what to test first.
| Provider shape | Best for | Proof | Limitations |
|---|---|---|---|
| Arkolith EDGAR layer | Normalized ownership, insider, and filing-event workflows over REST and MCP. | Source accession, filing URL, accepted timestamp, parser version, and modeled row provenance. | Not full EDGAR coverage. It is deepest on the ownership and insider cluster. |
| SEC EDGAR direct | Primary source retrieval, legal verification, and complete filing documents. | Official SEC documents, accession numbers, and company filing indexes. | You build polling, retries, parsing, form-specific schemas, entity resolution, and agent tools. |
| Generic EDGAR APIs | Teams that need broader filing coverage or convenience endpoints over raw SEC data. | Vendor source links and filing metadata where documented. | Check whether normalized rows preserve field-level provenance and point-in-time semantics. |
| Research agents and terminals | Questions that need summarized filings, narrative analysis, or analyst UX. | Citations and linked filings where available. | May run inference and return answers rather than raw, reproducible data rows. |
Source and provenance proof
Normalized rows retain the SEC accession and source filing URL.
Form-specific modeling is explicit, so a Form 4 transaction is not treated like a generic filing blob.
The public data pages show what is supported today and what remains roadmap, which keeps claims bounded.
Run the path
FAQ
Is Arkolith a replacement for SEC EDGAR?
No. EDGAR remains the primary source. Arkolith models selected EDGAR-derived workflows so agents can call structured, sourced data without rebuilding the pipeline.
Which EDGAR forms does Arkolith support best?
The strongest current surfaces are the 13F ownership spine and SEC Form 4 insider transactions. Broader filing-event coverage should be judged against the live data pages and docs.
When should I use raw EDGAR instead?
Use raw EDGAR when you need the complete filing document, every exhibit, or legal primary-source review. Use Arkolith when your workflow needs normalized rows with source proof.