Xbrlkit
Read SEC EDGAR and XBRL filings with an AI: 18 tools over the filing itself. Local, free, no account
Work with XBRL filings above Arelle: fetch a filing, parse it once into a neutral typed model, and project that model into whichever portable representation you need — or hand it one of those representations and get the model back.
EDGAR ───────────┐
filings.xbrl.org ├──▶ Arelle ──▶ XbrlModel ──┬──▶ holon.jsonld (RDF / JSON-LD)
XBRL zip / iXBRL ┘ ▲ ├──▶ TAVI (compiled model)
│ ├──▶ xBRL-JSON (OIM)
holon, TAVI ──────┘ └──▶ property graph (parquet, .lbug)
primary HTML ──▶ xbrlkit.text ──▶ sections (text blocks, Items, tables)
holon, TAVI ──▶ xbrlkit view ──▶ the report, rendered in a browser
any of the above ──▶ xbrlkit serve ──▶ MCP client (18 shaped tools)
Three ways in — the SEC, everyone else through
filings.xbrl.org, and the filing itself: an
XBRL package or archive (.zip), an iXBRL document (.htm), a bare instance
(.xml), a filing directory, or an http(s) URL to any of them. Nothing about
the middle of this requires EDGAR, or a regulator at all — a report that was
never filed with anybody parses like one that was.
Four projections out, and two of those read back, so a report that was never an
SEC filing gets the same treatment. A fifth surface, the filing's text, reads
the primary HTML directly and needs neither Arelle nor the network. And
xbrlkit view puts a filing on screen.
It is also a local MCP server. The package stands alone — a library and a
CLI — but xbrlkit serve holds filings in memory and exposes them to Claude,
ChatGPT or any MCP client through eighteen shaped tools, which makes reading a
filing a conversation instead of a script: ask for a statement, the concepts
behind a phrase, what foots to a subtotal, a segment breakdown, an exhibit, or
a regex across the prose. Nothing is indexed and no database sits behind it —
every answer is read from the filing in memory, on your machine.
What you can ask it →
Arelle stays the parser — nobody should reimplement DTS resolution. What it
does not give you is anything ergonomic to hold: ModelXbrl is a large
mutable object graph tied to a controller you have to close. XbrlModel is the
answer to that — stateless, single-filing, lossless, and the waist every
projection hangs off.
The one architectural rule: everything goes through XbrlModel. A feature
that reaches into Arelle's ModelXbrl directly is bypassing the waist, and
that is the change that turns a kit into a junk drawer.
What's in the box
parse |
Arelle in, XbrlModel out |
the load, the DTS cache policy, taxonomy packages |
serialize |
the four projections | holon, TAVI (+ its gap report), xBRL-JSON, the property graph |
deserialize |
the importers | a holon or a TAVI read back into the model, no Arelle |
edgar |
the SEC | discovery, download, full-text search, 1994 onward |
filings_org |
everyone else | ESEF and the national regimes, by LEI |
text |
the filing as prose | inline text blocks, 10-K/10-Q Items, the XML forms |
serve |
the local MCP server | eighteen shaped tools over a filing in memory |
From the project's README.