> For the complete documentation index, see [llms.txt](https://docs.wheelx.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wheelx.fi/overview/features/multi-router-quote-comparison.md).
# Multi-Router Quote Comparison
Get full visibility into every evaluated route — see quotes side-by-side before you commit.
### How It Works
When you request a quote, the WheelX API doesn't just return one route — it returns **all viable routes** with complete metrics for each, so you can compare and choose with confidence.
1. **Submit a quote request** — Specify your source token, destination token, and amount via the Quote API.
2. **Receive multiple routes** — The API evaluates all available liquidity sources (DEXs, bridges, aggregators) and returns every viable path, each with its full cost breakdown.
3. **AI tags the optimal route** — The AI Router scores every route across Price, Speed, Slippage, Gas, and Liquidity, and marks the best one with an `optimal` tag.
4. **Choose your path** — Use the AI-recommended route, or select any alternative route manually via `select_route`.
> **Multi-Router Quote Comparison is the transparency layer of AI Route Optimization** — while the AI Router automatically selects the optimal path, this feature gives developers full visibility into all evaluated routes and the reasoning behind each selection.
***
### What's Compared
Each route in the quote response includes these metrics:
| Metric | Description |
| --------------------------- | ------------------------------------------------------------------------ |
| **Output Amount** | The exact amount of destination tokens you'll receive |
| **Fee** | Total fees (network gas + bridge fees + DEX fees), broken down by source |
| **Time** | Estimated fill time in seconds, based on current network conditions |
| **Slippage / Price Impact** | Expected price impact based on trade size vs. pool depth |
| **Route Path** | The full execution path (e.g., DEX-A direct, or Bridge → DEX-B combined) |
| **AI Recommendation** | Tag indicating whether the route is optimal, fastest, or lowest-gas |
***
### Two Selection Modes
#### AI Auto-Select (Default)
The AI Router evaluates all routes and automatically executes the one with the highest composite score across Price, Speed, Slippage, Gas, and Liquidity. No manual intervention needed.
#### Manual Select
Developers can inspect all route metrics and manually specify `select_route` to choose a specific path — for example, preferring the fastest route for time-sensitive trades, or the lowest-gas route for cost optimization.
***
### Benefits
* **Full transparency** — Every route's cost, timing, and risk metrics are visible. No hidden fees or opaque routing.
* **Developer control** — Inspect, compare, and manually override the AI's recommendation when your use case demands it.
* **Better decision-making** — See exactly why the AI chose a route. If a slightly slower route yields 0.6% more output, you decide whether the extra wait is worth it.
* **Auditable routing** — Track and log every evaluated route for compliance, reporting, or optimization analysis.
* **Flexible integration** — Use the Quote API's `quotes` array to build custom route-selection UIs in your wallet or dApp.
***
---
# 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.wheelx.fi/overview/features/multi-router-quote-comparison.md?ask=&goal=
```
`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.