> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/documentation/zh/zhang-hu-yu-ji-fei/billing-faq.md).

# 计费常见问题

关于 GitBook 套餐、计费和付款的常见问题解答

查找有关试用、付款、发票，以及 GitBook 如何对方案、成员和站点收费的常见问题解答。

有关每个方案的完整详情，请参阅 [套餐](/docs/documentation/zh/zhang-hu-yu-ji-fei/plans.md)。有关按比例收费和补缴调整的运作方式，请参阅 [计费政策](/docs/documentation/zh/zhang-hu-yu-ji-fei/plans/billing-policy.md)。如需取消方案，请参阅 [订阅取消](/docs/documentation/zh/zhang-hu-yu-ji-fei/plans/cancelling-a-plan.md).

浏览账单主题：

<table data-view="cards"><thead><tr><th>主题</th><th data-card-target data-type="content-ref">了解更多</th></tr></thead><tbody><tr><td>免费试用</td><td><a href="/docs/documentation/zh/zhang-hu-yu-ji-fei/billing-faq/free-trial.md">免费试用</a></td></tr><tr><td>付款和发票</td><td><a href="/docs/documentation/zh/zhang-hu-yu-ji-fei/billing-faq/payments-and-invoices.md">付款和发票</a></td></tr><tr><td>站点和成员费用</td><td><a href="/docs/documentation/zh/zhang-hu-yu-ji-fei/billing-faq/plan-and-member-costs.md">站点和成员费用</a></td></tr><tr><td>AI 额度和使用情况</td><td><a href="/docs/documentation/zh/zhang-hu-yu-ji-fei/billing-faq/ai-credits-and-usage.md">AI 额度和使用情况</a></td></tr></tbody></table>


---

# 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://gitbook.com/docs/documentation/zh/zhang-hu-yu-ji-fei/billing-faq.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.