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

# Liquidation Fees

When Aevo liquidates a position, the liquidated account pays a liquidation fee on the liquidated quantity. The rate depends on the instrument:

* Tier 1 perpetuals: 1%
* Tier 2 perpetuals: 3%
* Options: 0.5% of index notional, capped at a share of the option's premium

Aevo assigns each perpetual to a tier based on conditions such as global market liquidity and the CEX and DEX availability of the underlying.

The liquidated account also pays the taker fee on the same quantity. Staking discounts reduce the liquidation fee on perpetuals.

#### **Example Scenario**

Symbol: ETH-30DEC22-1500-C\
Type: ETH Call Option\
Underlying: ETH\
Current Price: $2000\
Strike Price: $1500\
Quantity: 1 contract\
Expiration Date: December 30, 2022

User A is short 1 contract of ETH-30DEC22-1500-C, which is in the money. User A's margin falls below the maintenance requirement, and Aevo liquidates the position.

Liquidation fee paid by User A: `0.5% × 1 × $2000 = $10`


---

# 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://www.aevo.xyz/docs/aevo-products/aevo-exchange/fees/liquidation-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.
