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

# Plans, credits and billing

Zerve's plans, how credits work, and what happens when they run out.

Zerve plans include a monthly allowance of **credits**, Zerve's unit of usage for the agents and compute. For what uses credits and how much, see [How credits are used](/zerve-docs/administration/how-credits-are-used.md).

## Plans

| Plan           | Includes                                                                                                   |
| -------------- | ---------------------------------------------------------------------------------------------------------- |
| **Free**       | 50 credits a month, to get started                                                                         |
| **Pro**        | $25 per user per month, with 250 credits a month. Add-on credits in packs of 250 for $25.                  |
| **Team**       | 500 credits a month per seat. Add-on credits in packs of 500 for $50, with pooled credits across the team. |
| **Enterprise** | Custom plans, with pooled credits and volume discounts. Contact Zerve.                                     |

For current prices and what each plan includes, see [zerve.ai/pricing](https://www.zerve.ai/pricing).

Some models aren't available on the Free plan. See [Supported models](/zerve-docs/agents-in-the-workspace/supported-models.md#models-on-the-free-plan).

## Plan credits and add-on credits

| Credits                  | Roll over? | Notes                                                             |
| ------------------------ | ---------- | ----------------------------------------------------------------- |
| **Monthly plan credits** | No         | They reset each month                                             |
| **Add-on credits**       | Yes        | They never expire, and are shared by everyone on the same account |

When your plan credits run out, add-on credits are used next.

### Auto-recharge

Organizations can turn on **auto-recharge**, which buys more credits automatically when your balance falls below a threshold you set, up to a limit you set. If an automatic purchase fails, you're notified.

## Whose credits are used

When you work in an organization, Zerve decides which credits to use:

| Where you're working                                                     | Whose credits are used                   |
| ------------------------------------------------------------------------ | ---------------------------------------- |
| **An organization on a Team or Enterprise plan that you're a member of** | The organization's credits               |
| **An organization you own**                                              | That organization's plan                 |
| **Anywhere else**                                                        | Your own personal organization's credits |

## Seats

On Team plans, credits belong to the **seat**, not the person. If someone leaves and a new person takes their seat, the seat's remaining credits carry over to them. Removing and re-adding someone doesn't give them a fresh allowance.

Each person uses at most one seat per organization. They're assigned one automatically the first time they use credits there.

## When work stops

Work that uses credits stops when:

* Your plan or seat credits and add-on credits are all used up
* Your subscription payment is overdue
* Your organization has been disabled

Superagents also have their own [daily budget](/zerve-docs/superagents/budgets-and-credits.md), on top of your organization's credits.


---

# 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.zerve.ai/zerve-docs/administration/plans-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.