Account
Get capacity
How many computers the account has against its limit, its RAM and vCPU pools, and how much room of each size it may still add.
GET
Get account capacity
Reads the account’s capacity: its computer limit and its pools, what it uses, what it has added beyond its plan, its self-serve cap, and how many more computers’ worth of room of each size it may add right now. Use it before a purchase to know what fits, and after one to see the new limits.
Capacity is billed to the whole account, so this endpoint needs an account-wide API key. A workspace-scoped key returns
403 with code account_key_required.computers.limit and computers.in_use count plan computers: how many the plan funds, and how many plan computers the account has. Beside them is the account’s one computer limit, which counts plan and hourly computers together, as described in Computers per account:
total, baseline, ceiling and can_raise are null, and raise_available is false, when the limit could not be read.
vcpu.limit is null when the account has no vCPU limit. Each size’s vcpu is what a computer of that size launches with and is billed at.
rates are the per-part prices every shape is billed at, so you can price any computer, or memory, vCPU and storage on their own, without a dry run. computer_usd is 0: computer slots are no longer sold. per_computer_max is the largest any one computer can be. past_xl_allowed is whether this account may add computers past XL (more than 6 vCPU or 32 GB) itself; otherwise they’re set up on request.
can_add is how many more computers’ worth of each size’s memory, vCPU and disk fit under the self-serve cap. It is room, not computers: buying it adds none to total. can_add at 0 means the account has reached its self-serve cap for RAM, vCPU or disk, or for 2xl that past_xl_allowed is false. Ask us and we raise the cap for the account, at the same prices.Authorizations
Response
The account's capacity.