Insider trading API comparison
The Form 4 insider trading API for sourced agent workflows
A practical comparison for teams that need insider transactions as structured data, not just alerts. The hard parts are transaction-code classification, insider identity, issuer resolution, and source proof.
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?ticker=TSM&signal=true"Best for
- Agents that need to explain whether a trade was an open-market buy, sale, grant, award, or exercise.
- Cluster-buy screens where several distinct insiders bought the same issuer in a defined window.
- Ticker-level dashboards that need recent insider activity plus source accessions.
- Workflows that link an agent answer back to a human-readable issuer insider page.
Not for
- Legal claims that a trade was illegal insider trading. The API models disclosed Form 4 transactions.
- Non-US insider disclosure regimes or private-company transactions.
- A real-time news alert product with editorial summaries.
- A complete market-data bundle for prices, fundamentals, estimates, and private markets.
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 Form 4 API | Structured insider trades, cluster signals, ticker pages, and MCP calls for agents. | SEC accession, issuer, insider, transaction code, shares, price, value, and provenance metadata. | Focused on SEC Form 4. It does not label trades as illegal or cover every global regime. |
| SEC EDGAR direct | Primary-source Form 4 XML and filing verification. | Official Form 4 filing documents and accession numbers. | You parse XML, footnotes, derivative tables, amendments, identities, and cluster signals yourself. |
| Broad market data APIs | Teams that want insider data alongside prices, fundamentals, and other feeds. | Vendor records and source references where documented. | Often optimized for breadth. Check how transaction codes, footnotes, and source accessions are exposed. |
| Alert and research tools | Human monitoring, emails, watchlists, and summarized insider news. | Alert payloads and linked filings where provided. | Good for awareness, weaker for reproducible agent calls and field-level provenance. |
Source and provenance proof
Each transaction preserves the Form 4 accession and transaction code context.
Open-market buys and sells are separated from award, exercise, and derivative-table noise.
Issuer ticker pages show the same transaction stream that REST and MCP expose.
Run the path
FAQ
What is an insider trading API?
In this context it usually means a structured API for publicly disclosed SEC Form 4 transactions. It does not mean the provider knows whether a trade was illegal.
Why do transaction codes matter?
A Form 4 can report open-market buys, sales, grants, awards, option exercises, gifts, and derivative transactions. Treating all of them as the same signal creates false positives.
When should I use Arkolith for insider data?
Use Arkolith when the workflow needs structured Form 4 line items, source accessions, ticker-level pages, and MCP or REST access for an agent.