verify[402]
snapshot · block — Run free check

AI agents · x402 · pre-signing

AI agent payment security starts before the signature.

An agent that can pay can also be tricked into paying the wrong address, approving the wrong token, or trusting a stale quote. verify402 puts a free pre-signing gate in front of the signer: it reads the payment request or transaction, prints the reasons, and issues a short-lived receipt the executor can verify.

01 · The actual risk

The dangerous moment is a signature, not a chat answer.

A public x402 endpoint returns an HTTP 402 with a price, asset, network, payee and resource. That challenge comes from a server the agent does not control. If the agent signs it without checking, the payment is valid even when the seller is wrong, the amount is wrong, or the resource is not what the agent thinks it bought.

The same applies to a transaction: an unlimited token approval, a swap with no minimum output, or a call that reverts on-chain can all look reasonable in natural language. The bytes are what the signer sees.

02 · The free gate

One call: PASS, CAUTION or BLOCK.

POST /preflight is free, needs no wallet and returns three things: a verdict, typed reasons, and two lists named checked and notChecked. For a payment it checks the scheme, CAIP-2 network, asset, amount against your cap, payee allowlist, resource host, timeout, payer balance on EVM, and block freshness. For a transaction it checks the recipient, decoded calldata, approval policy, swap fields, simulation, and block freshness.

Fail closed

If the chain cannot be read, the gate returns 503 and no receipt. An executor should refuse to sign. A PASS is a measurement at one block, not a guarantee; a CAUTION is an explicit decision, not a pass; a BLOCK is a refusal.

03 · MCP payment safety

Advice in the agent. Enforcement at the signer.

The verify402-mcp bridge exposes preflight_gate with no wallet, so an agent can ask before it acts. The paid checks need a dedicated wallet and settle per call in USDC over x402. The bridge signs the x402 payment only; it never signs or sends a trade.

MCP is advisory. An agent can ignore a tool result. Put the reference guard where the signature happens: require a verified receipt, require intentBound and requestBound, stop on BLOCK, and demand an explicit acknowledgement for CAUTION.

04 · The paid layer

Deep measurements answer the next question.

The gate says whether the intent is what you think it is. The six paid checks measure claims behind it: /verify $0.05 for a cross-venue arbitrage verdict; /safety $0.10 for quote-based sellability; /route $0.03 for the execution path; /quotecheck $0.05 for a quoted price; /depth $0.05 for trade capacity; and /assure $0.19 for a bundle at one pinned block.

/assure accepts only bundles whose supplied checks cost at least $0.19 separately. It never quietly adds a cheaper check to reach the bundle price. Unsupplied checks stay in notChecked.

What AI agent payment security does not prove here

The gate does not screen sanctions or counterparty reputation, audit a contract, prove who controls payTo, confirm facilitator settlement, inspect off-chain promises, or scan tool output for prompt injection. A PASS means the listed checks passed at that block. Read notChecked every time. verify402 is a measurement service, not financial advice and not a guarantee of profit.

Next step

Start with one request.

Paste a real x402 request into the free gate, or check an endpoint before your agent sends a payment.