> For the complete documentation index, see [llms.txt](https://docs.premia.blue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premia.blue/the-premia-protocol/key-protocol-features/fee-schedule.md).

# Fee Schedule

## Exchange Layer Fees

{% hint style="info" %}
Maker: A “maker” order is an order that adds liquidity to the order book. A maker order is not executed instantly but is placed on the order book or AMM. \
Taker: A “taker” order is an order that removes liquidity from the order book. A taker order is an order that is executed instantly against other orders upon submission.
{% endhint %}

| Fee Category           | Premia  | Deribit         |
| ---------------------- | ------- | --------------- |
| Maker Fee              | 0.00%   | 0.03%           |
| Taker Fee (AMM)        | 0.30%\* | -               |
| Taker Fee (Orderbook)  | 0.08%   | 0.03%           |
| Settlement Fee (Short) | Free    | Free            |
| Excercise Fee (Long)   | 0.30%\* | 0.015%          |
| Quoting Fee            | Free    | -               |
| Deposit Fee            | -       | Free            |
| Withdrawal Fee         | -       | Variable        |
| Multi-Leg (Combo)      | TBD     | Highest Fee Leg |

For more information on calculations, please see [Concepts>Fees](/the-premia-protocol/concepts/fees.md)

This is the current fee schedule on Premia V3 (active version) and is subject to change anytime.

\*This fee is capped at 12% of the Option's value.


---

# 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.premia.blue/the-premia-protocol/key-protocol-features/fee-schedule.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.