> 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/use-cases.md).

# Use Cases

#### Premium infrastructure (RPC, indexing, webhooks)

Wrap existing infra endpoints and charge per call in USDC. Share a stable paid URL with customers and agents; no keys or billing dashboards needed.

#### AI services (generation, retrieval, scoring)

Expose model calls as x402-protected endpoints. Agents can discover and call them via MCP, paying only for what they use.

#### Data APIs (market data, analytics, signals)

Monetize niche datasets with micro-pricing. Provide sample requests and responses so agents onboard themselves.

#### Automation hooks (jobs, triggers, micro-tasks)

Sell small automations or integrations as single-call tools. Great for the long tail of “tiny SaaS” tasks agents need frequently.

#### Community-maintained endpoints

Open-source teams can self-host a paid endpoint to cover costs. Payments settle directly to your wallet; no platform custody.

**Tips:**

* Start with a simple, low price to encourage trial
* Provide good examples and sample bodies
* List in the marketplace for agent discovery


---

# 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/use-cases.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.