> 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/account-and-billing/billing-faq.md).

# Billing FAQ

Answers to common questions about GitBook plans, billing, and payments

Find answers to common questions about trials, payments, invoices, and how GitBook charges for plans, members, and sites.

For full details of each plan, see [Plans](/docs/account-and-billing/plans.md). For how pro-rata charges and true-ups work, see the [Billing policy](/docs/account-and-billing/plans/billing-policy.md). To cancel a plan, see [Subscription cancellations](/docs/account-and-billing/plans/cancelling-a-plan.md).

Browse billing topics:

<table data-view="cards"><thead><tr><th>Topic</th><th data-card-target data-type="content-ref">Learn more</th></tr></thead><tbody><tr><td>Free trial</td><td><a href="/docs/account-and-billing/billing-faq/free-trial.md">Free trials</a></td></tr><tr><td>Payments and invoices</td><td><a href="/docs/account-and-billing/billing-faq/payments-and-invoices.md">Payments and invoices</a></td></tr><tr><td>Site and member costs</td><td><a href="/docs/account-and-billing/billing-faq/plan-and-member-costs.md">Site and member costs</a></td></tr><tr><td>AI credits and usage</td><td><a href="/docs/account-and-billing/billing-faq/ai-credits-and-usage.md">AI credits and usage</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/account-and-billing/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.