x402 endpoints, checked: November 2026

• ValidAnswered 402 with payment terms a buyer can read.3,655 (87.1%)
• Valid, with something to fixAnswered 402 with terms, but a field is wrong or the answer is slow.84 (2.0%)
• Did not quote a priceTo a request with no input. This is not the same as broken: see below.414 (9.9%)
• Could not be reached45 (1.1%)

An endpoint that checks its input before it quotes will answer 400 here and 402 to a real buyer, and a path that needs real parameters can answer 404, so “did not quote” only means it did not quote to us. What those 414 answered:

• 20040
• 404151
• 402 with no readable terms38
• 400, 415 or 422108
• 5xx33
• Anything else44

Among the 3,739 endpoints that quoted a price:

• On x402 v2133 are still on v1.96.4%
• Payment options using the exact scheme99.1%
• Accept Base96.2%
• Accept Solana23.8%
• Accept Polygon13.4%
• Accept Arbitrum12.2%
• Offer more than one payment option29.6%
• Price, medianThe lowest USDC option on Base, across 3,731 endpoints. One in ten charges $0.19 or more.$0.01
• Time to answer, medianOne in ten took over 929 ms. 17 took over three seconds. Measured from one machine.487 ms

• A POST-only route that answers GET with something other than 405. 32.2% of endpoints quote a price only on POST. Of the 962 we could compare, 418 (43.5%) answered a GET with something else, usually a 404 or a 200. A client or crawler that tries GET first has no reason to try again. It fooled our own checker: see below. A 405 says the method was wrong, not that nothing is there.
• An amount that is not in base units. 29 endpoints left it out or sent a decimal such as 0.01. For USDC, one cent is 10000.
• A network name in a v2 answer. 24 endpoints sent something other than a CAIP-2 id, such as base where v2 expects eip155:8453. The name is correct in v1.
• A listed price that is not the price charged. Of 3,726 endpoints we could compare on Base USDC, 201 (5.4%) asked for an amount other than the one listed: 106 more and 95 less. Some of that will be dynamic pricing or a listing that has not refreshed, but a buyer comparing prices sees one and is asked for another.
• A 402 with terms nobody can read. 38 endpoints answered 402 with neither a PAYMENT-REQUIRED header nor a body with an accepts list that we could read.
• A listing that outlived its domain. 21 listed names no longer resolve, and 5 failed certificate checks.

Check your own endpoint, free and with no account. If it speaks x402 you can see it as an Agoreum listing.

• The list is agentic.market's public directory. Its pages shifted as we read them, so we read it several times and reached 4,190 of the 4,208 services it reported.
• One endpoint was chosen at random from each service, at most three per host. So a service with thousands of buyers counts the same as one with none: this describes what is listed, not what is used.
• Each endpoint got one GET and, if that did not answer 402, one POST with no body. The requests name us in their User-Agent, went only to public HTTPS addresses, and came from one machine on one day.
• We sent no input and paid nothing, so this says nothing about whether any service does what it claims. It shows whether a buyer could read the price.
• Who answered what stays private. This is a picture of the market, not a list of who got it wrong.
• Agoreum sells this check and lists x402 services, so we have an interest in you caring about it. The method is here so you can judge that.

Our first run said far fewer endpoints were valid. Most of the gap was our check: it asked with POST only after a 405. Across the 3,421 endpoints in both runs, 420 moved from “not x402” to speaking x402 once that was fixed, and we had been giving that wrong answer to anyone who asked. If our checker told you your endpoint was not x402 before 6 November 2026, please try it again.