> For the complete documentation index, see [llms.txt](https://docs.surged.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surged.fun/launchpad/fees.md).

# Fees

Surged charges three things: a 1 USDC fee to launch, a 1% fee on every trade and, only in the first seconds of a launch, the snipe tax. Creators can add a creator tax of their own. Everything is charged in USDC.

## Where the trade fee goes

Every trade pays 1% of its USDC side, on buys and on sells. That fee is shared out like this:

| Share | Goes to                              |
| ----- | ------------------------------------ |
| 70%   | The token's creator                  |
| 20%   | Buybacks of the top tokens on Surged |
| 10%   | The Surged protocol                  |

The snipe tax is shared out the same way. The 1 USDC launch fee goes to the protocol.

## Creator tax

A creator can add an extra fee on every trade on the curve, from 0% to 10%, and it goes entirely to them. It is fixed at launch and never changes. Once the token graduates it no longer applies: the Uniswap pool only charges its own fee.

## Creator earnings

As a creator, you earn:

* **70% of the trade fee and of the snipe tax** on your token's curve.
* **All of your creator tax**, if you set one.
* **A share of the trading fees of the Uniswap pool** after graduation, shared out the same way, for as long as the token trades.

Your earnings build up in an escrow contract, not in anyone's wallet. Claim them in USDC at any time from the [Earnings](https://surged.fun/earnings) page, with the wallet that launched the token.

## Gas

Arc charges gas in USDC, from the same balance you trade with. It is not a Surged fee and none of it reaches Surged.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.surged.fun/launchpad/fees.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.