---
title: "What the account may run, runs and has added, and how many of each size it may still add"
method: GET
path: "/api/account/capacity"
tags: ["account"]
---

# What the account may run, runs and has added, and how many of each size it may still add

`GET /api/account/capacity`

## Request

- Base URL: `https://www.orgo.ai`
- URL: `https://www.orgo.ai/api/account/capacity`
- Auth: HTTP bearer

## Response `200`

computers ({ limit, in_use }: the plan’s count and its computers; total: every computer, plan and hourly; baseline; ceiling: 999 or the account’s own number; can_raise and raise_available), ram_gb and vcpu ({ limit, in_use }; vcpu is the account vCPU pool, with no limit when unmetered), added, self_serve_cap, can_add per size (0 for 2xl unless past_xl_allowed), past_xl_allowed (whether computers past XL, more than 6 vCPU or 32 GB, are the account’s to add and create; false: set up on request), sizes with monthly prices and the vCPU each launches with, rates per term (ram_gb_usd, vcpu_usd, disk_20gb_usd, computer_usd, windows_usd: the per-part prices any shape is billed at) and per_computer_max.

## Other responses

- `401`: Unauthenticated.
- `403`: A workspace-scoped key: capacity needs an account-wide key.
- `429`: Over one of the account's rate limits (rate_limited): `limit` names it, `retry_after` and Retry-After say how many seconds to wait. Limits are per account (the workspace owner when the request acts on a computer or a workspace) and set by its plan (x-rate-limits).

## Changes

- **2026-10-30** `afb6f0ee1aac`: 1 info
  - added the non-success response with the status `429`
- **2026-10-02** `57e3ea6e140b`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/orgo/apis/orgo-api/changes/api/account/capacity/get.md)

---

[API](https://skmtc.dev/orgo/apis/orgo-api.md) - [All operations](https://skmtc.dev/orgo/apis/orgo-api/llms.txt) - [OpenAPI document](https://skmtc.dev/orgo/apis/orgo-api/revisions/e4c1e7379fa5?raw)