> For the complete documentation index, see [llms.txt](https://info.tilox.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.tilox.cc/execution/routes.md).

# Routes

Understand the action path selected for execution.

## Routes

An execution route is the sequence of actions used to complete a strategy. A route can include one or more compatible protocol interactions.

### Route considerations

| Consideration | Why it matters                                                         |
| ------------- | ---------------------------------------------------------------------- |
| Assets        | Inputs and outputs affect exposure and transaction requirements.       |
| Steps         | More steps can require additional approvals or transactions.           |
| Liquidity     | Available liquidity can affect price and execution.                    |
| Networks      | Cross-network activity can introduce bridge and timing considerations. |
| Fees          | Network, protocol, bridge, or platform costs may apply.                |

Route selection behavior and live route availability are not yet specified. Review the presented route before authorizing transactions.


---

# 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://info.tilox.cc/execution/routes.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.