> 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-overview/quickstart.md). # Welcome to Hypertrade **Hypertrade is a native on-chain DEX** (v2 + v3) **and aggregator** built for Hyperliquid, designed around a trader-friendly UI/UX that prioritizes speed, structure, and simplicity. Swap tokens instantly, manage liquidity positions without leaving the pool interface, and track all activity in the built-in transaction history. Your active pools are always sorted at the top for quick access. Alongside the DEX, **Hypertrade includes a routing engine** – the only aggregator on Hyperliquid with any-to-any token swaps across HyperEVM and HyperCore. No other aggregator lets you swap anything on HyperEVM to anything on HyperCore and back. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ht.xyz/hypertrade-overview/quickstart.md?ask=&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 `build a script that syncs our docs to a CMS` 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.