← opdevio  ·  shop

The x402 conformance census

We ran Coinbase's own validator against every endpoint in Coinbase's own x402 catalogue — all 10,811 of them. Just over half fail it. Nearly a third cannot accept a payment at all.

10,811endpoints in the catalogue
52.1%fail the validator
30.3%cannot take a payment at all
1median payers in 30 days

Measured 18–19 September 2026. Rechecked continuously, oldest first.

Method

Every resource listed in the CDP Bazaar discovery catalogue, submitted to the CDP validator endpoint, which applies 25 preflight checks. The verdicts are not ours. They are the catalogue's own validator applied to the catalogue's own listings, so no endpoint here is being judged against an outside standard.

Just over half fail

ResultEndpointsShare
Pass all checks5,17947.9%
Fail one or more5,63252.1%

The failures split into two very different groups

Lumping them together hides the important part. A listing that is merely hard to discover is a different problem from a listing that takes your money nowhere.

Failure modeEndpointsShare of catalogue
Broken. No parseable 402 at all — wrong status, unparseable body, or nothing there3,27630.3%
Invisible. Payment works, but discovery metadata is missing or malformed2,29421.2%

The first group is the one to care about as a buyer. Close to a third of everything in the catalogue is listed, looks live, and will not complete a payment. We spot-checked samples directly and got exactly what the validator got: 404, 405, 502, and a handful of endpoints returning 200 with no payment step at all.

The second group is a seller's problem, and a quiet one — the endpoint works perfectly. It just cannot be found, priced, or called automatically by anything that reads the catalogue.

Demand is real, and it is shallow

Almost everything listed has been paid at least once: 10,807 of 10,811 endpoints have one or more unique payers in 30 days. That number flatters the market. The distribution behind it does not.

Unique payers in 30 daysEndpointsShare
At least 110,80799.96%
10 or more3172.93%

The median endpoint in the catalogue has one unique payer and one to two calls across the whole month. The mean of 3.97 payers is carried by a thin tail — a single endpoint tops out at 2,255. Read the median, not the average.

Conformance does track demand — modestly

This is the finding we most expected to be an artifact, so we tested it that way. Mean payers alone would be misleading, because a handful of very busy endpoints distort both groups. After discarding the top 1% of each group, the gap survives:

PassingFailing
Mean payers, top 1% removed2.331.64
90th percentile payers53
99th percentile payers2617
Median calls21

Every robust statistic points the same way, by roughly 40%. But the medians are equal at one payer each. Conformance is worth having and it is not what decides whether anyone shows up.

One pattern we checked and discarded: endpoints with four to eight failing checks appear to average 23 payers, far above every other group. That is a single 949-payer endpoint distorting 239 rows. Its median is 1 and its 90th percentile is lower than the catalogue's. There is no real effect there.

If you are paying an endpoint

Check it before you call it. A 30.3% chance the thing you found in the catalogue cannot complete a payment is worth one cent to rule out.

Check an endpoint — $0.01

If you are listing one

Discovery metadata is the single most common thing missing: 2,294 endpoints that take payments correctly are invisible to anything reading the catalogue. Among failing endpoints, the most frequent individual failure is a missing output example, at 67.8%.