verify[402]
snapshot · block — Inspect a 402

Live watch · no wallet

Known x402 endpoints, watched.

A small public list, re-inspected every 15 minutes. Each entry carries two verdicts: protocol — is the challenge well-formed x402? — and sign — should an agent on our supported networks sign it? Most live 402s sit on chains this instance cannot verify, so sign is often BLOCK while protocol is PASS. Both are shown, and changes are recorded.

Free · no wallet 15-minute refresh No signatures Fail-closed

The list · public endpoints only

Every entry, every check.

Each row is one endpoint, its latest challenge, and what changed since the previous check. Nothing here is an endorsement; a PASS means the challenge is well-formed, not that the seller is honest.

memory 15 min No auth sent
Endpoint Price Network Payee Protocol Sign Last checked Changes
Loading the directory…

* priced at an assumed $1 parity for a known dollar stable other than USDC — the parity is not verified on chain. The gate recognizes USDC, USDT, DAI, USDG, and WETH on the chains it supports.

Times are UTC. “—” means the challenge did not name that field, or the endpoint could not be inspected. The preflight verifies Ethereum, Arbitrum and Base with chain data, plus the Sepolia testnets and Solana mainnet/devnet structurally; other networks show sign BLOCK by design — that is “we cannot verify this chain”, not “this seller is a scam”.

Two verdicts, one reason

Protocol ≠ permission.

A challenge can be perfectly formed and still be unpayable by this gate. The directory keeps those answers apart so a BLOCK never hides a well-formed endpoint, and a PASS never implies a safe seller.

Protocol

Is it well-formed?

Accepts present, scheme exact, amount positive, payee named and not the burn address, resource bound over https, expiry parseable, no duplicate payees on one network. Network-agnostic.

Sign

Should our agent sign?

The same structural payment preflight an agent runs before signing, on this instance's supported networks. A canonical USDC asset, a sane amount, a payee the policy allows.

Watch

What changed?

Status, price, payee, network, and both verdicts are diffed on every refresh. A price jump or a payee swap shows up as a change row, not a silent rewrite.

Limits, stated plainly

Want an endpoint added? Open an issue with the URL, method, and what it sells — entries are added by hand, so the list stays small and honest.

The directory only inspects public endpoints with no authentication. It cannot see paywalls behind an API key, a logged-in session, or a private network. History is process-local unless VERIFY402_DIRECTORY_FILE is set; on a free host that file is ephemeral, so a restart starts a fresh history and re-inspects the seeds. A BLOCK is a refusal to sign, not a verdict on the seller's honesty.

Keep the watch running.

The directory and the inspector are free. The mainnet cutover — where the gate can verify real payments instead of testnet — is funded by one-month sponsorships. No token, no equity, no influence on verdicts.