> 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/reference/fees.md).

# Fees

Trading taxes, Quant Pad's own fees and what it costs to launch a coin.

## Trading tax

Every Quant Pad coin has a trading tax, shown on its coin page.

| Launch type | Trading tax                              |
| ----------- | ---------------------------------------- |
| Standard    | 1%                                       |
| Quantum     | 1%, 2%, 3% or 5%, chosen by the launcher |

Standard launches can also opt into an anti-sniper tax: 25% at launch, falling to 1% over the first two minutes.

Meteora keeps its protocol share of the tax, and the rest goes to the coin's creator. For a Quantum coin, the creator is the coin's [well](/quantum-hooks/overview.md#key-terms), so that share is split by its [hooks](/quantum-hooks/fee-modules.md).

## Quant Pad platform fee

Any Quant Pad platform fee on trades and dev buys made through Quant Pad is shown before you sign, as a separate transfer.

## Quantum Hooks protocol share

Quantum Hooks can take a protocol share of each fee pulse before it is split. It is capped at 10% on-chain, and any share is shown before you sign.

## Launch cost

Launching costs about 0.02–0.03 SOL in network fees and account rent, plus any dev buy.


---

# 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/reference/fees.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.