Skip to main content
About Arche

The financial record, as it stood on any date.

Arche turns SEC EDGAR filings into point-in-time financial statements, drawing on a corpus of 17,000+ companies that have filed with the SEC, with filings from 2009 to today. That starting point is the SEC’s: XBRL financial data was phased in from 2009, so the earliest years hold fewer companies and nothing structured exists before them. Every figure carries the filing it came from, and every answer can be replayed and proven later, so AI agents, applications and research teams can cite what they use.

Filings change. The record shouldn’t.

Companies amend, restate and reclassify after they file, and most data sources replace the earlier figure with the new one. When Axon Enterprise amended its FY2024 10-K in May 2025, current liabilities rose from $997.6 million to $1.68 billion. A source that overwrites history returns $1.68 billion for a query dated March 2025, a figure that was not filed until May.

Arche keeps every filing as filed. Time is a dimension of the data, not a filter applied afterward.

  • Point-in-time resolution. Every request resolves against an explicit as-of date, based on when each filing reached the SEC. Results carry no look-ahead, and the same query returns the same answer every time.
  • Immutable history. Every filing is kept as filed. A restatement is the amendment filing, kept beside the original with a per-metric delta that says whether the change is material. The original never changes.
  • Provenance on every metric. Each figure traces to the filing it came from, its SEC acceptance time and how it was mapped from XBRL. Point-in-time snapshots and query results carry SHA-256 hashes you can check a later run against.
  • Checked, not assumed. Accounting identities, rollforwards and segment totals are reconciled. A check that runs reports PASS or FAIL with the expected and actual values; one that cannot be concluded reports SKIPPED with its reason, never a pass.
  • Stable contracts. Versioned schemas, deterministic ordering and explicit errors, served through the same contracts over HTTP and MCP.

What did we know then?

Every figure Arche serves can answer that question for any date, and name the filing it came from.

How the record is kept

Principles you can query

Point-in-time

Time is an axis, not a filter

The same request, resolved against two as-of dates either side of the amendment, returns what was on file that day.

Immutability

Amendments add, they don’t overwrite

Each filing's figures are kept as filed. An amendment is added as its own filing, and nothing filed is rewritten.

Stated up front

The edge cases are published

Every metric carries its definition: what it depends on, and what it returns when a denominator is zero or an input is missing. You read that before you integrate, not after.

Who it’s for

Work that has to hold up

AI agents
Schema-validated MCP tools that answer from filed figures and name the filing behind each one, so an agent cites a source instead of a guess.
Financial applications
Typed schemas over HTTP for products that show fundamentals to their own users, and a signed webhook when a figure they showed is restated.
Research, audit and models
A record of what was reported, when it changed and by how much, and a replay token that proves what a model or backtest read.
Protos Systems

Built by Protos Systems

Arche is built and operated by Protos Systems LLC. We build financial infrastructure that holds its answers still: every filing kept as filed, every figure traceable to the filing it came from, and the same query answerable years from now.

Protos Systems LLC · protos.fi

Contact us