Playground
Abstract
vet402 verifies x402 payment endpoints by actually using them: probing the payment wall (L0), and above that, paying the listed price with its own funds and recording whether the payment settles (L1) — every receipt public, transaction hash included. This page lets you run the L0 step yourself, live, against a real listed endpoint, and then follow the same evidence trail a paying agent would read. pass / fail / unverified are defined measurements, not opinions — definitions here.
1. Pick a listed endpoint
2. Read the measurement
The probe runs the moment you press the button — this is a live HTTP request to the endpoint's payment wall, not a cached result.
3. The evidence trail
L0 is the free layer: the 402 challenge itself is the observable. The layer above it, L1, is a real purchase — vet402 pays the listed price with its own funds and records whether the payment settles, receipt by receipt, transaction hash included. Every receipt for this endpoint: x402.twit.sh/tweets/search. The downstream decision surface reads the same ledger:
4.What you just ran
The probe approached the endpoint with the HTTP method its catalog entry declares, and read the wall's answer: did it return 402 with a parseable accepts array, and does that answer agree with what the catalog promised (price, asset, network, payee)? That is L0 — no payment attached, the challenge itself is the observable. It is the same measurement the Observatory performs on the whole public catalog daily. Demo probes are not written into the public register — the daily cadence stays clean.
L1 receipts on each endpoint's page are real purchases made under a hard daily budget, and failures are published with the same weight as successes — State of x402 carries the aggregate numbers.