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

# Fees

What Kyte charges, when, and where every fee goes.

{% hint style="success" %}
**In short.** **3%** of the premium on every fill, **0.1%** of the strike on every exercise, and **0.1%** of the WETH side of `$KYTE`/WETH swaps through KyteHook. Cancel and expire are free. Every fee lands in the FeeVault and is split **30% stakers · 20% buy-and-burn · 50% operations**.
{% endhint %}

| Fee                 | Rate              | Charged on                                                                                                                                     | Paid by                                     | Hard cap (immutable) |
| ------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- | -------------------- |
| Premium fee         | **3%** (300 bps)  | The premium, when an offer is filled                                                                                                           | Deducted from what the seller receives      | 10%                  |
| Exercise fee        | **0.1%** (10 bps) | The strike, when an option is exercised                                                                                                        | Deducted from what the strike receiver gets | 1%                   |
| Swap fee (KyteHook) | **0.1%** (10 bps) | WETH side of swaps in the `$KYTE`/WETH Uniswap v4 pool, when WETH is the swap's unspecified side ([details](/protocol/uniswap-v4/kytehook.md)) | Traders in that pool                        | 1%                   |
| Cancel / expire     | Free              |                                                                                                                                                |                                             |                      |

* Fees are **snapshotted per position** at creation. A later fee change only applies to new positions.
* All fees flow to the **FeeVault** in WETH and are split once per epoch:

| Destination     | Share   | Notes                                        |
| --------------- | ------- | -------------------------------------------- |
| `$KYTE` stakers | **30%** | Can never be set below 20%                   |
| Buy-and-burn    | **20%** | Swapped for `$KYTE` on Uniswap v4 and burned |
| Operations      | **50%** | Ops Safe (multisig)                          |


---

# 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.kyte.sh/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.
