> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentsfleet.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Fleet budgets

> Daily and monthly spending limits for one fleet.

# Fleet budgets

## What it is

A fleet budget limits how much one fleet can spend. The fleet author sets the budget in `TRIGGER.md`.

```yaml theme={"theme":"vesper"}
budget:
  daily_dollars: 5.0
  monthly_dollars: 29.0
```

`daily_dollars` is required. `monthly_dollars` is optional.

## Why it exists

Every workspace under one tenant shares the same credit balance. A fleet budget stops one fleet from draining that shared balance.

The fleet owns its budget. Updating the fleet replaces the limits, and deleting the fleet removes them.

## How it behaves

The daily limit covers a rolling 24-hour window. The monthly limit covers one Coordinated Universal Time (UTC) calendar month.

`agentsfleet` checks the limits before a run and while the run continues. A reached limit blocks new work and stops an active run at its next billing check.

A blocked event does not retry. Raise the limit, update the fleet, and send a new event.

The fleet, memory, and activity stream survive a budget stop. A stopped run has no final result.

## Limits

| Field             | Default        | Unit                         | Valid range                          |
| ----------------- | -------------- | ---------------------------- | ------------------------------------ |
| `daily_dollars`   | None; required | Dollars per rolling 24 hours | More than `$0` and at most `$1,000`  |
| `monthly_dollars` | None           | Dollars per UTC month        | More than `$0` and at most `$10,000` |

An invalid budget blocks fleet installation. A stored budget that cannot be read blocks the next run.

`UZ-RUN-015` marks a budget stop during a run. `UZ-EXEC-015` records the final failure class.

## Related pages

* [Author a fleet](/fleets/authoring)
* [Error codes](/api-reference/error-codes)