Body-primary GET challenge
Compliant · GET /api/x402/compliant-body-get · Happy Path
Returns a valid x402 challenge in the response body only (no PAYMENT-REQUIRED header). Clients that read the challenge from the JSON body rather than decoding the base64 header must handle this path.
Explanation
A fully compliant GET that delivers the x402 challenge exclusively in the JSON response body — no PAYMENT-REQUIRED header is set. Some server implementations omit the base64 header and rely on the body alone. A compliant client must parse the PaymentRequired object from the response body when the header is absent, sign a permit against the challenge found there, and complete the normal verify/settle flow. Use this alongside compliant-get to confirm your client handles both challenge-reading paths.
What to watch
Returns 402 with the full PaymentRequired object as JSON body. No PAYMENT-REQUIRED header is set. Pay with radius-cli to confirm the body-reading path works end-to-end.
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