otlite · Web and records
Install EDGAR Tool on Linux or macOS in one command
EDGAR Tool runs the SEC's full-text search over company filings and saves the matches to a file. Each row names the filer, form type, and filing date and links to the document, in CSV, JSON, or JSON Lines.
EDGAR Tool in three lines
pipx install otlite
otlite install edgar-tool
otlite run edgar-tool -- q:acmeRuns bellingcat/edgar (MIT, ★ 218, otlite 1.2.1, catalog updated Oct 23, 2026). otlite installs and runs it at a tested version; it does not change or verify the tool itself.
What EDGAR Tool is for
- Finding every US filing that mentions a person or company name.
- Narrowing by form type, date range, or place of incorporation.
- Pulling recent filings for a list of tickers with edgar rss.
Typed inputs for EDGAR Tool
otlite translates these prefixes into EDGAR Tool's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- q:
- Search text ·
otlite run edgar-tool -- q:acme
Run every installed tool that takes the same input at once: otlite run --all q:acme
Where the results go
Every run lands under ./results/edgar-tool/<target>/ as a timestamped output file, a .meta.json sidecar (the exact command, start and end time, exit code, and the SHA-256 of the output), and a .envelope.json with the entities found, in the same shape for every tool. List runs with otlite results, group them with --case, compare the last two with otlite diff edgar-tool <target>, and pull indicators out with otlite extract edgar-tool.
Before you run it
- The q: input runs edgar text-search, and a filing must contain every word you give, so shorter queries return more.
- Searches cover the last five years by default. Add --date-range all or --start-date for older filings; SEC full-text search starts in 2001.
- edgar rss with --every-n-mins keeps polling until you stop it. Run it on its own rather than under otlite run --all.
Update, remove, inspect
otlite info edgar-tool # inputs, keys, an example command
otlite example edgar-tool # sample output, where there is one
otlite update edgar-tool # move to the next tested version
otlite remove edgar-tool # delete its virtualenvFull reference: the otlite docs, and the tool's own README on GitHub.
Pairs with
FAQ
EDGAR Tool with otlite, answered
How do I install EDGAR Tool on Kali, Ubuntu, or macOS?
Install otlite once with pipx install otlite (or the one-line installer on the otlite page), run otlite init, then otlite install edgar-tool. The tool lands in its own virtualenv under ~/.otlite/, pinned to a version that was tested, so nothing touches your system Python. otlite doctor prints the command that fixes a missing git or venv module.
Which inputs does EDGAR Tool take through otlite?
q: (search text). otlite maps each prefix to EDGAR Tool's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.
Where does otlite save EDGAR Tool results?
Under ./results/edgar-tool/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar (the exact command, timing, exit code, and SHA-256) and a .envelope.json with the entities found. Add --case <name> to group runs, otlite results to list them, and otlite diff edgar-tool <target> to compare the last two.
Does EDGAR Tool need an API key or a login?
No key is required for the basic run. Optional keys, where the project supports them, go in with otlite keys set NAME and are passed only to tools that declare them.
Can I run EDGAR Tool together with other tools?
Yes. otlite run --all q:acme runs every installed tool that takes search text input, in parallel, including EDGAR Tool. Save the combination as a playbook to repeat it.