> 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/why-epiora-exists.md). # Why Epiora Exists Financial markets are becoming increasingly composable, but the user experience remains fragmented. A user may need one application to trade tokenized assets, another to access spot crypto markets, another for perpetual futures, another to move liquidity between networks, and several additional interfaces to monitor positions and balances. The underlying systems may be programmable, but the interaction model is still largely manual. Epiora is built around a simple idea: Markets should be fragmented underneath, not in front of the user. The interface should understand where an asset exists, which execution environment it belongs to, what type of market it represents, and which execution path is appropriate. This creates a separation between two layers: ``` User Intent | v Epiora | +-----------------------+ | | Robinhood Chain Hyperliquid | | Spot Spot + Perps ``` Users interact with markets. Epiora handles venue context. --- # 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/why-epiora-exists.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.