Skip to main content
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

Authorization
string
header
required

API key authentication. Get your key at orgo.ai/workspaces

Response

The account's capacity.

plan
string

The account's plan, such as startup_v2.

computers
object

limit and 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, plan and hourly computers together: total, baseline, ceiling, can_raise and raise_available.

ram_gb
object

The account-wide RAM pool and what its computers use.

vcpu
object

The account vCPU pool and what its computers use. limit is null when there is no pool limit.

added
object

What the account has added beyond its plan.

self_serve_cap
object

The most the account may add on its own. Past it, purchases return 403 capacity_cap; ask us and we raise it for the account.

can_add
object

How many more computers' worth of each size's memory, vCPU and disk the account may add now, under its cap. It is room, not computers. 0 for 2xl unless past_xl_allowed.

max_per_request
integer

The most computers' worth one purchase may add (500).

sizes
object[]
terms
enum<string>[]
Available options:
monthly,
yearly
windows_available
boolean
has_subscription
boolean
renews_at
string<date-time> | null
scheduled_reduction
object | null
rates
object

Per-part prices for each term: every shape, and parts on their own, are billed at these.

per_computer_max
object

The largest any one computer can be.

past_xl_allowed
boolean

Whether this account may add computers past XL (over 6 vCPU or 32 GB) itself. Otherwise they are set up on request.