> 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/learn-more/faq.md).

# FAQ

#### Do I need to change my API code?

No. Point xPay at your existing HTTP endpoint and set pricing. We handle x402 payment verification and proxying.

#### What tokens are supported?

Any SPL token by mint address. USDC on Solana is the default/recommended.

#### How do agents discover my tools?

Your endpoints become MCP tools under `/mcp/:username`. xPay also provides a marketplace listing.

#### When do I get paid?

Per-request, instantly, after payment verification. Funds settle directly to your wallet.

#### Can I control auth to my upstream API?

Yes. Provide optional custom auth headers that xPay will add when forwarding requests.

#### How are prices represented?

`paymentAmount` is a decimal in the token’s standard units (e.g., `0.05` USDC).

#### Is there a sandbox?

Use low `paymentAmount` and local backend. Prefer a dedicated Solana RPC (`SOLANA_RPC_URL`) during testing.


---

# 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/learn-more/faq.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.