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

# Trading

Buy and sell any Meteora bonding-curve coin with SOL.

Buy with SOL and sell for SOL from any coin page.

## Where your trade goes

* **Before graduation**, trades go to the coin's Meteora bonding curve.
* **After graduation**, trades go to the coin's Meteora DAMM v2 pool.

<figure><img src="https://3333211986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWu2Zj9LCnjL5ul1zbj2X%2Fuploads%2Fgit-blob-1923113f3668dff11aecf9dc3e2ebb5fafb5d832%2Fdiagram-lifecycle.jpg?alt=media" alt="A coin&#x27;s life on Meteora in three steps: it is launched with a dev buy in one transaction, trades on the Meteora bonding curve until the curve fills, then graduates to a DAMM v2 pool whose liquidity is locked forever."><figcaption></figcaption></figure>

## Slippage

Your slippage limit is enforced on-chain. If the price moves past your limit, the trade fails instead of filling at a worse price.

## Finding a coin

You can open any Meteora bonding-curve coin, not only coins launched on Quant Pad. Paste its mint address in the search box.

## Fees on trades

Each coin has a trading tax, shown on its coin page. Any Quant Pad platform fee is shown before you sign, as a separate transfer. See [Fees](/reference/fees.md) for details.


---

# 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://docs.quantpad.company/getting-started/trading.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.