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

# Fees

Find out why Demex is one of the cheapest Perp DEX to trade on.

Three main types of fees may be charged on Demex.

1. [**Trading Fees**](/trade/fees/trading-fees.md): All executed trade pays a commission. This fee can be reduced by [staking SWTH](https://guide.dem.exchange/trade/fees/trading-fees). Trades also earn large [trading fee rebates](https://guide.dem.exchange/trade/fees/carbon-credits) (e.g. Demex Credits) to offset trading fees.  
2. [**Network Fees**](/trade/fees/network-fees.md): Most actions on Demex require a nominal network fee (<$0.01) for using the underlying network ([Carbon](https://carbon.network)) that the DEX runs on. The fee is paid as consideration to the decentralized network of validators that validate every transaction (e.g. order) placed on Demex.
3. [**Deposit & Withdrawal Fees**](/welcome/deposits-and-withdrawals.md): When depositing or withdrawing tokens from other blockchains, network fees of the external blockchain need to be paid to execute the deposit or withdrawal transaction. This is based on the external blockchain and is not controlled by Demex.&#x20;


---

# 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://guide.dem.exchange/trade/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.