About the index ↗
MARKET MONITOR / CATALOGUE Services 83,357 MCP listed 39,611 x402 43,755 Rails Base / Solana / Polygon / Arbitrum Imported 2026-10-25 · 2 sources
Transparency

Every number has a source and a date.

This is a catalogue of services other people run. It is not a shop, not a broker and not a review site. The only thing it can honestly sell is knowing where a claim came from.

01

Discovery

Entries come from documented discovery interfaces that exist so that services can be found. Nothing is scraped from search results, nothing is bought, and no provider is listed because they asked politely. A source that changes its terms or closes its endpoint is switched off; its rows keep their last-known state with an older check date instead of being silently rewritten.

02

Attribution

Every row names the source that produced it and the date it was read. Where a figure comes from the provider’s own record it is labelled a provider claim, not a finding of ours. Where we checked it ourselves, the finding is quoted in the evidence field.

03

Reconciliation

A payment is counted once: every ledger row carries the unique id of the record it came from (transfer hash, charge id), so a second ingestion is rejected by the database rather than reconciled afterwards. Usage figures are deduplicated per service and day.

04

Coverage

Missing is shown as missing. A service without a measurement is absent from a ranking and counted as “not measurable” — never shown as zero, because that would claim it has no revenue. Daily histories carry the number of measured days (12/30), so a gap reads as a gap in our evidence.

05

Valuation

A market capitalisation is quoted from CoinGecko for tokens, never invented for services: a service has no circulating supply. The only money figure this site can prove is a settled payment with an evidence class attached — and today that ledger is empty, which the pages state instead of hiding.

The four statuses

StatusWhat it means here
Verified We checked it ourselves and the finding is quoted in the evidence field. For a price this is the endpoint answering with an HTTP 402 and stating the amount; for an endpoint it is our call returning a documented status.
Provider claim Read from the provider’s own record — the registry entry, the discovery listing, their submission. Repeated, not confirmed.
Not found We looked and did not find it. That is a statement about our search, never proof that something does not exist. Every such row names where we looked and when.
Outdated It was true once and a re-check no longer found it. Kept visible rather than deleted, because “was true in March” is information.

Money: three evidence levels, never mixed

A call count is not a payment, and a transfer is not a sale. Only the first two levels below are ever added into an earnings figure; the third is shown as volume and never ranked as revenue.

Level What has to be true Counted as earnings?
Verified · agent-attributed settled_agent We have a processor or facilitator record for the charge, and evidence that the buyer was an AI agent (x402 payment payload signed by an agent wallet, or a provider report that names the agent). Counted as earnings. Yes
Verified · buyer unknown settled_unknown We have a processor or facilitator record for the charge, but no evidence of who bought it. Counted as earnings; never described as agent spending. Yes
Observed transfers observed_transfer A token transfer reached the address the service publishes for payment. A transfer is not a purchase: it can be a treasury move, a refund, a test, or a payment for something else. Shown as volume, never added to earnings. No — volume only

What we measure, and what we merely repeat

·

Endpoint checks are ours

We request the documented URL once, without credentials and without paying. We record the status code, the latency and any payment challenge. A 402 is a success: it proves the service is alive and tells us its price.

·

Usage figures are not ours

Where call and payer counts appear, they come from the source that measured them — currently the x402 Bazaar — and are labelled with the read date. The value shown next to them is calls × published price; it is what the traffic would be worth at list price, not money that moved.

·

Prices are converted only when the unit is unambiguous

x402 amounts are atomic units of a named asset. We convert when the asset is identified as USDC with six decimals; if it is not, the price stays empty and the raw amount is kept as a note.

·

Nothing is scraped, nothing is paid, nothing is stored about buyers

We do not bypass paywalls, do not use credentials that were not given to us, and do not store wallet keys. A payment is a row with a public transaction id; the person behind the wallet is not something this site can know.

Connected sources, their terms and the limitation of every metric: Data coverage. The machine-readable version of this page is the OpenAPI spec.