> For the complete documentation index, see [llms.txt](https://docs.zircuit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zircuit.com/infra/gud-trading-engine-beta.md).

# GUD Trading Engine (Beta)

### What's the Trading Engine?

The Trading Engine is a cross-chain trading infrastructure that aggregates liquidity across multiple blockchain networks and bridge protocols to provide users with the best possible rates for their trades.

#### Key Features

* **Multi-Protocol Integration**: Connects to leading cross-chain protocols like Across, deBridge, and more to ensure competitive pricing
* **Best Quote Aggregation**: Automatically compares quotes across all integrated protocols and returns the most favorable rate
* **Direct Wallet Execution**: Users maintain full custody - trades are executed directly from their wallets without intermediaries
* **Gasless Options**: Integrators can provide users with a gasless trading experience using off-chain EIP712 signatures
* **Universal Token Support**: Trade any token across supported chains with automatic routing and bridging
* **Fee Transparency**: Clear fee structure with customizable integrator fees


---

# 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:

```
GET https://docs.zircuit.com/infra/gud-trading-engine-beta.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.