> 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/readme.md). # Welcome ### What you'll find here This is the official documentation for Mojo. It covers what Mojo is, how it works, and how to use it during the Closed Beta. * **About Mojo** — what we're building and why * **What Mojo Can Do** — the full capability surface, in one place * **Closed Beta Guide** — how to join, set up, and use Mojo * **Community & Links** — where to find us and talk to the team *** ### ⚠️ Closed Beta is Invite-only Access is limited and invite-only. If you have an invite code, head to [**Closed Beta Guide**](/closed-beta-guide/about-the-closed-beta.md) **→** [**How to Join**](/closed-beta-guide/how-to-join.md). If you don't yet, you can request access through our community channels listed in [**Community & Links**](/community-and-links.md). ⚠️ **Beta software notice.** Mojo is in active development. Features, performance, and availability may change. Trading involves risk. Nothing in this documentation is financial advice. See [**Beta Disclaimer**](/beta-disclaimer.md) before using Mojo with real funds. --- # 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/readme.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.