> 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/zh/feng-bi-ce-shi-zhi-nan/ru-he-jia-ru.md).

# 如何加入

Mojo 封闭 Beta 版是 **仅限邀请**.

我们是有意把早期范围控制得很小。在这个阶段，反馈质量比注册数量更重要。

***

### 如果你已收到邀请

你会直接收到我们发来的 App Store 邀请（iOS）或 APK 下载链接（Android），以及任何额外的设置说明。

直接前往 [**快速开始**](/zh/feng-bi-ce-shi-zhi-nan/kuai-su-kai-shi.md) 即可开始使用。

***

### 如果你还没有收到邀请

以下是让我们注意到你的方法：

1. **在 X 上关注我们，或加入我们的社区** — 见 [社区与链接](/zh/she-qu-yu-lian-jie.md)。邀请批次会先在那里公布。团队会在聊天中活跃，并留意谁来了。
2. **和当前的 Beta 用户聊聊** —— 一旦活跃的 Beta 用户完成设置，他们就会获得邀请少量新用户加入计划的权限

***

### 邀请如何扩展

当一位 Beta 用户加入、设置好自己的钱包并开始使用 Mojo 后，就会解锁邀请他人的权限。那些新用户在变为活跃后，也可以继续邀请更多人。

这是有意为之：它让社区从内部推动 Mojo 成长，由交易者带来他们认为能从中受益的其他交易者。我们宁愿要 100 位深度参与的交易者，也不要 10,000 个从不执行策略的注册用户。

我们寻找的对象，简而言之，就是已经有想法、并希望用更好的方式把想法付诸行动的交易者。


---

# 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/zh/feng-bi-ce-shi-zhi-nan/ru-he-jia-ru.md?ask=<question>&goal=<user_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.