Canonical GET (real verify and settle)
Compliant · GET /api/x402/compliant-get · Happy Path
The textbook x402 flow: an unpaid GET gets a 402 with a PAYMENT-REQUIRED challenge, then the server runs a real /verify and /settle against the Radius testnet facilitator.
Explanation
This is the textbook x402 flow. An unpaid request is answered with HTTP 402 and a base64-encoded PAYMENT-REQUIRED challenge; the client signs a permit, and the server runs a real /verify followed by /settle against the Radius testnet facilitator before returning 200 with a PAYMENT-RESPONSE receipt. Use it as the baseline every other endpoint is compared against.
What to watch
Returns 200 with a PAYMENT-RESPONSE header carrying a real testnet txHash.
Facilitator
Settled against the live Radius testnet facilitator (https://facilitator.testnet.radiustech.xyz). A valid payment runs a real /verify and /settle on-chain.
Metadata
- Status: Compliant
- Method: GET
- Price: 0.0001 (100 atomic)
- Responsible party: No fix needed