verify[402]
snapshot · block — Inspect a URL

Free · read-only · no wallet

Check the 402 before your agent pays it.

An x402 endpoint asks for money by returning HTTP 402 with a payment challenge. The verify402 inspector fetches that challenge once, reads every payment option, and runs the same structural payment preflight an agent should run. Nothing is signed, paid or settled.

01 · Why inspect first

A 402 is a request from a server you do not control.

The challenge names a price, asset, network, payee and resource. Those fields can be wrong, stale, or aimed at a different service. A browser shows a price tag; an agent sees instructions. The inspector turns those instructions into a plain verdict before the wallet does anything.

The public sample points at this service's own paid endpoint, so you can see a real 402 without setting anything up. You can also paste a challenge you already captured with curl -i.

02 · What it reads

Price, token, network, payee, expiry, resource.

For each payment option, the inspector reports the amount and token, the CAIP-2 network, the payee address, the resource, the timeout and expiry, and the structural verdict. It uses canonical USDC recognition, a payee allowlist, resource-identity policy and block freshness where available. It lists checked and notChecked on every result.

VerdictPlain meaning
PASSThe listed structural checks passed at that moment. Not a seller audit.
CAUTIONSomething could not be bound or was outside policy. A human or agent must decide.
BLOCKThe request failed a hard rule, such as payee mismatch or a burn address.

03 · Safe by construction

One fetch. No redirects. No private hosts.

The URL mode fetches a public http(s) host once, refuses localhost and private ranges, refuses redirects, caps the response at 64 KB, and does not forward cookies or auth headers. If the endpoint is slow or unreachable, you get a clear error instead of a guessed verdict.

Paste mode makes no network request at all. It reads the JSON challenge or the base64 PAYMENT-REQUIRED header you supply.

04 · Honest limits

A 402 is not a receipt and not a promise.

The inspector reads one moment. The endpoint can change its challenge a second later. It does not prove that the seller controls the payee wallet, that the resource will be delivered, that the token is safe to sell, or that settlement succeeded. For the exact request you are about to sign, run it through the payment preflight gate with your own policy.

Do not paste secrets

Use a public endpoint URL or a challenge header. Never paste private keys, seed phrases, wallet signatures or authenticated session tokens into the inspector.

Keep going

Inspect, then gate, then sign.

The checker is the first read. The pre-signing gate is the decision your executor can verify.