> For the complete documentation index, see [llms.txt](https://docs.useglade.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useglade.org/agents/pay-per-request.md).

# Paying per request with x402

x402 is an open protocol for payments between machines. It is built on HTTP status 402 Payment Required, a code that sat mostly unused for a long time. Glade supports x402 natively, which means an agent account can pay for API calls, compute and other services with no card, no OAuth flow and no prepaid balance to keep topped up. A payment takes about as long as an HTTP round trip.

Robinhood Chain was designed for exactly this kind of user; its stated goal is to let agents trade, swap and pay. On that chain, x402 is the obvious way to handle payments. A service gets one standard way to state its price. An agent gets one standard way to pay it, inline, as part of the request it was making anyway.

## The payment flow


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.useglade.org/agents/pay-per-request.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.