> For the complete documentation index, see [llms.txt](https://docs.mojo.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mojo.trade/beta-disclaimer.md). # Disclaimer **Please read this before using Mojo with real funds.** *** ### Mojo is actively developed software Mojo ships fast. Features may change, be added, or be removed, and while we work hard to make it reliable, you should expect the occasional bug, edge case, or service interruption. By using Mojo, you accept that: * Mojo may produce unexpected results, including failed orders, missed conditions, or incorrect strategy interpretations * Service availability is not guaranteed * Features and interfaces may change without notice * Your data and history will be preserved across versions, but the experience around them may evolve *** ### Trading involves risk Trading any financial instrument — including cryptocurrencies, derivatives, perpetual futures, and prediction markets — involves substantial risk of loss. You can lose some or all of the funds you trade with. Past performance does not predict future results. You should: * Only trade with funds you can afford to lose * Understand the venues and instruments you're trading on * Use small sizes while you get comfortable with Mojo * Never assume any system, including Mojo, will protect you from losses *** ### Mojo is not financial advice Nothing in Mojo, this documentation, the Mojo website, or any communication from the Mojo team constitutes financial, investment, legal, or tax advice. Mojo is a software tool that executes strategies you design and approve. The decisions are yours. The trades are yours. The outcomes are yours. We are not a registered financial advisor, broker, dealer, or fiduciary. We do not manage your money. We do not make recommendations about what to trade. If you need financial advice, consult a qualified professional in your jurisdiction. *** ### Your responsibility By using Mojo, you confirm that: * You are legally permitted to use the trading venues you connect, in your jurisdiction * You understand that all trading decisions and outcomes are your responsibility * You will not hold Mojo, MINDORIGIN, or its team liable for trading losses, missed opportunities, software bugs, or any other consequence of using the product * You are using Mojo voluntarily and at your own risk *** ### Reporting problems If you encounter a bug, an unexpected outcome, or anything that feels wrong, please report it immediately through the channels in Feedback & Support. Fast feedback helps us protect every other Mojo user. *** *Last updated: October 2026* For the full legal terms, see Mojo's [Terms of Service](https://www.mojo.trade/terms-of-service/) and [Privacy Policy](https://www.mojo.trade/privacy-policy/). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mojo.trade/beta-disclaimer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.