> 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/capital-formation-layer/pre-buy-tokens-for-ai-agent-launches.md).

# Pre-buy Tokens for AI Agent Launches

### Pre-buy tokens before an AI agent launch

The free Pre-buy module lets founders purchase up to 100% of total token supply during creation. It enables founder token purchases before public trading opens.

***

### How the Pre-buy token module works

Pre-purchased tokens are:

* Transparently disclosed in the Agent Launch Page tokenomics section
* Subject to a default one-month cliff and 12-month linear vesting schedule
* Visible to the community before token trading opens

Pre-buy can help founders stabilize early token markets, prevent sniping, and signal conviction through direct participation.

***

### Pre-buy token vesting

The default vesting schedule has a one-month cliff and 12 months of linear vesting.

Founders can adjust these vesting parameters before launch. Tokenomics remain transparent for participants.

***

### Pre-buy and Automated Capital Formation

If [Automated Capital Formation](/about-virtuals/capital-formation-layer/automated-capital-formation.md) is active and founders self-purchase above $2 million FDV at TGE, corresponding ACF tokens are reclassified as Team Allocation. They are not distributed immediately.

This prevents early founder token purchases from accelerating capital release.

***

### Pre-buy restrictions and token launch relaunches

Once the Agent Card is live, teams cannot use Pre-buy without relaunching the AI agent.

To add Pre-buy after the Agent Card is deployed, teams must cancel the existing token launch and create a new one. This cancellation and relaunch is available until one day before the scheduled launch. Module fees are not refunded.


---

# 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://whitepaper.virtuals.io/about-virtuals/capital-formation-layer/pre-buy-tokens-for-ai-agent-launches.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.