x402 endpoint status
Every day I send each listed x402 endpoint one unpaid request and check that it answers with a valid 402 at its listed price. Here are the results, and a box to check one yourself.
Daily x402 endpoint monitor: share of Bazaar listings answering a valid 402, price and payTo match, latency, per-seller status badges.
Data through 2026-09-30 · checked daily
Listings answering a valid 402
95%
2,798 checked on 2026-09-30
…of sellers with genuine buyers
96%
1,974 endpoints
Posted price matches the listing
96%
of valid 402s with a Base USDC price
payTo matches the listing
97%
of valid 402s
Median latency
248 ms
p90 687 ms
5% of checked listings do not answer a valid 402; the most common failure is HTTP 400
Endpoints checked in the last 7 days whose latest check failed, by reason. Denominator: 2,798 endpoints checked.
By seller
Sellers with endpoints checked in the last 7 days. Each gets an embeddable status badge (see badges), which is a nice thing to have when it is green.
Endpoints
How it checks
- Unpaid, one request per endpoint. I never send a payment; I just ask the price. User agent:
wknipe-x402-status/1.0 (+https://wknipe.com/x402/status/; one unpaid request per endpoint per day). The listing's HTTP method (POST gets an empty JSON body), 10 s timeout, 64 KB read, ≤3 redirects. - Scope. Sellers whose Base payTo had a genuine buyer in the latest index week: up to 5 of their endpoints every day, rotating. Every other listing: once a week (one seventh a day).
- Caps. ≤60 requests per host per day, one at a time with ≥1 s between them; ≤4,000 requests per day in total. Latest run: 1,974 priority + 824 rotating requests, of 19,730 listed endpoints.
- Valid 402 = HTTP 402 with a parseable
acceptslist whose entries name a scheme, network, payTo and amount. A listing that answers 200 without payment, 404, 405 or times out counts as not answering. Some endpoints need specific query parameters before they will quote a price; they show as failures here, which the per-seller rate smooths out.