> For the complete documentation index, see [llms.txt](https://docs.usexpay.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usexpay.xyz/xpay-overview/pricing-and-tokens.md).

# Pricing & Tokens

#### Simple, per-call pricing

With xPay, you set a price for each request to your endpoint. Callers pay per use - no subscriptions, no manual billing. Payment is verified at request time using the x402 standard.

#### Default: USDC on Solana

* USDC is the default token for its stability and ubiquity.
* Prices are entered in standard units (e.g., `0.05` USDC per call).
* Funds settle instantly to your wallet, with near-zero fees.

#### Other SPL tokens

* You can choose any SPL token by providing its mint address.
* Keep prices simple and clear so users and agents can reason about cost.

#### Tips for setting prices

* Start low to encourage trial and adoption.
* Consider tiered endpoints (cheap “basic” calls, premium “heavy” calls).
* Communicate value: include examples and sample responses.

#### Refunds and failures

* x402 payment is verified before forwarding the request.
* If your upstream returns an error, callers still paid to pass the paywall. Keep your upstream reliable and communicate SLAs where relevant.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.usexpay.xyz/xpay-overview/pricing-and-tokens.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.