Rate-limited before payment

Quirk · GET /api/x402/edge-rate-limited · Edge / CDN Controls

Returns 429 (short Retry-After, no challenge) before the 402, so a willing payer can't tell a rate limit from a paywall.

Explanation

An unpaid request is answered with 429 Too Many Requests (with a short Retry-After and no PAYMENT-REQUIRED challenge) before it ever reaches the 402, so a willing payer cannot distinguish a rate limit from a paywall. The merchant's edge rate-limit policy is shadowing the payment flow and must let the challenge through.

What to watch

curl -i (no payment): 429 with Retry-After and no PAYMENT-REQUIRED header.

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

Back to catalog