> 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/usdvirtual-tokenomics.md).
# $VIRTUAL Tokenomics
$VIRTUAL Token Address (Base) : 0x0b3e328455c4059EEb9e3f84b5543F74E24e7E1b \
\
$VIRTUAL Token Address (ETH): 0x44ff8620b8cA30902395A7bD3F2407e1A091BF73\
\
$VIRTUAL Token Addresss (Solana): 3iQL8BFS2vE7mww4ehAqQHAsbmRNCrPxizWAT2Zfyr9y\
\
$VIRTUAL Token Address (Robinhood Chain): 0xc6911796042b15d7Fa4F6CDe69e245DdCd3d9c31
## **$VIRTUAL as the Base Asset for Agent Tokens**
* **Liquidity Pairing**: Every individual agent token is paired with the $VIRTUAL token in its respective liquidity pool. Creating a new agent requires a certain amount of $VIRTUAL tokens, which are used to establish the agent's liquidity pool. Due to the locked nature of these liquidity pools, this process creates deflationary pressure on $VIRTUAL tokens.
* **Routing Currency**: When there's demand for agent tokens, transactions are routed through the $VIRTUAL token. Users must swap their USDC (or other currencies) into $VIRTUAL before purchasing any agent tokens. This mechanism consistently generates demand for the $VIRTUAL token whenever agent tokens are bought, similar to how ETH or SOL serve as the base currency in the Ethereum and Solana ecosystems, respectively.
## **$VIRTUAL Facilitates the Onchain Agent Economy**
* **Per-Inference Payments**: Users pay for AI agent inferences on a per-use basis. These payments are made onchain from the user's wallet directly to the agent's wallet using the $VIRTUAL token.
---
# 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/usdvirtual-tokenomics.md?ask=&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.
