> 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/epiora.md). # Epiora ### A unified execution layer for digital markets Epiora is a trading and execution interface designed to bring fragmented digital markets into a single environment. Today, accessing markets often means moving between different applications, networks, wallets, execution systems, and account models. Spot assets may exist on one network, perpetual markets on another venue, liquidity may be distributed across different protocols, and every platform introduces its own interface and execution flow. Epiora approaches this differently. Instead of treating every protocol or venue as a separate product, Epiora provides a unified workspace where users can discover markets, analyze assets, prepare transactions, and execute across supported venues from one interface. At the center of Epiora is an AI-assisted execution layer that converts natural-language intent into structured actions while preserving an explicit boundary between intelligence and authorization. The agent can understand. The execution layer can prepare. The user remains in control. --- # 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/epiora.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.