> For the complete documentation index, see [llms.txt](https://docs.midasmarkets.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.midasmarkets.xyz/trading/relay.md).

# Relay

Relay is the cross-chain and EVM route in Midas for supported bridges, EVM swaps, and Hyperliquid funding paths.

* **Cross-chain routes** — Relay can move assets between supported chains when the desired output is not on the same chain as the source funds.
* **EVM execution** — Relay supports EVM-side routes where Midas has an explicit source chain, token address, and destination.
* **Settlement tracking** — Asynchronous routes are tracked by request ID so the UI can reconcile completion or failure.

## When Midas uses Relay

Midas uses Relay when a trade or funding action needs a cross-chain route, an EVM-chain route, or a bridge into a destination such as Arbitrum for Hyperliquid funding.

## Address safety

Relay routes should use explicit token addresses from the UI or resolver. Symbol-only routing can select the wrong asset, especially on chains with multiple variants of the same symbol.

## USDC variants

USDC is tracked per chain. Polygon native USDC and USDC.e, wallet USDC, and protocol account USDC are not interchangeable in every flow.


---

# 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.midasmarkets.xyz/trading/relay.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.