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

# Hypertrade R2 Overview

Hypertrade R2 Aggregator is a DEX aggregator on Hyperliquid with full support for HyperCore and HyperEVM routing. R2 is the rebuilt generation of the router with improved routing logic. It uses our internal simulation engine to evaluate routes and secure the best executable rate across all liquidity sources, returning a quote on 100% of requests at a 292ms median latency.

R2 optimizes each trade by scanning every available DEX on HyperEVM as well as HyperCore Spot. The router evaluates Hypertrade DEX liquidity alongside all other venues and splits orders across multiple exchanges (multi-market) and multiple intermediate tokens (multi-hop) to secure the best available execution.

Hypertrade R2 currently supports the widest set of liquidity sources on Hyperliquid:

* HyperCore Spot&#x20;
* Hypertrade DEX (v2, v3)
* Hyperswap (v2, v3)
* ProjectX
* Hybra (v3)
* Kittenswap (v3)
* Ramses (v3)
* UltraSolid
* Nest


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ht.xyz/hypertrade-aggregator/openapi.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
