Paid verification statistics
Probing proves an endpoint answers. It cannot prove that paying it returns anything. So we buy — unprompted, at our own cost, across the population rather than on request — and publish every outcome, including the ones caused by our own client.
8,285 endpoints purchased from · 5,644 delivered
Latest purchase attempt: 2026-11-22. Every figure on this page is computed live from the database on request.
The pass rate, and what it excludes
Of the endpoints where payment was actually required, 68.8% delivered (5,644 of 8,201). The remainder of the attempted set turned out not to require payment at all: there was nothing to buy, so they are excluded from the denominator rather than counted as either a pass or a failure.
Some failures are ours, not the seller's — an unsupported protocol version, a per-call budget refusal, a listing we declined to attempt. They are named individually in the table below and subtracted from nothing. Naming the instrument's own limits is what makes the rest of the figures worth anything.
Basis
Each endpoint's latest attempt, never every attempt row. Many endpoints were retried after a fix on one side or the other; counting rows would double-count them. Dry runs are excluded.
WITH last AS (
SELECT listing_id, failure_reason, ok,
ROW_NUMBER() OVER (PARTITION BY listing_id
ORDER BY attempted_at DESC) rn
FROM paid_verifications WHERE dry_run = 0 AND superseded_by IS NULL)
SELECT ok, failure_reason, COUNT(*) FROM last WHERE rn = 1 GROUP BY 1, 2;
A record replaced by a published correction is left out (superseded_by IS NULL); the correction
stands in its place, dated when the purchase was made (since 2026-11-18).
What a listing is
A listing is one priced route: one endpoint URL that answers an unpaid request with a payment request. One host often carries many routes, so the catalogue has 10,832 listings on 2,684 hosts. A host is not a seller either: one seller can run several hosts, and a marketplace host can carry many sellers.
The largest host carries 104 listings, 1.0% of all listings (104 of them verified, 1.0% of all verified listings). The ten largest hosts together carry 838 listings, 7.7% of the catalogue. We publish these shares so a count of listings is never mistaken for a count of independent services; the hosts themselves are not named here, though every listing’s own record shows its host.
Same set as listings_total in /v1/stats, where these figures are
listing_definition and host_concentration.
Every outcome
| Outcome | Endpoints |
|---|---|
delivered | 5,322 |
paid_but_status_402 | 552 |
rejected_400_blind_request | 420 |
paid_but_status_404 | 169 |
declared_params_unmet | 138 |
pre_flight_status_404 | 118 |
price_drift | 104 |
paid_but_status_502 | 97 |
corrected_2026-11-18_regraded_freshness | 93 |
no_payment_required | 84 |
pre_flight_status_405 | 75 |
paid_but_status_405 | 69 |
quote_above_per_call_cap | 66 |
corrected_2026-10-19_chain_verified_rpc | 66 |
paid_but_status_422 | 62 |
corrected_2026-09-22_chain_verified_index | 58 |
pre_flight_status_400 | 57 |
paid_but_status_503 | 56 |
settlement_unproven_onchain | 49 |
error_Failed to create payment payload: No network/scheme registered for x402 version: | 38 |
requires_params_skipped | 36 |
timeout | 35 |
unparseable_402_quote | 34 |
stale_data | 31 |
paid_but_status_401 | 29 |
error_fetch failed | 28 |
paid_but_status_500 | 28 |
params_unknowable | 27 |
pre_flight_status_429 | 25 |
corrected_2026-09-25_chain_verified_rpc | 23 |
error_Failed to create payment payload: All payment requirements were filtered out by | 19 |
corrected_2026-11-13_regraded_media | 19 |
empty_body | 16 |
error_payload | 16 |
params_fillable | 15 |
pre_flight_status_401 | 15 |
corrected_2026-11-18_regraded_201 | 15 |
pre_flight_status_410 | 13 |
paid_but_status_202 | 12 |
corrected_2026-11-11_chain_verified_rpc | 11 |
corrected_2026-11-13_regraded_text | 11 |
pre_flight_status_503 | 10 |
upto_not_enabled | 10 |
paid_but_status_400 | 9 |
paid_but_status_403 | 9 |
settlement_unproven_onchain:local-skip | 8 |
corrected_2026-08-21_chain_verified_body_claim | 8 |
error_Failed to parse payment requirements: Invalid payment required response | 7 |
invalid_json | 6 |
corrected_2026-10-15_chain_verified_rpc | 6 |
accepted_not_followed | 5 |
paid_but_status_409 | 5 |
pre_flight_status_530 | 5 |
corrected_2026-10-07_chain_verified_rpc | 5 |
schema_mismatch | 4 |
pre_flight_status_204 | 3 |
pre_flight_status_501 | 3 |
pre_flight_status_502 | 3 |
corrected_2026-10-11_chain_verified_rpc | 3 |
paid_but_status_424 | 2 |
paid_but_status_429 | 2 |
price_raised_at_payment | 2 |
error_Failed to create payment payload: EIP-712 domain parameters (name, version) are | 1 |
error_Failed to create payment payload: No client registered for x402 version: undefin | 1 |
paid_but_status_307 | 1 |
paid_but_status_415 | 1 |
paid_but_status_431 | 1 |
paid_but_status_503;settlement_junk:header_unverified:0x6d4cb9f7cd8b94b6 | 1 |
paid_but_status_503;settlement_junk:header_unverified:0xa356ca723f70c837 | 1 |
paid_but_status_503;settlement_junk:header_unverified:0xf98586ae7c3399db | 1 |
paid_but_status_504 | 1 |
paid_but_timeout | 1 |
pre_flight_status_403 | 1 |
pre_flight_status_521 | 1 |
settlement_unproven | 1 |
settlement_unproven_onchain:corrected_2026-10-20 | 1 |
settlement_unproven_onchain:first-can | 1 |
corrected_2026-09-15_chain_verified_index | 1 |
corrected_2026-10-05_chain_verified_rpc | 1 |
corrected_2026-10-20_chain_verified_rpc | 1 |
corrected_2026-10-30_chain_verified_rpc | 1 |
What we have got wrong
An early draft of our seller page claimed a pass rate near 94%. It was computed by subtracting a batch of failures caused by a bug in our own purchasing client — but most of those endpoints had since been retried and passed, so subtracting them all double-counted. Caught before deploy.
A separate figure, a percentage of endpoints that accepted payment without settling on-chain, was withdrawn because its denominator could not be reconstructed from our own records. Raw counts with a stated sample are published instead. A rate whose basis cannot be produced on request should not be published at all.
Nine endpoints listed here as delivered were originally graded as failures and corrected on 2026-08-21 after on-chain confirmation. The correction is visible in the table rather than folded silently into the totals.
What this does not establish
A delivered paid call proves that one call, at one moment, returned something. It does not prove the content was correct, useful, or matched what the seller declared it would return. Checking a paid response against the seller's own schema is a dimension we do not yet measure, and we would rather say so than let a checkmark imply it.
Nor does any of this establish who operates an endpoint. Everything here verifies behaviour at a URL. See methodology for that boundary in full.
Machine-readable
Every number above, as JSON: https://nohumans.directory/v1/stats · field reference
Questions: hello@nohumans.directory · methodology · for sellers