The x402 delivery index

Every x402 directory answers whether a seller is listed and whether its paywall responds. This answers the question a buyer actually has: if I pay, do I get the thing? Generated 2026-11-13T14:01:49.188Z (28h ago) from payability-census-2026-11-09.jsonl - 9 seller(s) graded of 11 attempted, median score 94.

How to read this

Six checks, all free and unpaid, run against publicly advertised paid endpoints - the same requests an x402 client makes to learn a price. No funds move. A score records wire behaviour and is not a statement about a seller's intent, security or product quality.

Our own surface is in the table, graded by the identical code path, and ranked with everyone else. A rating layer that scores itself by a different rule is self-dealing. The spec is open: core/x402_delivery_conformance.cjs, runnable against any seller with --target.

Capped at 10 sellers and 8 priced routes each per run. Both caps are stated because a truncated index that reads as complete is worse than a small one. Served from disk: no third party is graded inside a page request.

Ranked - 9 seller(s)

seller	score	routes graded	routes with a failing check	per check
`stillosdigitalholdings.com` (this is us)	100	40	0	C1 39/39 C2 39/39 C3 24/24 C4 40/40 C5 40/40 C6 40/40
`www.stratalize.com`	95	40	40	C1 40/40 C2 40/40 C3 40/40 C4 40/40 C5 40/40 C6 0/40
`asiaref.dev`	94	40	40	C1 40/40 C2 40/40 C3 0/0 C4 40/40 C5 40/40 C6 0/40
`latamref.dev`	94	40	40	C1 40/40 C2 40/40 C3 0/0 C4 40/40 C5 40/40 C6 0/40
`openclawproductions.com`	94	40	40	C1 40/40 C2 40/40 C3 0/0 C4 40/40 C5 40/40 C6 0/40
`usaref.dev`	94	40	40	C1 40/40 C2 40/40 C3 0/0 C4 40/40 C5 40/40 C6 0/40
`fiatdock.com`	80	40	40	C1 40/40 C2 40/40 C3 0/40 C4 40/40 C5 40/40 C6 0/40
`library.forgemesh.io`	80	40	40	C1 40/40 C2 40/40 C3 0/40 C4 40/40 C5 40/40 C6 0/40
`x402.forgemesh.io`	80	40	40	C1 40/40 C2 40/40 C3 0/40 C4 40/40 C5 40/40 C6 0/40

Unmeasured - 2 seller(s)

Published as unmeasured, with the reason, rather than scored. A seller whose manifest we could not read is not a seller that failed a check.

seller	why not
`minia2a.uk`	no priced routes found in the manifest — FALSE ZERO, not a clean grade
`api.agentstools.dev`	no priced routes found in the manifest — FALSE ZERO, not a clean grade

The six checks

id	asks	a pass means
`C1` PAYABLE_CHALLENGE	Does an unpaid request to a priced route answer 402?	HTTP 402 on an unpaid request.
`C2` CHALLENGE_WELL_FORMED	Does the 402 carry terms a client can actually pay against?	accepts[] (or a PAYMENT-REQUIRED header) with an amount, an asset and a payTo.
`C3` MALFORMED_STILL_PAYABLE	Does a malformed request body still get the price, not a parse error?	402 on a malformed unpaid body. A 400 is allowed ONLY if it also carries the terms.
`C4` METHOD_HONESTY	Does the method the manifest advertises actually answer?	The advertised method does not answer 404 or 405.
`C5` CONSTRUCTIBLE_INPUT	Can a buyer build a valid call from published information alone?	Every required field beyond an attribution id has an example, an enum, or a concrete e.g.
`C6` FREE_EVALUABILITY	Is there any way to evaluate the product before paying?	A free tier, a preview route, or a published example response exists.

Weights sum to 100. A check that could not run on a surface is excluded from its own denominator and never counted as a pass.

Disclosure

Every check is free and unpaid, and no funds move. Scores record wire behaviour on publicly advertised endpoints: whether an unpaid request receives a payable 402, whether that challenge carries terms a client can sign, and whether the call can be constructed from published information. A score is not a statement about a seller's intent, security or product quality. A seller we could not read is published as unmeasured, never as a failure. Our own surface is graded by the identical code path and ranked with everyone else.

Machine-readable: /delivery.json. Corrections are free and are published: /claim.