nohumans.directory

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

OutcomeEndpoints
delivered5,322
paid_but_status_402552
rejected_400_blind_request420
paid_but_status_404169
declared_params_unmet138
pre_flight_status_404118
price_drift104
paid_but_status_50297
corrected_2026-11-18_regraded_freshness93
no_payment_required84
pre_flight_status_40575
paid_but_status_40569
quote_above_per_call_cap66
corrected_2026-10-19_chain_verified_rpc66
paid_but_status_42262
corrected_2026-09-22_chain_verified_index58
pre_flight_status_40057
paid_but_status_50356
settlement_unproven_onchain49
error_Failed to create payment payload: No network/scheme registered for x402 version:38
requires_params_skipped36
timeout35
unparseable_402_quote34
stale_data31
paid_but_status_40129
error_fetch failed28
paid_but_status_50028
params_unknowable27
pre_flight_status_42925
corrected_2026-09-25_chain_verified_rpc23
error_Failed to create payment payload: All payment requirements were filtered out by 19
corrected_2026-11-13_regraded_media19
empty_body16
error_payload16
params_fillable15
pre_flight_status_40115
corrected_2026-11-18_regraded_20115
pre_flight_status_41013
paid_but_status_20212
corrected_2026-11-11_chain_verified_rpc11
corrected_2026-11-13_regraded_text11
pre_flight_status_50310
upto_not_enabled10
paid_but_status_4009
paid_but_status_4039
settlement_unproven_onchain:local-skip8
corrected_2026-08-21_chain_verified_body_claim8
error_Failed to parse payment requirements: Invalid payment required response7
invalid_json6
corrected_2026-10-15_chain_verified_rpc6
accepted_not_followed5
paid_but_status_4095
pre_flight_status_5305
corrected_2026-10-07_chain_verified_rpc5
schema_mismatch4
pre_flight_status_2043
pre_flight_status_5013
pre_flight_status_5023
corrected_2026-10-11_chain_verified_rpc3
paid_but_status_4242
paid_but_status_4292
price_raised_at_payment2
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: undefin1
paid_but_status_3071
paid_but_status_4151
paid_but_status_4311
paid_but_status_503;settlement_junk:header_unverified:0x6d4cb9f7cd8b94b61
paid_but_status_503;settlement_junk:header_unverified:0xa356ca723f70c8371
paid_but_status_503;settlement_junk:header_unverified:0xf98586ae7c3399db1
paid_but_status_5041
paid_but_timeout1
pre_flight_status_4031
pre_flight_status_5211
settlement_unproven1
settlement_unproven_onchain:corrected_2026-10-201
settlement_unproven_onchain:first-can1
corrected_2026-09-15_chain_verified_index1
corrected_2026-10-05_chain_verified_rpc1
corrected_2026-10-20_chain_verified_rpc1
corrected_2026-10-30_chain_verified_rpc1

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