> 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/risks.md). # Risks Epiora interacts with external systems whose behavior, availability, liquidity, and security are outside Epiora's direct control. These can include: * blockchain networks * smart contracts * decentralized exchanges * bridges * RPC providers * market-data providers * wallet infrastructure * Hyperliquid * Robinhood Chain * AI model providers Transactions involving digital assets can fail or result in financial loss. Quotes can become stale. Liquidity can change. Networks can become congested. Third-party systems can become unavailable. AI-generated interpretation can also be incorrect. Users should independently review transactions before authorizing them. ## Experimental Software Epiora is evolving software. Features, integrations, supported markets, interfaces, routing behavior, and infrastructure may change as the system develops. The presence of a market in Epiora does not constitute: ``` financial advice investment advice an endorsement a recommendation a guarantee of liquidity a guarantee of execution ``` Users remain responsible for the transactions they authorize. --- # 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/risks.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.