> 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/how-it-works/bridging.md).
# Bridging
#### Cross-Chain Execution
WheelX enables seamless cross-chain transactions by integrating multiple bridge protocols directly into its routing system. Instead of relying on a single bridge, WheelX continuously evaluates different options and selects the most efficient route based on real-time conditions.
In practice, a cross-chain transaction may involve several coordinated steps, such as swapping into a bridge-compatible asset on the source chain, transferring it across chains, and then swapping into the desired token on the destination chain. All of these steps are automatically combined and optimized into a single execution flow, so users don’t need to manage them manually.
To ensure reliability and efficiency, WheelX connects with leading cross-chain infrastructure providers. The routing engine continuously monitors factors like bridge performance, fees, and execution conditions to determine the optimal path for each transaction.
At the same time, WheelX maintains a strong focus on security and user ownership. The protocol is fully non-custodial, meaning users always retain control over their assets. Funds are not locked within the system, and every execution path is selected with both safety and efficiency in mind.
---
# 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/how-it-works/bridging.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.