Landscape · deep-dive · XBRL / iXBRL

agentic-first vs XBRL.

XBRL is the right answer for regulated financial filings of listed companies. It is the wrong answer for the ~99% of companies that don't file. agentic-first borrows XBRL's discipline (currency, period, revisions) without trying to model the full P&L, and stays deliberately on the public side of the financial-promotion line.

What XBRL is

XBRL (eXtensible Business Reporting Language) is a mature, ISO-aligned XML-based standard for financial reporting, and iXBRL is its inline form embedded in HTML. It's mandated by regulators across the world: SEC EDGAR (US-listed), Companies House (UK), ESEF (EU listed), HMRC (UK corporation tax), and more. Taxonomies cover the full statutory P&L and balance sheet at a level of granularity that auditors can sign off.

It does what it does very well - for the audience it's built for. If you're a listed company filing annual accounts, XBRL is non-negotiable.

Why most companies don't use it

XBRL is not a publishing standard, it's a filing standard. It addresses regulators, auditors, and exchanges; it's submitted through their portals, not hosted on the company's own website. Production tooling is enterprise-grade: tagging, taxonomy mapping, validation against the regulator's specific schema. For a private Series A or a fractional NED, the closest XBRL gets to being relevant is "your accountant filed it for you eight months after year-end."

What's missing - and what XBRL was never built to solve - is a lightweight, current, banded, publisher-controlled summary that a sourcing agent can fetch in one HTTP GET. That's the slot agentic-first fills.

Side-by-side

Question	XBRL / iXBRL	agentic-first
Audience	Regulators, auditors, exchanges, financial analysts	Agents, directories, investors, customers, the publisher's own ops team
Who's mandated	Listed companies + regulated entities (~1% globally)	Voluntary; designed for the other 99%
Granularity	Full statutory P&L, balance sheet, cash flow at line-item taxonomy	Public: banded summaries (revenue band, growth band, headcount band). Protected: precise figures behind your own auth.
Where it lives	Submitted to a regulator portal; sometimes mirrored on the company's investor-relations page	`/.well-known/agentic-profile.json` on the company's own website
Cadence	Annual / semi-annual / quarterly, lagged by months	Refresh whenever you want - directory revalidates daily for verified profiles
Tooling required	iXBRL tagging suite, taxonomy mapping, regulator's validator	A text editor
Discipline borrowed	-	Explicit currency, explicit reporting period (`as_of`), revision-aware bands. We don't reinvent the discipline; we just narrow the scope.
Financial-promotion exposure	Out of scope - filings are statutory disclosures	Public surface uses bands only - never precise revenue, growth, or fundraise numbers - to stay clear of UK FCA financial-promotion rules

Where the two compose

For listed and regulated firms, both can ship together - they describe different things at different cadences:

XBRL for the statutory annual / quarterly filing, in the regulator's pipeline.
agentic-first public profile for the always-current banded shape an agent fetches without going through EDGAR or Companies House.
agentic-first protected profile for diligence-grade detail an investor needs between filings, behind the company's own OAuth.

For everyone else - private companies, fractional advisors, portfolio companies of an accelerator - agentic-first is the only one of the three that actually applies.

Example: same company, both surfaces

A UK-listed SaaS company files annual accounts in iXBRL with Companies House. They also publish an agentic-first profile so an investor agent doing a sector scan finds them with a current, banded snapshot rather than year-old XBRL:

{
  "schema_version": "0.1.0",
  "updated_at":     "2026-04-19T00:00:00Z",
  "profile_kind":   "company",
  "tier":           "public",
  "company": {
    "name":         "ListedCo",
    "website":      "https://listedco.example",
    "jurisdiction": "GB",
    "registry":     { "type": "companies-house", "id": "00000000",
                      "url":  "https://find-and-update.company-information.service.gov.uk/company/00000000" },
    "lei":          "5493001KJTIIGC8Y1R12"
  },
  "stage":   { "current": "Public" },
  "metrics": { "revenue_band": "10m-50m",
               "growth_band":  "20-50%",
               "as_of":        "2026-03-31" },
  "evidence": [
    { "kind": "filing",
      "url":  "https://find-and-update.company-information.service.gov.uk/company/00000000/filing-history",
      "supports": "/metrics/revenue_band" }
  ]
}

The XBRL filing carries the precise figures, audited and signed off. The agentic-first profile carries the up-to-date banded shape, with the filing itself as evidence. The two reinforce each other.

The honest summary

XBRL is a triumph of regulatory data engineering and we're not remotely competing with it. We're standardising the surface regulators don't reach: the lightweight, current, banded, publisher-controlled file an agent or a directory can use as a first read. If you file XBRL, ship agentic-first too - the audiences don't overlap. If you don't file XBRL, agentic-first is the closest thing the open web has to a structured-business summary you can publish yourself.

Read the standard → Back to landscape