> For the complete documentation index, see [llms.txt](https://fordex.gitbook.io/fordex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fordex.gitbook.io/fordex/trade-terminal/multi-router-aggregation.md).

# Multi-Router Aggregation

## Multi-Router Aggregation

The **Multi-Router Aggregation Engine** ensures that traders always get the **best execution price** when swapping tokens.

#### **How It Works**

* Fordex scans liquidity across multiple DEXs (Uniswap V2/V3, PancakeSwap, Curve, Balancer, etc.).
* It compares routes in real time and calculates:
  * **Effective Price** (after slippage + tax).
  * **Gas Costs** (execution cost).
* The route with the **lowest total cost** is selected automatically.

#### **Benefits**

* Avoid overpaying on low-liquidity pools.
* Reduce slippage on volatile pairs.
* Access deeper liquidity by splitting routes if necessary.


---

# 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://fordex.gitbook.io/fordex/trade-terminal/multi-router-aggregation.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.