> 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/taster-ji-hua/how-to-become-a-taster.md).

# 如何成为 Taster

成为 Mojo Taster 需要什么条件——三项要求以及审核如何进行。

所有申请者都要经过官方审核。只有通过的人才会成为 Taster；提交申请并不意味着你就是大使。

> 🎟️ **从这里开始：** [**申请 Taster 计划 →**](https://ljphvb2e0v84.jp.larksuite.com/share/base/form/shrjpib9E1Z00Ft2LQXPgyKJ4xe)
>
> 你也可以在 [Taster 计划网站](https://www.mojo.trade/taster.html).

***

### 三个要求

要被接受，你需要满足 **这三项全部**。没有面试。

#### ① 带来真实用户

你的 2 个邀请码被使用，且受邀用户完成了入金和首次交易。

> 我们看重的是入金和真实交易，而不是注册量，这样一批空账号就不会算数。

#### ② 在你的渠道发布内容

至少 **2 条原创 Mojo 帖子** 发布在你的 X 账号或社群中，并带上 **#Mojo** 和 **@MojoAI\_HQ**，并获得真实互动——每条帖文大约需要 1,000+ 浏览和 5+ 条真实评论。

#### ③ 帮助官方渠道增长

通过可追踪来源，带动真实用户关注 Mojo 的官方 X 账号或加入官方 Telegram。

***

### 审核流程

1. [**提交申请表**](https://ljphvb2e0v84.jp.larksuite.com/share/base/form/shrjpib9E1Z00Ft2LQXPgyKJ4xe)**.** 我们会联系你，带你了解整个计划，并解答问题。
2. **体验 Mojo。** 你会收到下载链接和产品指南。
3. **完成这三项要求** 并提交我们发送给你的简短表单。
4. **审核。** 提交内容会按到达顺序，根据完成度和质量进行评估。
5. **公布。** 新 Taster 会在 Mojo 的官方 X 账号上公布，并附带专属的 Mojo Taster 徽章。

新 Taster 会按 **滚动方式公布，大约每两周一次** ——不会一次性全部公布。如果这轮没入选，继续努力；你会在下一轮被纳入考虑。

***

### 一旦加入

请查看 [Taster 手册](/zh/taster-ji-hua/taster-handbook.md) ，了解每个月的要求、你能获得什么，以及内容规范。


---

# 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/taster-ji-hua/how-to-become-a-taster.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.