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

# Shuffle Index fees

## Entry and exit

The more **SHUFFLE** you hold, the lower your fee. The same schedule applies when you deposit and again when you withdraw, including withdrawals into tokens.

| SHUFFLE held                 | Fee per entry or exit |
| ---------------------------- | --------------------: |
| Below 1,000,000              |                    4% |
| 1,000,000 to below 2,000,000 |                    3% |
| 2,000,000 to below 3,500,000 |                    2% |
| 3,500,000 to below 5,000,000 |                    1% |
| 5,000,000 or more            |                    0% |

At 4%, depositing 1 ETH leaves 0.96 ETH after the entry fee, before trading costs. A later withdrawal has its own exit fee.

Thresholds stay fixed as SHUFFLE is burned. The official website applies the fee tier based on your SHUFFLE balance.

## Management fee

The Shuffle Index charges a **3% annual management fee**. Nothing is deducted from your wallet: instead, new XSHUFFLE is created for the team (the initial admin) at 3% of supply per year, diluting existing shares. See [share price and management fee](/how-the-basket-works-technical-section/rebalancing.md#share-price-and-management-fee) for the exact formula.


---

# 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.shuffle.family/fees/xshuffle-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.