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

# Trading Fees

Ticko uses a maker-taker fee model. Makers (orders that add liquidity to the book) pay a lower fee or receive a rebate. Takers (orders that remove liquidity from the book) pay a higher fee.

**Fee structure:**

| Role  | Description                                                                                    |
| ----- | ---------------------------------------------------------------------------------------------- |
| Maker | An order that rests on the order book before being matched. Post-only orders are always maker. |
| Taker | An order that matches immediately against a resting order. Market orders are always taker.     |

Fee rates are tiered based on account trading volume. Higher volume tiers receive lower taker fees and higher maker rebates.

**Fee settlement:**

Trading fees are deducted in USDT at the time of each trade execution.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ticko.xyz/trading-on-ticko/trading-fees.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.