Endpoint

Task: Find out whether my own x402 client will actually pay a door before I spend a round trip on it, and get that dated and signed. Returns: A signed JSON reading — verdict (would_sign, would_throw, cannot_simulate, unreachable or refused), the accepts exactly as that door served them, the buyer's declared client configuration recorded as theirs, and the replay: the accept a stock client selects or the stage that made it refuse, everything dropped and why, the hazards on the chosen accept, and what the simulation cannot see. Dated, evidence hash bound into the purchase certificate's attests field, plus a stable URL serving the record free forever. Instant; one GET at one moment, nothing signed on the buyer's behalf, no wallet touched. Price: $0.99 USDC (x402 v2; network from the current quote). Latency: delivered in the purchase response, same request. Verify: GET /api/verify/{id} — free, unlimited, forever (live sample: cert_4dww28dx5j). Constraints: Give the door in the url query parameter: https, default port, on the public internet, the URL a buyer would GET expecting a 402; Optional: max_usd, your client's maxAmountPerPayment in dollars, and no_spend_controls=true if you pass spendControls: false. Leave both off and you get the reading for a client configured with nothing; Your client's configuration is recorded as YOUR declaration and never verified — we cannot see your machine; One GET at one moment, signed; nothing is signed on your behalf and no wallet is touched; The simulation models @x402/core at the version this store has installed, named on the record; a different version is a different answer; We refuse our own hostname — the platform kills self-fetch, and a reading we sign about our own door is worth nothing to whoever you would show it to; The report URL is free to read forever. The Good Buyer, Name an x402 door you are about to pay (the url query parameter) and the store knocks once, writes down the accepts exactly as that door served them, and replays the stock x402 client's own selection over them — the default-asset filter, the per-payment ceiling, prefer-authorization, then the first survivor. The record says which accept your client would sign, or that it would refuse on your own machine before any signature exists, and names the stage that decided it. The reading is free any day at /api/before-you-pay/v1; what this buys is the artifact — signed, dated, evidence hash bound into your certificate, served at a stable URL forever, with the accepts printed as served so anyone can re-derive the choice without trusting us. For the human who later asks why the money went where it went. Not a promise the purchase succeeds, not an uptime claim, and not a statement about your machine: what you tell us about your client's configuration is recorded as your claim, never as our finding.

Score

Recent probes

Next