> For the complete documentation index, see [llms.txt](https://docs.peach.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peach.ag/documentation/arc/launchpad/core-features/trading-before-and-after-graduation.md).

# Trading before and after graduation

The Aggregator supports trading Launchpad tokens in both stages:

* **Before graduation:** buy and sell through the Aggregator, with trades routed to the Launchpad bonding curve (`LAUNCHPAD`).
* **After graduation:** liquidity moves to a Uniswap V4 pool. Once that pool is created, continue buying and selling through the Aggregator, with trades routed to Uniswap V4 (`UNISWAPV4`). The original Launchpad bonding curve no longer accepts trades.

Graduation closes curve trading. V4 trading becomes available after pool creation and route availability; a graduated flag alone does not guarantee that migration has finished.

**Recommended:** omit `providers` or pass `[]` so the API selects available providers. If your application intentionally restricts routes to these two sources, pass `providers: ["LAUNCHPAD", "UNISWAPV4"]`. A filter of only `["LAUNCHPAD"]` excludes the V4 pool after graduation.

Use `await arc.getAvailableProviders()` to discover provider identifiers. Provider filters apply to both Direct Allowance and delegated Permit2 Witness flows. Route availability still depends on the token pair, liquidity, and API indexing.

Integration examples with Arc Aggregator SDK:[Quickstart](/documentation/arc/aggregator/quickstart.md)


---

# 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.peach.ag/documentation/arc/launchpad/core-features/trading-before-and-after-graduation.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.