# div limits

> What the org holds against what its plan allows — GPUs, containers, seats and storage — and what it has spent this period against its usage limit.

```bash
div limits
div limits --json
```

```text
Free plan
GPUs              2  of 2
containers        3  of 10
seats             1  of 2
storage       12 GB  of 50 GB    as last measured
usage        $41.20  of $500.00  this period, resets 2026-10-01
```

Each line is what the org holds now against the most it may. A line that has reached its limit is printed in mustard, and the next thing that needs more of it is refused: a run that wants a GPU with `quota_exceeded`, a run that wants a container with `container_quota_exceeded`, a write to a volume with `storage_full`.

GPUs and containers count runs and endpoint replicas alike, so an idle endpoint still holds what it holds. Seats count people and open invitations. Storage is what the volumes last measured, which is what the cap is held against.

The usage line is the org's own limit on what it spends in a period, set in the dashboard. It says `no limit` when there is none. Unlike the others, reaching it stops the runs already going, as `limit_reached`. The period is the billing period on Compute Pro and the calendar month (UTC) on Free.

On Free, a last line on stderr says what Compute Pro holds and what it costs. The plan is changed at [divergentlabs.xyz/plan](https://divergentlabs.xyz/plan) and the usage limit at [divergentlabs.xyz/billing](https://divergentlabs.xyz/billing), never from here.

## Flags

| Flag | What it does |
| --- | --- |
| `--json` | print `GET /billing/summary` as the API sent it |
| `--token <key>` | ask about the org this key belongs to |
| `--api-url <url>` | ask this control plane instead |