> 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/guan-yu-mojo/shen-me-shi-mojo.md).

# 什么是 Mojo

**Mojo 是一体化的智能体交易操作系统。**

**使用品味模式投资。**

***

### Mojo 是什么

* 一个将你的想法付诸执行的个人交易智能体
* 在任何操作执行前先供你审阅的系统
* 面向永续合约、现货和预测市场的跨平台层
* 一个可检查每一条信号、每一个决策和每一个动作的工具

### Mojo 不是什么

* 一个问答聊天机器人，或一个需要你不断用新命令驱动的 Telegram 机器人
* 一个跟单交易产品
* 一个信号订阅或新闻驱动的交易工具
* 一个托管策略市场
* 一个“AI 替你交易”的黑箱
* 一个绑定单一交易场所的交易所原生机器人


---

# 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/guan-yu-mojo/shen-me-shi-mojo.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.