> 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/agents-in-the-workspace/evolve-mode/credit-caps.md).

# Credit caps

Limit how much a single Evolve Mode run can spend.

Every Evolve Mode run has a **credit cap**: the most that run can spend. It stops a large or unexpectedly complex task from using more credits than you intended.

## Setting the cap

Set the cap in the Evolve Mode settings in the agent composer.

| Detail      | Value                                           |
| ----------- | ----------------------------------------------- |
| **Default** | 50 credits                                      |
| **Minimum** | More than 0. A run can't start with a cap of 0. |

## When a run reaches its cap

When a run reaches its cap, it **pauses**, rather than stopping and losing its work. You can then:

* **Resume** it, to let it carry on
* **Discard** it, to stop

## Other limits

The credit cap works alongside two other limits:

* Each agent run times out after **60 minutes**.
* Every run also draws on your organization's credits. If your organization runs out, the run can't continue, whatever its cap. See [Plans, credits and billing](/zerve-docs/administration/plans-credits-and-billing.md).

For what uses credits and how they're calculated, see [How credits are used](/zerve-docs/administration/how-credits-are-used.md).


---

# 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/agents-in-the-workspace/evolve-mode/credit-caps.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.