> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/credits-and-billing.md).

# Credits & Billing

- [Convai credits](https://docs.convai.com/api-docs/credits-and-billing/convai-credits.md): Find out how Convai credits work, how your balance changes during a billing cycle, and how to estimate the credits a project will use.
- [How Convai credits work](https://docs.convai.com/api-docs/credits-and-billing/convai-credits/how-convai-credits-work.md): Understand what a Convai credit is worth, which parts of a conversation use credits, and how Convai calculates the charge for each turn.
- [Credit balance and billing cycle](https://docs.convai.com/api-docs/credits-and-billing/convai-credits/credit-balance-and-billing-cycle.md): Understand when your plan's credits arrive and expire, which usage alerts Convai sends, and what happens when your credits run out mid-conversation.
- [Estimate credit usage for a project](https://docs.convai.com/api-docs/credits-and-billing/convai-credits/estimate-credit-usage.md): Estimate how many credits your character uses per turn and per month with the Convai credit calculator, so you can choose a plan that fits.
- [How existing subscriptions move to credits](https://docs.convai.com/api-docs/credits-and-billing/convai-credits/existing-subscriptions-and-credits.md): Find out how Convai converts a paid subscription to a credit balance, how many credits you receive, and why your renewal date stays the same.


---

# 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.convai.com/api-docs/credits-and-billing.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.