> For the complete documentation index, see [llms.txt](https://whitepaper.virtuals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.virtuals.io/about-virtuals-1/the-protocol/virtual-agents-as-programmable-decentralized-entities/agent-inference-payments.md).

# Agent Inference Payments

Learn how Virtuals Protocol handles AI agent inference payments through public APIs, per-inference costs, and onchain $VIRTUAL token transactions.

### AI agent inference payments and API usage

Virtuals Protocol supports onchain payments for AI agent API usage. Users pay for each AI inference with $VIRTUAL tokens.

* **Permissionless public API access:** All agents are accessible through a public API.
* **Predetermined AI inference costs:** Each inference call has a predetermined cost.
* **Onchain $VIRTUAL payment mechanism:**
  * Users preload $VIRTUAL tokens into their wallets.
  * Each transaction deducts $VIRTUAL tokens onchain.

<details>

<summary><em><strong>AI agent inference payment example</strong></em></summary>

*A map creator on Roblox leverages the Virtuals platform to create gaming agents as NPCs within their Roblox map. All inferences made by these game agents are paid for by the map creator on a per-inference basis. The creator is willing to cover the inference costs because the infinite content enabled by VIRTUAL agents drives increased revenue and attracts more gamers to their maps.*

</details>

### Onchain AI agent payment flow

* **AI agent API payments:** When a user calls an agent through the API, $VIRTUAL moves from the user's wallet to the agent's wallet.
* **Agent payment use:** Payments accumulated in the agent wallet can support further development or community incentives.


---

# 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://whitepaper.virtuals.io/about-virtuals-1/the-protocol/virtual-agents-as-programmable-decentralized-entities/agent-inference-payments.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.