Separate opt-in product · service-wallet purchases
A 402 response is not proof that customers can buy.
Test the actual purchase: authorize a bounded payment, verify settlement on Base, and observe the paid JSON response. Get a transaction reference and evidence—not a launch certification.
5 USDC per case: one test purchase, public-code diagnosis and one separately requested post-fix retest. Each target purchase is capped at 1 USDC, included in the service fee. No additional customer debit.
Daily monitoring: one prepaid 5 USDC credit per purchase check, at most once every 24 hours. Stops on failure, ambiguity or exhausted credits. No subscription or automatic wallet charge.
Supported now: public HTTPS GET, synchronous JSON, x402 v2 exact EIP-3009 native USDC on Base. Concrete patch candidates: public Node/Express code only, inspected without execution. No browser checkout, target POST or MCP purchasing.
Checking operational availability…
Get a free quote
This makes an unpaid GET request. It does not sign or pay.
The browser does not pay. Send this request with an x402-capable client only after approving the 5 USDC fee. Keep the idempotency key private and reuse it for recovery, not a new payment authorization.
Read your case or monitor
Use the receipt's bearer token. It stays in this page only; it is not saved to browser storage or put in a URL.
Creating or buying a credit does not activate a monitor. Resuming requires a fresh quote and explicit consent. Pausing cannot revoke an already signed authorization. No missed-run catch-up.
What the evidence proves
Payment, settlement, response delivery and configured JSON assertions are separate outcomes. A confirmed transaction with an unobserved response is not a successful delivery. Public code findings are hypotheses until deployed and retested. Three confirmations are not full chain finality.