> For the complete documentation index, see [llms.txt](https://stonkfun.gitbook.io/stonkfun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stonkfun.gitbook.io/stonkfun-docs/launching/standard-launch.md).

# Standard launch (fee coin)

A standard launch, or "fee coin", gives the creator a locked liquidity position of their own and a Fee Key NFT to claim its trading fees with.

## What you get

|                          | 1% tier (default)     | 2% tier                 |
| ------------------------ | --------------------- | ----------------------- |
| Pool trading fee         | 1%                    | 2%                      |
| Liquidity split          | 50 / 50               | 25 platform, 75 creator |
| Creator earns per trade  | about 0.42% of volume | about 1.26% of volume   |
| Platform earns per trade | about 0.42% of volume | about 0.42% of volume   |

{% hint style="info" %}
Those figures account for Raydium keeping 12% of the pool fee for its own buybacks and 4% for its treasury, leaving 84% distributable to LP positions. Headline figures elsewhere quote the simpler "0.5% or 1.5% of every trade", which is the share of the pool fee rather than of volume.
{% endhint %}

The 2% tier's split is chosen so the platform's take per trade is identical to the 1% tier's. Your higher cut comes out of the trader's fee, not out of the platform's share.

## What happens when you launch

The token is minted with 1,000,000,000 supply and its mint and freeze authorities revoked. Your logo and metadata are uploaded to Arweave. The Raydium pool is created on your chosen fee tier, both positions are seeded in a single transaction, the realised split is verified against the target, and then both positions are locked. One Fee Key goes to the platform and the other to your wallet.

All of that, plus your fee payment and any dev buy, is submitted as a single atomic bundle. It lands together in one block or not at all.

## Choosing the tier

On the launch page the tier is part of the standard fee-model panel. Over the API it is the optional `feeTier` field:

```json
{
  "mode": "standard",
  "feeTier": "2%"
}
```

`"1%"` is the default when omitted, and the response echoes the result as `poolFeePercent`. The field is rejected on reward launches.

## Claiming

Fees accrue on the locked position until you claim them. There is no deadline and no expiry, and unclaimed fees sit safely on-chain.

Claim from the token page, or over the API in three calls. See [Creator fees](/stonkfun-docs/earning/creator-fees.md).

Fees arrive in both tokens of the pair, or in the quote token alone depending on how the pool collects them. See [Fee models](/stonkfun-docs/core-concepts/fee-models.md#where-fees-accrue).

## The Fee Key is yours

The Fee Key NFT is minted directly to the wallet that paid for the launch. It is an ordinary transferable NFT, so you can move it, sell it, or hold it in a multisig. Whoever holds it is who can claim.

{% hint style="warning" %}
Losing the Fee Key means losing the ability to claim that position's fees. The liquidity itself is locked forever either way and cannot be lost, but the fee stream follows the NFT.
{% endhint %}

## Over the API

```js
const prepared = await call('/launches/prepare', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    creatorWallet: creator.publicKey.toBase58(),
    quoteMint: pair.mint,
    name: 'My Token',
    symbol: 'MYTKN',
    mode: 'standard',
    // feeTier: '2%',
    logo,
  }),
});
```

Full walkthrough: [Launch endpoints](/stonkfun-docs/developer-api/launch-endpoints.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://stonkfun.gitbook.io/stonkfun-docs/launching/standard-launch.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.