> 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/the-epiora-model.md). # The Epiora Model Epiora currently organizes markets around three primary execution surfaces. ``` Epiora Robinhood Spot -> Buy -> Sell Hyperliquid Spot -> Buy -> Sell Hyperliquid Perpetuals -> Long -> Short ``` The important distinction is that Epiora does not pretend these markets are identical. Robinhood Chain spot execution and Hyperliquid execution use fundamentally different infrastructure. Epiora preserves those differences internally while presenting them through a consistent interface. A user can therefore search for an asset globally while every result retains its execution identity. For example: ``` ETH/USDG Robinhood Spot ETH/USDC Hyperliquid Spot ETH Hyperliquid Perp ``` The symbol may be similar. The market is not. Venue identity, market type, execution path, balances, signing behavior, and settlement remain explicit throughout the system. --- # 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/the-epiora-model.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.