> For the complete documentation index, see [llms.txt](https://docs.vertigo.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vertigo.sh/for-launchpads/getting-started.md).

# Getting Started

There are three phases in every token launch.

1. Mint the token
2. Create the pool
3. Begin trading

## The Mint

Create your token any way you like. Any token can be used with Vertigo pools.

## The Pool

Once the token is ready to go, deploy a pool with your chosen parameters. Parameters can be as simple or complex as you want. We provide sensible defaults that work out of the box, but feel free to experiment with different liquidity and fee settings to discover what your users like best.

When using a Raydium AMM, you lock your SOL and $TOKEN into the pool.

When using the Vertigo AMM, you simply lock **Magic SOL** and $TOKEN into the pool.

Again, Magic SOL is not actual SOL. It is a variable used to determine the beginning market cap.

## Begin Trading

Make sure your frontend integrates trading on Vertigo pools to allow your users to trade. Trading on a Vertigo pool is simple: You either **buy** or **sell**, with an optional setting for slippage. That's it.&#x20;


---

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

```
GET https://docs.vertigo.sh/for-launchpads/getting-started.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.
