> For the complete documentation index, see [llms.txt](https://monoprotocol.gitbook.io/monoprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monoprotocol.gitbook.io/monoprotocol/architecture/routing-overview.md).

# Routing Overview

In most cases, when using the Toolkit, applications specify a high-level intent, which is then translated into the actual payload on the Toolkit side and provided to the client ready for signing. Routing in a chain-abstracted intent includes:

1. Which chains are optimal to spend from, given the user's balance is distributed across chains
2. Whether bridging is required to perform an intent, or if it can be executed on the same chain
3. What is the minimal bridging amount required to perform an intent
4. Which solver/bundler provides the best execution price
5. Whether a paymaster is needed or if the user pays for gas from their own account

Note that some optimizations from the list are work in progress and will be delivered soon.

The application does not need to worry about any of these - they are optimized on the Toolkit side. The routing system automatically:

* **Analyzes** user's Mono Balance distribution across all supported chains
* **Determines** optimal execution path considering liquidity, fees, and timing
* **Accounts** for MEV risks and selects best execution timing
* **Coordinates** cross-chain operations with atomic settlement guarantees


---

# 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://monoprotocol.gitbook.io/monoprotocol/architecture/routing-overview.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.