Skip to main content
GET
Storage Usage
Shows how much storage an account, or a team you belong to, uses against its plan, and what uses it. MCP: storage_usage. CLI: rip storage. Who pays for what:
  • A workspace counts toward its owner, the account or the team, whoever wrote its files.
  • Standalone artifacts count toward the account that owns them.
  • Bundles count toward the account that owns them, every version.
Every kept version and every table row counts, not just the current content. Anything in the trash counts too, until it is purged: deleting frees no space, emptying the trash does. Sizes are in bytes; the plan limits are decimal (1 GB = 1,000,000,000 bytes). Auth: Authorization: Bearer tr_...

Query parameters

Example response

Response fields

When storage is full

A write that would take the payer past its plan’s limit is refused with 403 STORAGE_LIMIT_REACHED, and nothing is stored. That covers every write that adds bytes: publishing or uploading an artifact, a new version, a fork, appending, upserting or updating table rows, a CSV import, moving your files into another payer’s workspace, and deploying a bundle or a new bundle version. Writes that add nothing are never refused: deleting, restoring from the trash, purging, deleting a version, pruning history and deleting rows.
To make room: prune old versions, or delete files and empty the trash (deleted files count until then; this read’s largest[] shows what holds the most, trashBytes what the trash holds), keep data that grows in a table rather than re-publishing a file, or move up a plan. The refusal names the next step for the payer’s plan: Pro from Free (a team with no plan subscribes to Team), a team on the Team plan from Pro (a team of one is fine; the account’s own workspaces stay on it), and Enterprise from [email protected] after Team. It carries billingUrl when that step is bought on the Billing page and the payer is your own account or team. An agent should tell its person rather than delete anything on its own. An internal member of a workspace someone else pays for gets the numbers, with “This workspace’s owner’s storage is full” and a remedy for the owner. Some writers get only the code and one sentence, without the numbers: a workspace’s external member (“This workspace’s owner is out of storage. Ask them to free space or upgrade.”), and someone writing another account’s file through a team share (“This file’s owner is out of storage. …”). Their refusal carries no billingUrl: it is not their bill. Over MCP the four fields, and billingUrl when present, are in the failure’s details; the CLI keeps them in its error details and prints the link as Billing: <url>.

Errors

The operator dashboard reads the same usage through GET /v0/operator/storage.