> For the complete documentation index, see [llms.txt](https://docs.slinky.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slinky.network/payments/how-x402-requests-work.md).

# How x402 requests work

x402 lets an HTTP resource return a price as part of the request flow. The client can pay for one call without creating a subscription or keeping a prepaid balance with the individual provider.<br>

<figure><img src="https://4263197242-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtVM0qTwW1SmwvBaQwlXq%2Fuploads%2FvMLM5LPu7XLlLykqUz5k%2Fimage.png?alt=media&amp;token=5cd2f022-42df-4399-9aaa-e6d9c8b0deaf" alt=""><figcaption></figcaption></figure>

1. The client sends a normal request to a discovered resource.
2. The resource returns HTTP `402` and a `PAYMENT-REQUIRED` header.
3. The client checks the amount, network, asset, destination and expiry.
4. A compatible wallet creates the authorization.
5. The client repeats the request with `PAYMENT-SIGNATURE`.
6. The resource returns the result and can include `PAYMENT-RESPONSE`.

Paying for one resource does not grant permission to read more conversation history, call a second paid resource or submit an onchain action. Each additional operation needs its own policy decision.