> For the complete documentation index, see [llms.txt](https://documentation.ocoolai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ocoolai.com/app_guides/app/botgem-jiao-cheng.md).

# BotGem教程

> 该app在Apple设备中不支持国区下载，需要切换外区App Store下载（建议美区）。 美区账号注册教程 · 换区教程

## 下载

[官方下载页面](https://botgem.com)

## 配置

> 各平台应用界面差不多，仅用iPadOS和iOS做演示。

* 首次安装并进入app后首先会让你配置APIkey
* `API Key`填写你在ocoolAPI站点生成的秘钥，如果没有或者不会生成可以查看获取秘钥教程
* [去获取秘钥](https://one.ocoolai.com/token)
* `API Sever`填处点击`+`号填入API站地址`https://one.ooo.cool`或`https://one.ocoolai.com`
* 然后确定→点击`继续`即可

## 添加自定义模型

* 点击主界面`设置`
* 点击`对话设置`
* 找到`Model`点击`+`号添加你想用的模型
* 模型名到页价格页选择你想要的模型名抄进去。
* 其余参数可保持默认，也可以按自己需求调整

添加成功后的演示


---

# 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://documentation.ocoolai.com/app_guides/app/botgem-jiao-cheng.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.