State of x402 - directory statistics

This page reports the slice of x402 that x402 List measures directly, on a rolling 30-day horizon: the services in this directory and the facilitators we watch on-chain. It is not a census of the whole ecosystem. For what x402 is and how it works, see what is x402.

Over a 30-day window anchored to UTC midnight, the services listed here account for 5.3% of the settlement volume we can measure through the facilitators we track (as of 2026-09-28 04:38 UTC). That share is our coverage of the measured flow, not of the ecosystem, and it is itself a floor: settlement we never observe, or cannot attribute to a listed service, is not counted in it.

As of September 28, 2026, 831 services are listed as accepting x402 (743 answering now, 88 offline), and a further 63 offline for 30 days or more are delisted, 772 payment-ready and 12 delivery-verified, average uptime 97.4% (trailing 30 daily rollups).

Two 30-day numbers travel together and they are not the same number. The facilitator volume further down is the wider one: settlement measured across the facilitators we track, not de-duplicated and not limited to listed services. The measured service traction block on the home page is the subset attributable to listed services, de-duplicated on settlement identity. The coverage share above measures that same relationship on a different basis: a window anchored to UTC midnight rather than the trailing 30 days these figures use, and every facilitator snapshot we hold, enabled or not and with no row cap. So dividing the home traction figure by the facilitator volume further down lands near it and not exactly on it.

Every figure below is generated live from the x402 List monitoring database on September 28, 2026. Uptime here is built from UTC daily rollups: the latest daily rollup (each service's latest UTC-day bucket, reset at 00:00 UTC) and trailing 7d / 30d windows; the API also serves a 90d window per service that fills progressively since monitoring began. Facilitator volume is read directly on-chain. Payment-ready counts services whose endpoint answers a valid x402 challenge and is live (a discovery signal, not an endorsement); verified counts the stronger tier, where x402 List paid a real call and the service delivered. The verified tier starts empty and grows only with paid probes, so it can read 0 while the directory is very much alive. See methodology.