# $VIRTUAL Tokenomics

$VIRTUAL Token Address (Base) : 0x0b3e328455c4059EEb9e3f84b5543F74E24e7E1b \
$VIRTUAL Token Address (ETH): 0x44ff8620b8cA30902395A7bD3F2407e1A091BF73\
$VIRTUAL Token Addresss (Solana): 3iQL8BFS2vE7mww4ehAqQHAsbmRNCrPxizWAT2Zfyr9y

## **$VIRTUAL as the Base Asset for Agent Tokens**

<figure><img src="/files/F8rjOPHCQdzkzaGGfTQU" alt=""><figcaption></figcaption></figure>

* **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: 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:

```
GET https://whitepaper.virtuals.io/about-virtuals-1/usdvirtual-tokenomics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.