01
Open data for everyone
Direct from SEC EDGAR, EDINET, ESEF, CNINFO, and the rest. Every filing keeps its source URL.
About
Public filings are open.
We make them speak one language.
Every company covered here already discloses its numbers to a regulator, for free. What's missing isn't the data — it's a common structure across 62 markets, a dozen accounting standards, and just as many languages and portals.
OpenFilings is a small, remote-first team based in Switzerland, building the infrastructure that reads a filing once and makes it queryable everywhere — Filings and Atom (RSS+), a REST API, and MCP for AI agents.
Our mission
Build your own analyst on OpenFilings.
Bring open data to everyone. Make fundamentals a common asset for the world's analysts.
Enrich your analysis with an agent connected to OpenFilings, or build your own on the same filings. MCP and the API plug into the tools you already use.
02
Fundamentals as a commons
One set of KPI names across GAAP, IFRS, and Asian standards. Revenue, margins, and cash flow, comparable across markets.
03
Filings as they land
Your agent can pull a filing as soon as it hits the regulator, typically under 60 seconds. Browser, RSS+, REST, and MCP.
04
Connect your agent
MCP and the API sit under Claude, Cursor, or an analyst agent you build. Calls, filings, and standardized financials, in the stack you already run.
Why this exists
An analyst covering two markets rebuilds the same work twice
Regulatory disclosure is a solved problem in each market individually — SEC EDGAR, EDINET, ESEF, and the rest all publish reliably. The gap opens once you look across markets: an analyst or fund covering US tech and Japanese suppliers in the same book ends up reconciling GAAP labels by hand, rebuilding parsers per exchange, and risking a comparison between numbers that were never meant to line up.
We built OpenFilings to do that reconciliation once, in the open, so it doesn't have to be redone inside every fund, every terminal, and every side project that needs it.
Methodology
From regulator filing to standardized financials
1. Source directly from the regulator
Every filing is fetched from the official registry — SEC EDGAR, EDINET, ESEF, CNINFO, and the rest — never from a third-party aggregator or a model's training data. The source URL is kept on every filing record.
2. Extract structured data, not OCR guesses
Where a filing carries XBRL or another structured tag set, we extract from that. Otherwise, parsers built per-market read the actual document structure. Numbers are traceable back to the line they came from.
3. Normalize across accounting standards
Revenue, operating income, net income, and the rest of the Golden KPIs use the same field name whether the underlying standard is US GAAP, IFRS, JP GAAP, or K-GAAP — figures are not restated, only made comparable.
4. Verify, don't approximate
Extracted figures are checked against the filed annual report before being marked reliable. Red flags (dilution, margin compression, cash-vs-earnings divergence) are computed from that verified data, not inferred by a language model.
Sources, by market
62 registries, one data model
United States
SEC EDGAR
Japan
EDINET (FSA)
Hong Kong
HKEX
Taiwan
MOPS
Israel
MAGNA (ISA)
United Arab Emirates
ADX / DFM
Saudi Arabia
Tadawul
South Korea
DART (FSS)
China
CNINFO
European Union
ESEF / ESMA
United Kingdom
Companies House
Brazil
CVM
Canada
SEDAR+ / EDGAR (cross-listed)
Australia
ASX
India
NSE
Singapore
SGX
Every filing links back to its source document — we never restate a figure without keeping the trail to where it came from.
Who's behind it
A small, remote-first team — based in Switzerland
OpenFilings is built and operated by a small team, not a large data vendor. We run the product ourselves — the parsers, the API, the dashboards — and we're reachable directly.
Questions about a specific figure, a missing filing, or how a KPI was computed? [email protected].
Explore the data yourself
No sign-up needed to browse companies, filings, or the Atom (RSS+) feed.