Sato Hub
Pay per request

x402

x402 is the HTTP 402 payment protocol for agents and APIs, not ITU X.402. See who takes it, who answers a payment request, and who settles on Base.

As of 2026-11-20, we hold no Base payments reading for any seller wallet yet, and 1,518 of the 1,944 seller wallets we checked answered HTTP 402 when we asked. Payments are counted on Base only; delivery after payment is not measured here, and a payment observed is not proof that the endpoint delivered.

Sellers indexed
4,145
one per payout address, across chainsas of
Answering HTTP 402
1,518
with a payment payload when we askedas of
Payments, 7 daysPayments, 7 daysCounted from signed USDC authorizations (EIP-3009) on Base. Other chains are not measured yet.
unknown
Base only, from signed USDC authorizations, wallets read over the dated window

Where to look

  • The sellers behind the catalogue, one per payout address, ordered by the evidence.

    Browse merchants
  • Endpoints that declare x402 and answered our daily check. The check reads a 402 and never pays.

    See endpoints
  • Who broadcasts x402 settlements on Base, with the public evidence behind each address.

    See facilitators
  • Selling over x402? Paste an endpoint and see what a paying client would meet. Nothing is paid.

    Check an endpoint

Questions this page answers

Which x402 endpoints answered a paid request recently?
Sato Hub does not observe a paid request being answered; what it records is this. As of 2026-11-20, we hold no Base payments reading for any seller wallet yet, and 1,518 of the 1,944 seller wallets we checked answered HTTP 402 when we asked. Payments are counted on Base only; delivery after payment is not measured here, and a payment observed is not proof that the endpoint delivered. Sellers are listed one per payout address on /x402/merchants, with each reading dated.
What is x402?
x402 is the HTTP 402 payment protocol for agents and APIs, not ITU X.402. A server answers an unpaid request with status 402 and its payment terms; the client signs a payment and asks again.
Does the daily check pay for the endpoints Sato Hub lists?
The daily check that feeds these pages sends an unpaid request and records whether the endpoint answers HTTP 402 with a payment payload. It sends no payment, and Sato Hub publishes no paid-delivery result, so what paying returns is never shown on this site.

Appearing in an index is not an endorsement. Every page names what it measured, on which chain and on which date. A blank means unknown, not failed. How we measure