x402 Preflight · verify a challenge
Verify an x402 payment challenge
Paste an endpoint. See the live 402 decoded — amount, network, asset, receiver, discovery metadata — and the checks that pass or fail. One HTTPS request, no wallet, no credentials, no payment.
Nothing is signed or purchased. The response is public, exactly what any buying agent sees.
—
What the agent sees
Checks
Issues
Bazaar / discovery metadata
What this proves — and what it does not
Proves
Does not prove
Raw JSON
Reproduce it from your terminal
curl -s -X POST https://x402.chikocorp.com/api/preflight/inspect \
-H 'content-type: application/json' \
-d '{"resource_url":"https://your-api.example.com/paid/route","method":"GET","max_price_usd":1}'What each result means
| Decision | Meaning | What to do |
|---|---|---|
ALLOW | The endpoint serves a readable challenge, the price is inside your limit, and network, asset and receiver are consistent. | Nothing to fix. Keep a periodic monitor so it stays that way. |
BLOCK | Either the endpoint does not present a usable challenge (200, 401, 404, 405, unreadable 402) or the price is above your limit. | Read the issues list: each one names the check, the evidence and the fix. |
UNKNOWN | The route could not be verified as published — usually a template with :param that has no real value. | Retry with a real sample value for the parameter. |
Why this is not a purchase
A challenge check reads what the endpoint asks for. It cannot tell you whether a correct payment gets settled, whether the facilitator accepts it, or whether the resource actually gets delivered — that requires a funded wallet and a real transaction, which is a different, paid check. Any report that claims to verify settlement without spending is guessing.
See the paid audit and diagnostic Guides for x402 developers