// compare
Form4API vs EdgarTools: library or hosted API?
Updated 2026-07-12. By Theodor Nielsen, founder of Form4API. Checked July 2026 against EdgarTools' public GitHub repository and documentation.
// answer
EdgarTools is a genuinely excellent free, open-source Python library for pulling SEC filings, with broad form coverage, no key, and no rate limit. Form4API is a hosted, real-time insider trading API with webhooks. These solve different jobs, not competing versions of the same job: EdgarTools is well suited to ad-hoc research you run yourself; Form4API is suited to production systems that need push delivery and an uptime guarantee. Many teams reasonably use both.
What EdgarTools is
EdgarTools (github.com/dgunning/edgartools) is an actively maintained, MIT-licensed Python library with roughly 2,500 GitHub stars and a weekly-ish release cadence. It covers a broad slice of the SEC corpus — 10-K, 10-Q, 8-K, XBRL, Form 3/4/5, 13F, Form ADV — with a clean, typed Python API. A Form 4 lookup is a couple of lines: Company("AAPL").get_filings(form="4").latest().obj(), with a .to_dataframe() for the underlying transactions. It has recently added its own MCP server and AI skills, aimed at the same Claude/agent-tooling audience Form4API targets. It is not a bolt-on side project — it is a serious, well-built library used at hedge funds and fintechs, per its own documentation.
None of that is a knock on Form4API's approach; it is simply a different tool built for a different mode of working.
Different jobs, not a rivalry
EdgarTools is a library: you pip install it and call functions inside your own process. That means no API key, no rate limit, and full control — but also no push notifications, no hosted uptime, and support that depends on one maintainer's availability (their GitHub Sponsors tiers exist precisely to fund faster response times, which is a healthy sign of a sustainable project, not a red flag). It is also Python-only.
Form4API is a hosted REST API: no infrastructure to run, real-time webhooks on paid plans, any language over HTTP, and a published, measured uptime and ingestion-latency figure (p50 ~59s / p95 ~92s as of July 2026). The trade-off is the opposite of EdgarTools': you give up running your own process in exchange for not having to run it at all.
Use EdgarTools for research, Form4API for production
A practical split that works for a lot of teams: use EdgarTools in a notebook to explore a company's Form 4 history, sanity-check an idea, or do one-off analysis across the broader SEC corpus — it is free, fast to start with, and Python-native. When an idea is ready to become a feature that needs to react to new filings as they happen, register for real-time alerts, or serve non-Python consumers, that's where a hosted, webhook- based API like Form4API takes over — see the webhooks guide for how the delivery model works.
Neither tool is trying to be the other. If your whole workflow is local Python research with no push requirement, EdgarTools alone may be all you need, and there is no reason to pay for Form4API on top of it.
Side-by-side, by job-to-be-done
| Dimension | Form4API | EdgarTools |
|---|---|---|
| Job to be done | Production integrations: real-time alerts, trading automation, apps that need push delivery and uptime | Ad-hoc research: exploring a filing, a quick DataFrame, notebook analysis, one-off scripts |
| Cost | Free tier, then $49/mo (Pro) and up | Free, open source (MIT), no paid tier — sponsorship is optional, not required |
| Setup | Hosted REST API — no infrastructure to run | Python library — you install, run, and host it yourself |
| Real-time push | HMAC-signed webhooks on paid plans | None — pull-based; you poll if you want freshness |
| Language | Any language over HTTP; MCP server, JS/Python SDKs | Python only |
| Uptime / SLA | Hosted; measured latency & uptime published on /status | None — no formal SLA, single maintainer |
| Form coverage | Form 4 + Form 144 + 13F-HR (insider-focused) | Broad — 10-K/8-K/XBRL, Form 3/4/5, 13F, ADV, and more |
| AI/MCP tooling | MCP server — 27 tools + 6 prompts | Ships its own MCP server + AI skills for Claude |
Sourced from EdgarTools' public GitHub repository and documentation as of July 2026.
Frequently asked questions
Is EdgarTools free?
Yes. EdgarTools is MIT-licensed, open source, with no API key and no rate limit — you install it with pip and it runs against SEC EDGAR directly. Its maintainer offers optional paid GitHub Sponsors tiers ($250–$1,500/mo) for support SLAs and strategy calls, but the library itself carries no license fee or usage cap.
Can EdgarTools replace a hosted insider trading API?
For ad-hoc research, often yes — it can pull a company’s Form 4 filings into a typed object or a DataFrame in a few lines of Python. What it doesn’t provide is a hosted, always-on service: no webhooks or push notifications, no formal uptime SLA, and it depends on a single maintainer. For a production system that needs to react to new filings in real time, or that isn’t written in Python, a hosted API like Form4API fills a gap EdgarTools isn’t designed to fill.
Should I use EdgarTools or Form4API?
Many teams reasonably use both. EdgarTools is well suited to interactive research, prototyping, and notebook work, especially in Python, and its broad SEC form coverage goes beyond insider filings. Form4API is suited to production integrations that need real-time webhooks, a language-agnostic REST API, and a hosted uptime guarantee, with insider-specific depth like amendment supersession and 10b5-1 flags. Prototype against EdgarTools; move to a hosted webhook-based API when the feature ships to production.
Does EdgarTools have real-time alerts or webhooks?
No. EdgarTools is a pull-based library: you call a function and get data back, on your own schedule. There is no push mechanism, which is a deliberate consequence of being a library rather than a hosted service — the same reason it has no formal SLA. If your use case needs an event to trigger the moment a filing lands, that is what a hosted webhook API is for.