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

# Billing

## Key Features

* **View Current Plan:** See details about your current subscription, including the plan name, number of seats, and renewal date.
* **Buy Credits:** Purchase additional credits to use for various services within GenStudio.
* **Upgrade/Change Plans:** Explore different subscription plans and upgrade or downgrade your current plan.
* **Manage Seats:** See the number of member seats available in your current plan.
* **View Model Usage Prices:** Understand the pricing for different AI models.

## Getting Started

To access the billing section, navigate to the "Account" tab and select "Billing".

<figure><img src="/files/rPhboMwReZHAWwUCM11u" alt=""><figcaption><p>Control Center Billing Tab</p></figcaption></figure>


---

# 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.skydeck.ai/control-center/billing.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.