> For the complete documentation index, see [llms.txt](https://hypurrtrade.app/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hypurrtrade.app/docs/introduction.md). # Introduction Hypurr Trade brings advanced execution to Hyperliquid, inside the interface you already trade on. It is a Chrome extension that upgrades the order form on app.hyperliquid.xyz in place. Same screen, same workflow, nothing new to get used to: everything else stays exactly as Hyperliquid built it. What changes is what the form can do. Instead of working orders by hand, you hand them to an execution engine: peg to the top of the book, show a sliver while working the full size, slice across time or traded volume, trail a stop, fire in waves. {% embed url="" %} A Swarm order working S\&P500-USDC. {% endembed %} ## How it is built * **Non-custodial.** No deposits, no withdrawals. Funds stay in your Hyperliquid account. The agent key you approve can trade but can never move funds. * **Wallet-native.** A wallet signature is your entire login. No email, no password, no tracking. * **Server-side execution.** Algos run on our servers around the clock. Close the tab and they keep working. Each slice reaches the book as an ordinary order, so your working size is never public. Hypurr Trade is an independent tool and is not affiliated with Hyperliquid. --- # 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://hypurrtrade.app/docs/introduction.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.