Restrict HTTP methods

Every paywall declares the HTTP methods it accepts. Requests using any other method are rejected before payment is considered.

Supported methods

GET, POST, PUT, PATCH. You must select at least one method per paywall.

API shape	Methods to enable
Read-only data API	`GET`
Inference or agent tool	`POST`
Idempotent updates	`PUT`
Partial updates	`PATCH`
RPC-style endpoint that accepts both	`POST`, `GET`

Cost discipline. A POST paywall won’t accidentally charge for a GET health-check.
Security. Methods you don’t explicitly allow can’t be used to call your origin through Proceeds.
Predictability. Clients see a consistent interface — they know exactly which methods are paid.

Edit the paywall and toggle methods. The change takes effect immediately. Existing payments for previously-allowed methods remain valid.

Restricting methods does not affect routes elsewhere on your origin — only the route protected by this paywall.