> 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.md).

# Launchpad

Integrate token launches, trading and fee claims on Arc Testnet and Arc Mainnet.

Use the TypeScript SDK to create tokens, trade on bonding curves and manage fees on Arc Testnet and Arc Mainnet. Holder Fee Sharing is optional.

### Launch lifecycle

Create a token → trade on its bonding curve → complete Graduation → trade in the Uniswap V4 pool through Peach Aggregator. Graduation is the transition from curve trading to pool trading.

An initial or final buy can complete the first Graduation step. V4 pool creation is a separate, permissionless transaction.

### Start here

* [Overview](https://docs.peach.ag/documentation/arc/launchpad/overview) — the protocol lifecycle and integration overview.
* [Quickstart](https://docs.peach.ag/documentation/arc/launchpad/quickstart) — install the SDK, configure a client and execute your first transaction.
* [Core Features](https://docs.peach.ag/documentation/arc/launchpad/core-features) — creation, trading, Graduation, revenue and recovery.
* [Changelog](https://docs.peach.ag/documentation/arc/launchpad/changelog) — release features.


---

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