x402 · merchants

x402 merchants, ranked by evidence

One row per payout address, with the chains it is registered on. The order uses what we observed and nothing else: first sellers with x402-style payments from several outside payers on Base, then sellers whose endpoints answered HTTP 402 when we asked, then the rest. Listing count, the seller’s own wording and any payment to us never move a row. Latest collector run: 2026-10-05.

Own an x402 endpoint? Run the endpoint doctor to see what a buyer’s client would see.

Merchants · 1,793 indexed

Answers 402

Whether the listed endpoints answered HTTP 402 with a parseable payment payload when we asked. Each reading carries its date. We never send a payment, so we never observe delivery.

Payments

x402-style payments, last 7 days (Base): payments, payers and USDC from an exact read of the window. Wallets we pay from are removed before counting. Method: counted when the transaction carries a signed USDC authorization (EIP-3009), the settlement x402's exact scheme uses. Some non-x402 gasless sends use it too. Chains other than Base show unknown because we do not measure them yet. USDC that reached the payout address by other routes is shown on each profile as context and never moves a row.

Unknown

A blank means we hold no reading. It is never counted as a failure and never ranked below a reading that says no.

Claimed

The payout key signed a message for this page. It proves control of that key and says nothing about the service.

Related

Declared endpoints that answer · Facilitators · House rules

Data CC-BY-4.0, attribution: data by satohub.ai. Appearing here is not an endorsement. The same list is at /api/x402/merchants.