> For the complete documentation index, see [llms.txt](https://docs.clore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clore.ai/clore.ai/clore.ai-eng-zh/mian-xiang-zhu-ji-fang/advanced/hiveos-integration.md).
# HiveOS 集成
本节展示如何使用 HiveOS 将服务器（rig）添加到 Clore.ai：系统准备、安装 Clore Hosting、应用令牌、启动 flightsheet
### **步骤 1. 创建飞行表并获取令牌**
* 打开 **HiveOS → Workers → 你的矿机 → Create Flight Sheet**.
* 在 **币种** 字段，类型 **clore rentals** 并从列表中选择它。
* 点击 **获取令牌**.
### **步骤 2. 通过 HiveOS 在 Clore.ai 上授权**
* 点击 **获取令牌**后，你将被重定向到 **Clore.ai**.
* 点击 **使用 HiveOS 登录** 并批准登录。
### **步骤 3. 设置价格/时长并将令牌推送到 HiveOS**
* 设置 **价格** 且 **最长租赁时长**.
* 点击 **将令牌应用到 HiveOS** ——令牌将自动填入 **钱包** 字段中，位于你的 HiveOS 飞行表里。
* 返回 HiveOS 并继续完成飞行表。
### **步骤 4. 创建飞行表**
* 在 HiveOS 中，点击 **Create Flight Sheet**.
* 确认 **钱包** 包含你的令牌，并且 **币种：clore rentals** 已被选中。
* 点击 **创建**.
### **步骤 5. 将飞行表应用到矿场**
* 打开 **HiveOS → Farms** 并进入 workers 列表。
* 选择所需的矿场/workers（如有需要可使用 **全选** ）。
* 点击 **Rocket / Apply** 操作。
* 从下拉菜单中选择已创建的 **Flight Sheet** 并点击 **应用到所选项**.
完成。干得好——现在前往 [**Clore.ai**](https://clore.ai/my-servers) 并在 **Marketplace → My Servers**.
### 闲置挖矿
你有两个选项：
* 如果你的服务器已经出现在我们网站上的“My Servers”中并且在线——只需在 HiveOS 中禁用 clore.rental 飞行表，并为闲置挖矿应用你自己的挖矿飞行表。
* 给我们的 clore.rental 飞行表添加第二个矿工——在 HiveOS 中编辑该表，点击 Add miner，配置你的币种/矿池/矿工并保存。当矿机未被租用时，它就会运行。
---
# 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.clore.ai/clore.ai/clore.ai-eng-zh/mian-xiang-zhu-ji-fang/advanced/hiveos-integration.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.
