verify[402]
snapshot · block — Run free check

Free · x402 · USDC · Base mainnet

Verify a USDC payment request, field by field.

A payment request is a signed authorization waiting to happen. Before an agent signs, verify402's free /preflight gate checks the exact request against your policy and the chain, then returns PASS, CAUTION or BLOCK with a receipt bound to that intent.

01 · What you are checking

Six fields decide what gets paid.

A canonical x402 request names the scheme, network, asset, amount, payee (payTo), and resource. It also carries a timeout. Your own policy adds the maximum amount and the resource hosts you allow. On Base mainnet, USDC uses eip155:8453 and the canonical asset address; amounts are raw units, not dollars.

FieldWhat the gate asks
networkIs this a supported CAIP-2 network on this instance?
assetIs it canonical USDC, or another recognized dollar stable named in the registry?
amountIs it inside your maxAmountUsd cap?
payToIs it inside your payee allowlist, and not a burn address?
resourceIs the URL valid and its host allowed or exactly bound?
timeoutIs the authorization window still open and reasonable?

02 · Chain facts, not vibes

Balance and block age are part of the verdict.

For an EVM request the gate reads the payer's USDC balance where a from address is supplied. It also reads a fresh block and its timestamp: a block older than 30 seconds is CAUTION, older than 120 seconds is BLOCK, and a block with no timestamp returns 503 with no receipt. If the chain cannot be read, the answer is not invented.

Caller-supplied payment.idempotencyKey and obligation state can reject an already-settled key or spending above a grant. Those checks only see the state you pass in; the gate does not persist a ledger.

03 · Reading the result

PASS, CAUTION, BLOCK — and the reasons.

A non-canonical asset is CAUTION by default and BLOCK if you explicitly allowlist only canonical assets. A foreign resource host with no binding is CAUTION resource_identity_unverified; an explicit allowlist mismatch is BLOCK. A payee outside your allowlist is BLOCK. Every response names the checks that ran and the ones that did not.

Pair it with a receipt check

The response includes an HMAC-signed receipt bound to the normalized intent, the request body and the block. POST /preflight/verify recomputes it without a chain call. Require intentBound and requestBound before allowing a signature. See the receipt guide.

04 · Honest limits

A verified request is still not a seller audit.

The gate does not prove who controls payTo, confirm that the facilitator settled the payment, check sanctions or counterparty reputation, or enforce an off-chain promise. A signed seller manifest from a caller-pinned HTTPS origin can bind the request to the seller's published payout list, but wallet ownership still remains in notChecked.

If you need the endpoint's price and payee read from a live 402 first, start with the x402 endpoint checker.

One more read

Check the bytes you will actually sign.

The free gate takes the same request shape your agent uses. No account, no API key, no wallet needed.