Set the organization's spend budget
Set or replace the ceiling. Requires organization owner or admin.
When the budget is reached, new MCPJam-billed work — chat turns, eval runs, computer starts — is refused for the whole organization until the window resets or an owner or admin raises the cap. Work already in flight finishes, and running computers keep going until they hibernate.
capUsd is stored as whole credits (1 credit = 1 cent), so it is rounded to the cent; the response reports what was kept. Changing the cap mid-window does not reset the spend counter, and does not re-announce a threshold the organization was already told about.
Authorizations
MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.
Path Parameters
ID of the organization, from GET /organizations.
Body
Response
The stored spend budget.
An organization's ceiling on MCPJam-billed spend for the current billing window. Amounts appear in both USD and credits (1 credit = 1 cent); the credit figures are what the ledger actually stores.
The ceiling in USD. null means uncapped.
The same ceiling as the ledger stores it.
Whole percents of the cap that notify owners and admins. Reaching the cap always notifies, whether or not 100 is listed.
MCPJam-billed spend so far in this window, in USD.
The same spend as the ledger counted it.
Start of the current billing window (epoch ms). Team and enterprise organizations run on their own subscription cycle; everyone else on the UTC month.
When the window resets and the counter returns to zero (epoch ms).
Thresholds already announced this window. Each fires once per window.
When the cap was reached this window, or null.
When the budget was last changed (epoch ms).
The smallest budget the platform accepts.
The largest budget the platform accepts.
False for a personal organization, which cannot have a budget.

