Cacheable paid response (shared cache)

Quirk · GET /api/x402/edge-cacheable-paid · Edge / CDN Controls

Sends the paid 200 publicly cacheable, so a shared edge serves paid content to unpaid clients on the same URL.

Explanation

The paid 200 is sent publicly cacheable, so a shared edge cache stores the protected content and serves it to unpaid clients requesting the same URL — a complete paywall bypass at the CDN. Paid responses must be private and no-store; the merchant owns the cache-control configuration on its origin and edge.

What to watch

curl -i: the paid 200 carries public, max-age — a paywall bypass via the CDN.

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