Free · no wallet · read-only
Read the price tag before your agent pays.
Paste an x402 endpoint. The inspector fetches its 402 once, then runs the same structural payment preflight an agent runs before signing: price, token, network, payee, expiry, and a PASS / CAUTION / BLOCK verdict with typed reasons and a receipt. Nothing is signed, paid, or settled.
Free · no wallet One fetch · no redirects Never signs Fail-closed
Try it · free · no wallet
One URL in. A verdict out.
Spend 0.03 USDC on a story? Pay a random API? Point the inspector at it first. The default sample is this service's own paid endpoint, so you can see a real challenge without setup.
Advanced: paste a 402 challenge instead
curl -s -X POST https://vex402.online/inspect \
-H 'content-type: application/json' \
-d '{"url":"https://vex402.online/verify","method":"POST"}'
Nothing fetched yet.
Run an inspection to see the price, the payee, the verdict, the reasons, and the checks that actually ran.
Verdict
—
- Price
- —
- Network
- —
- Token
- —
- Payee
- —
- Resource
- —
Reasons
Payment options
Checked
—
Not checked
—
Raw response
Built for the x402 ecosystem. The inspector is free because it has to run before every payment. The paid checks stay paid. How the gate decides
The 402 is not proof that the seller controls the payee. The inspector says what it verified and what it did not.
The inspector stays free. The mainnet cutover is funded by one-month sponsorships — no token, no equity, no influence on verdicts.
What it checks
The same gate, pointed at a real 402.
Every option in the challenge goes through the structural payment preflight. The inspector adds three checks that only make sense with a target URL, then reports one verdict.
The money
Scheme, network, asset, amount, and payee. The gate recognizes USDC, USDT, DAI, and USDG on the chains it supports — a known dollar stable is named instead of flagged — while a non-zero non-burn payee and an amount inside the policy are still required.
The binding
The challenge's resource must name the URL you asked about. If the response is not a 402, the inspector says so instead of pretending it checked a paywall.
The options
Every accept is checked. Several payees, a missing resource, an unknown token, or a zero amount each become a typed reason — never a silent pass.
What the fetch can and cannot do
The URL is resolved first, every resolved address must be public, and the connection is pinned to that address — so a second DNS answer cannot point it at localhost. Redirects are refused, the body is capped at 64 KB, and the request carries no credentials. The response is treated as untrusted data. The fetch is still a best-effort guard on a shared host; the pasted-challenge mode makes no request at all.