> For the complete documentation index, see [llms.txt](https://docs.epiora.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.epiora.xyz/hyperliquid.md). # Hyperliquid Hyperliquid is integrated as a native execution venue rather than being treated as an extension of the Robinhood routing system. Epiora supports two distinct Hyperliquid market classes: ``` Hyperliquid Spot Hyperliquid Perpetuals ``` Both are discoverable through the unified market picker while retaining their own execution semantics. ## Hyperliquid Spot Hyperliquid Spot provides direct spot Buy and Sell execution. Supported markets are dynamically discovered from Hyperliquid's market metadata rather than being restricted to a manually maintained shortlist. The spot execution system supports market and limit order workflows where supported by the venue. A simplified market order flow is: ``` Market selected | v Balance preflight | v Order construction | v Deterministic review | v Live-state revalidation | v User signature | v Hyperliquid execution ``` Market execution uses Hyperliquid's current order model, including bounded IOC execution where applicable. Before a Buy, Epiora validates available quote balance. Before a Sell, Epiora validates available base balance. If material account state changes after the user has reviewed an order, the review is invalidated rather than silently modifying the transaction. ## Hyperliquid Perpetuals Epiora also provides access to Hyperliquid perpetual markets. Users can discover the full supported market catalog instead of a limited set of major assets. The perpetual execution layer supports trading concepts including: ``` Long Short Market Limit Leverage Open positions Close positions Trigger orders Take Profit Stop Loss ``` Where a function has different protocol requirements, Epiora keeps it explicit. For example, leverage is not merely a visual setting in the interface. If the requested leverage differs from live Hyperliquid state, leverage modification becomes its own reviewed execution step before the order is placed. This prevents the interface from displaying one state while executing another. ## Funding Hyperliquid Hyperliquid execution requires funds to reach the appropriate Hyperliquid environment. Epiora integrates the funding path with the broader application while keeping each transaction explicit. One supported route is conceptually: ``` Robinhood Chain USDG | v Relay | v Arbitrum native USDC | v Hyperliquid funding ``` Bridge and funding transactions are separate actions. One approval does not implicitly authorize the next. Epiora does not treat the arrival of funds on an intermediate network as proof that the final destination has been funded. The application confirms the appropriate destination state before presenting the process as complete. --- # 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.epiora.xyz/hyperliquid.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.