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

# Creator Fees

Every trade of your token pays you, in HYPE, from the first trade on its curve to every swap in its pool.

## How much

| Where your token trades | Fee per trade | Your share | You earn              |
| ----------------------- | ------------- | ---------- | --------------------- |
| Bonding curve           | 0.75%         | 20%        | 0.15% of curve volume |
| Pool (after graduation) | 0.25%         | 80%        | 0.20% of pool volume  |

Example: if your graduated token trades 100 HYPE of volume in its pool, you earn 0.2 HYPE.

The share is larger after graduation on purpose: it rewards creators whose tokens keep trading.

## Claiming

1. Open **Account**. The **Creator fees** box shows what you can claim.
2. Click **Claim**. The HYPE goes to your Neuriio wallet.

You can claim any time, as often as you like; you only pay gas. Unclaimed fees wait for you in the NeuriioFees contract and never expire.

## FTFs

An [FTF](/get-started/launch-an-ftf.md)'s creator share is split equally between its four members: each claims 25% of it from their own Account panel.

## Fixed shares

The 20% and 80% creator shares are constants in the NeuriioFees contract. Changing them would mean deploying a new contract publicly, and fees already earned stay claimable from the old one.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.neuriio.xyz/trading/creator-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 `build a script that syncs our docs to a CMS` 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.