Agent economy · x402

x402 verified

Declaring x402 support is free. Answering a payment request is not. Every day we ask each declared endpoint for something and record what came back — four states, each measured its own way, each dated. Nothing here is paid for: the probe reads a 402 and stops.

Endpoints · last checked 2026-09-11

Method

One GET per declared endpoint (POST retried on a 405), redirects not followed, 10 s deadline. A payment payload counts when it parses as x402 v2 in the body (accepts[] or paymentDetails) or as v1 in the headers (X-PAYMENT and friends); which one is recorded. The facilitator named in that payload is asked for /supported on its own host only — a facilitator URL that resolves elsewhere is not followed.

Candidate set

Directory listings whose standards field contains x402, plus resources declared by any /.well-known/x402 manifest found on those hosts. ERC-8004 registrations declaring x402Support are not included yet: there is no keyless way to enumerate them today.

Unknown

A timeout, a bot-block or an undeclared facilitator is stored as null and shown as “unknown”. It is never counted as a failure, and endpoints we could not reach are excluded from the rate rather than dragging it down.

Scope

This measures the DECLARED population. The Coinbase Bazaar catalogue is measured separately on the agent-economy pages, and the two populations overlap — they must never be added together.

Related

Who settles x402 payments on Base · Every listing implementing x402

Run caveat

4 of 64 candidates could not be reached and are unknown, not zero. Outcomes: open 48, blocked 4, other 5, unreachable 4, gone 1, answers 2.

Data CC-BY-4.0 — attribution: data by satohub.ai. Listing an endpoint here is not an endorsement, and a standing 402 is a statement about a protocol response on a date, nothing else.

Sato Hub. "x402 verified — declared endpoints probed for a real 402." Sato Hub, updated 2026-09-11, accessed 2026-09-11. https://satohub.ai/x402/verified