> For the complete documentation index, see [llms.txt](https://docs.openkey.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openkey.cloud/clarify.md).

# 售后须知

* 平台有专业客服，提供 12/24 \* 7 售前咨询和售后保障服务。
* 考虑到 API 商品的特殊性，无法二次销售，售出概不退款；若遇不可抗力平台无法继续提供服务，将妥善制定方案以弥补用户损失。
* 本站接口价格可能随美元汇率、市场供需关系波动，接口如有涨价/降价将通过官网发布公告（一般提前24小时左右会发布公告），恕不另行通知。价格一旦变动，即按新价格计算接口消耗。


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openkey.cloud/clarify.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.