> For the complete documentation index, see [llms.txt](https://docs.yad.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yad.finance/knowledge-base/basics/what-is-the-fee-structure.md).

# What is the fee structure?

The YAD platform does not charge any fees on its DEX transactions. However, the YAD DEX-Router directs these transactions through other DEXs like Uniswap, Curve, SushiSwap, 1inch, etc., which can charge fees. The quoted amount provided by the YAD widget includes these fees as part of the total cost.

## How does YAD makes revenue?

YAD earns revenue from keeping a positive slippage on swaps. It is important to note that we start taking it on swaps with a total amount exceeding $200. On smaller amounts, the positive slippage goes to the user completely.

{% hint style="info" %}
To learn more about positive slippage and slippage in general, check out [this page](/knowledge-base/basics/what-is-slippage.md).
{% endhint %}


---

# 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.yad.finance/knowledge-base/basics/what-is-the-fee-structure.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.