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

# Sandbox concurrency limits

> Read sandbox concurrency limits alongside admission policy, current usage, capacity restrictions, and reset times.

Before starting a batch, check sandbox concurrency limits to see how much room remains for new work. A funded account can still receive an admission refusal:

```bash theme={"theme":{"light":"github-light","dark":"github-dark-default"}}
bead limits
```

The native operation is `GET /v1/limits`.

## What the response contains

| Field | Use |
| - | - |
| `resources` | Organization machine, CPU, and memory usage and ceilings. |
| `policy` | Effective start windows, shape limits, saved-template limit, and batch policy. |
| `windows` | Current start counts and reset times. |
| `shapes` | Current use of CPU/memory shapes. |
| `batch_limits` | Reported batch admission limits. |
| `burst_enabled` | Whether paid extra starts are enabled. |
| `saved_templates` | Current saved-template count. |

The public pricing catalog also publishes admission tiers and hard batch maxima. `GET /v1/pricing` is the live source for that catalog and rates. Per-request enforcement remains authoritative.

## Other limits

Fleet requests have a hard maximum of 10,000 machines; swarms 256; forks 20. Your effective policy, aggregate quota, funds, and capacity can allow fewer. Large fleets use asynchronous status polling; see [Create fleets](https://docs.bead.run/parallel/fleets.md).

The estimator accepts up to 256 machines per bounded estimate. This is an estimator input bound, separate from fleet creation limits.

Trial accounts have [additional restrictions](https://docs.bead.run/platform/trial-credit.md). [Machine sizes](https://docs.bead.run/machines/sizes.md) define resource capacities; availability depends on placement and live capacity.

## Errors and what to do

A limit rejection includes `error_code`, a named `limit`, `maximum`, `usage`, `reset_at` when applicable, and `next_action`.

Start windows use fixed UTC minute, hour, and day boundaries. Reset times are Unix seconds. Honor `Retry-After` when present. Resource exhaustion may have no clock-based reset: pause or delete work, reduce the request, or wait for capacity to be released.

Paid bursting can extend start allowances with consent. It does not bypass other admission checks. See [Paid extra starts](https://docs.bead.run/platform/burst.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.