> 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/maker-and-taker-fees.md).

# Maker and Taker Fees

The concepts of "taker" and "maker" are crucial to understand. These terms don't relate to whether you're buying or selling (the side of the trade), nor whether you're opening or closing a position. Instead, they refer to how your order interacts with the existing order book:

1. Taker Orders:
   * A "taker" is someone who "takes" liquidity from the market.
   * You become a taker when you place an order that immediately executes against an existing order in the order book.
   * This typically happens when you place a market order or an aggressive limit order that crosses the current bid-ask spread.
   * Taker orders are often described as "aggressive" because they actively remove orders (liquidity) from the book.
   * Example: If the current best ask price is $100, and you place a buy order at $100 or higher, you're a taker.
2. Maker Orders:
   * A "maker" is someone who "makes" or provides liquidity to the market.
   * You become a maker when you place a limit order that doesn't immediately execute and instead sits in the order book waiting to be filled.
   * These orders add depth to the market and are typically seen as passive.
   * Example: If the current best ask price is $100, and you place a buy limit order at $99.50, you're a maker.


---

# 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/maker-and-taker-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.