> 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/venue-aware-intent.md). # Venue Aware Intent The same asset can exist in more than one market. Epiora therefore does not determine execution venue from the ticker alone. Consider: ``` ETH ``` That intent may correspond to: ``` Robinhood Spot Hyperliquid Spot Hyperliquid Perpetual ``` If the user's wording already defines the market: ``` Buy ETH on Robinhood ``` the intent can resolve deterministically. If the user says: ``` Long ETH 3x ``` the perpetual intent is explicit. If multiple valid spot venues remain possible and no deterministic routing policy exists, Epiora can request clarification rather than silently choosing where the user's funds should be used. Epiora intentionally does not implement automatic cross-venue best execution at this stage. Venue selection remains visible to the user. --- # 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/venue-aware-intent.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.