> 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/builders-hub/genesis-launch/modes.md).

# Modes

When user creates a new agent on the Virtuals platform, there are two phases: **Prototype** and **Sentient**.

## Standard Launches

### [Prototype Agents](https://app.virtuals.io/prototypes)

All agents initially created start off as Prototype agents. The creator pays 100 $VIRTUAL to set up a bonding curve for the agent token, paired with $VIRTUAL. During this phase, the agent token can be traded on the Virtuals platform or other supported trading platforms/bots. However, there is no liquidity pool set up for the agent. The 1% trading tax for prototype agents is allocated to the protocol treasury. In order for the agent to "graduate", 42k $VIRTUAL tokens are required in the bonding curve.

### [Sentient Agents](https://app.virtuals.io/sentients)

When an agent graduates, it becomes "sentient" and a liquidity pool is established for the agent token (e.g. on Uniswap for Base tokens, and Meteora for Solana tokens). Users can trade the tokens on the Virtuals platform or other DEXes/aggregators/bots. The 1% fee is split between the agent creator (70%) and ACP incentives (30%).


---

# 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/builders-hub/genesis-launch/modes.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.