Sources and coverage
How we know
Two independent streams are measured on this page. A probe asks each advertised URL for a 402, and an on-chain read counts settlement that actually moved. This page is how far each one reaches. The provider score adds a third source these counts do not cover, off-chain identity corroboration, which is documented on About.
Each group below describes its evidence and when it was updated. The streams are counted separately and are not built on the same clock, so there is deliberately no single page-wide timestamp.
Stream one · the probe
What answers when we ask
We send each advertised URL an unauthenticated request and read the payment challenge it returns. We ask for the terms; we never call the endpoint or pay it.
Endpoints known
—
every advertised URL we have found
Ever answered
—
— returned a payment challenge at least once
Live at last pass
—
answered its most recent probe
Never probed
—
not eligible for the live universe
Of the endpoints that answered, what did they actually say?
- Named a way to pay——
a price, an asset and a chain
- Said what you get——
a description of the work
- Both——
a complete offer — this is what a caller needs
- Answered without asking for payment——
responded, but published no terms
Read live from endpoint availability checks through the public data service on each page load. No figure on this page is baked into the build.
Who relays
Facilitators, as a statistic
Organisations that relayed measured settlement, by share of the measured total.
Answering is not the same as being callable. A URL that replies but names no price cannot be paid by an agent, and it does not reach the endpoint board.
Stream two · the chain
What settlement we can attribute
Settlement is read from public chain state. Attribution means tying a receiving account to a provider we can name from a public catalog — most accounts we see are never claimed by anyone.
Settlement measured
—
across every chain we read
Attributed to a provider
—
— of measured volume
Receiving accounts seen
—
— map to a named provider
Accounts above $100
—
— of those are named
Read live from public payment coverage through the public data service on each page load. No figure on this page is baked into the build.
The two coverage numbers disagree on purpose, and the gap is the honest part: almost all of the money lands on accounts we can name, while almost none of the accounts can be named — the long tail is hundreds of thousands of addresses that moved dust. We report both rather than the flattering one.
Where it settles
Multi-chain payment index
Every chain we admit, with what the catalog advertises on it and what actually settled. Read live; a chain with no settlement figure has none we can attribute, which is not the same as none happening.
Reach
Chains and confidence
Chains in the catalog
Settlement attributed
Settlement is read independently on each chain in the first group. A chain in the second is one the catalog advertises and we have no settlement we can attribute on, which is not the same as none happening.
An endpoint that accepts payment on two chains is one endpoint, counted once.
Read live from network payment summaries through the public data service on each page load. No figure on this page is baked into the build.
Providers by confidence tier
- Corroborated—
- Established—
- Emerging—
- Listed—
- Unrated—
A tier says how much evidence stands behind a provider, not how good it is. Most providers are Listed: present in a catalog, with nothing yet corroborating them.
Read live from provider evidence summaries through the public data service on each page load. No figure on this page is baked into the build.
Every figure on this page summarizes public endpoint or payment evidence. There is no catalog browser here, because browsing a catalog is not how a caller enters, and no facilitator table, because who relays the payments is a share of a total rather than a list to walk. Fleet counts and relay shares used to be their own pages; they are statistics, so they sit here. Read the methodology