AgentPay Directory / docs

Probe-pass

The strip on a listing answers one question: could a current x402 v2 client pay this endpoint without a human reading its docs? It answers nothing about whether the data is good. A seller that serves only the older v1 shape fails, even though an old v1 client could still pay it, because a client written this year expects v2 and that seller is a dead end for it.

Blocking checks decide the state. Notes are gaps worth fixing that cannot stop a client paying, so they are published without changing the state. A listing can pass with notes. The live count is at /api/directory/probe-pass, never printed here, so it cannot go stale.

What it checks

CheckKindWhat has to be true
answersblockingThe endpoint replies with HTTP 200 or 402. Not a timeout, not a 5xx. A 400 or 422 makes the result inconclusive, not a fail.
v2blockingThe 402 carries x402Version: 2.
price_namedblockingThe price is in the 402 body or an X-402-Price header.
network_namedblockingThe network is named, for example eip155:8453.
pay_to_namedblockingThe payee address is named.
resource_namednoteThe resource is named, so a client knows what it is paying for.
facilitator_namednoteA facilitator is named at the root or in accepts[].extra.facilitator. A facilitator in accepts[].facilitator is read if present, but never required.
facilitator_all_levelsnoteIt appears in both spec-safe places: root facilitator and accepts[].extra.facilitator. We do not ask for accepts[].facilitator: it is not a field of x402 v2 PaymentRequirements, and because a client echoes the accepted requirements back with its payment, adding it can stop a standard client's payment from matching.
header_body_consistentnoteWhere both the PAYMENT-REQUIRED header and the JSON body carry payment terms, they agree on version, network, amount and payTo. A client that reads only one of them must get the same answer. The header is what gets graded, because it is the canonical v2 transport.
gatedblockingAn unpaid request gets a 402 rather than the data.

States

How it runs

Run history

The first full run failed listings that a current client could pay, and every one of those fails was a bug in the probe, since fixed. The record is published with seller identifiers removed and a hash of the unredacted rows, so the number is checkable without naming anyone: first run, 2026-11-20.

Settlement observation, and its invariant

A settlement number never renders without the address and the window that produced it. The three states are counted, watched_zero, and not_observed. Zero only ever means an address was watched and nothing arrived. If no address or window was recorded, no number is emitted at all, because a number with no source is worse than an empty field.

Read it as data

The record is published as JSON, with the invariants written into the schema so a client can validate rather than trust:

What it does not do

Questions or a re-probe request: support@x402-agent-pay.com