Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

How credits are used

What uses credits in Zerve, how much models cost, and how to keep spending in check.

Credits are Zerve's unit of usage. Everything that costs Zerve money to run, from the models behind the agents to the compute that runs your code, is measured in credits, so you can track and budget usage the same way whatever you're doing.

Credits and tokens

Credits and tokens measure different things.

  • Tokens are the units models read and write. A token is roughly three-quarters of a word. Model providers charge separately for the tokens you send (input) and the tokens the model writes (output), and output usually costs several times more.

  • Credits are Zerve's own unit, combining model usage and compute into one number.

There's no fixed number of tokens per credit. The same number of credits buys many more tokens on a small, fast model than on a large one, and compute uses credits without involving tokens at all.

What uses credits

Credits are only used for what Zerve runs for you:

What
How it's charged

Model usage

When the agents call a model, you're charged the model provider's price plus 20%

Compute

When your code runs on Zerve's compute, you're charged by the second, based on the compute type

Calls your code makes to external services, such as a market data API, aren't charged as credits themselves. They only use credits through the compute time of the block that runs them.

If your organization uses its own API keys, you pay the model provider directly, and Zerve charges credits for orchestration at a reduced rate.

What a credit is worth

Credits work out at about $0.10 each: add-on credits are sold in packs of 250 for $25 on the Pro plan and 500 for $50 on the Team plan. See Plans, credits and billing.

Working out the cost of model usage

Example. Claude Sonnet 4.6 costs $3 per million input tokens and $15 per million output tokens. A request that sends 10,000 tokens and gets 2,000 back costs:

Step
Amount

Input: 10,000 tokens × $3 per million

$0.03

Output: 2,000 tokens × $15 per million

$0.03

Provider price

$0.06

Plus 20%

$0.072

In credits, at $0.10 each

0.72 credits

A single agent task usually involves many requests like this, as the agent reads, plans, writes code and checks results.

Model prices

These are the provider prices for some commonly used models, with the equivalent in credits (price × 1.2 ÷ $0.10). Prices are per million tokens.

Prices last checked on 2 October 2026. Providers change prices often, so check their pricing pages for current rates: Anthropic, OpenAI, Google Gemini, Amazon Bedrock and OpenRouter.

Model
Input price
Output price
Input credits
Output credits

Claude Haiku 4.5

$1

$5

12

60

Claude Sonnet 4.6

$3

$15

36

180

Claude Sonnet 5.5

$2

$10

24

120

Claude Opus 5.5

$4

$20

48

240

gpt-5.5

$5

$30

60

360

gpt-5.6-terra

$2

$12

24

144

Gemini 3.8 Flash

$0.75

$3.75

9

45

Some prices are temporary. Gemini 3.8 Flash's price, for example, is an introductory one until 31 December 2026.

What affects how many credits a task uses

Factor
Effect

The model

Larger models cost many times more per token than smaller ones

Output

Output tokens cost several times more than input tokens

Reasoning effort

Higher reasoning effort means the model writes more tokens while it thinks, which are charged as output

How much context is sent

Long conversations, large files and big notebooks mean more input tokens with every request

Tokenizers

Models count tokens differently. For example, newer Claude models count about 30% more tokens for the same text.

The mode

Evolve Mode and superagents run several agents at once, so they use more than Ask or Build

Compute

Larger compute, GPUs and longer runs use more

What Zerve does to keep costs down

  • Caching. Zerve reuses the parts of a request that don't change between calls, which providers charge much less for.

  • Limited history. Superagents only send the most recent part of a long conversation with each request, so long-running chats don't get more expensive over time.

  • Time limits. Each agent run stops after 60 minutes.

Controlling spending

Control
What it limits
Where to set it

A single Evolve Mode run. Default 50 credits.

Evolve Mode settings in the composer

A superagent's whole team, per day. Default and maximum 25,000 credits.

The superagent's settings

Model choice

How much each request costs

Auto-recharge

Whether your organization buys more credits automatically when it runs low

Seeing what you've used

Organization admins can see usage in Settings, under Credit Usage and Compute Usage. For a superagent, its page shows credits used today and in the last 24 hours.

When credits run out

When your organization's plan credits and add-on credits are both used up, work that uses credits stops until more are available. See Plans, credits and billing.

Last updated

Was this helpful?