Skip to main content
An organization-level limit caps the organization’s monthly ACU consumption across cloud Devin sessions, Devin Review, Devin Desktop, Windsurf JetBrains, and Devin CLI. Each organization in an enterprise can have its own limit, so administrators can allocate budgets across teams or projects. Manage the limit in Settings > Organizations (see Enterprise billing) or through the API below. The limit applies to total consumption in the current monthly billing window. For example, with a 5,000 ACU limit and 3,000 ACUs already consumed, the organization has 2,000 ACUs remaining. Changing the limit does not reset usage. Organization-level limits and user-level limits are enforced independently. New work is blocked if either the user’s limit or the relevant organization’s limit has been reached.

​
Billing organization attribution

Usage counts toward the limit of the organization it is billed to:
  • Cloud Devin sessions count toward the organization the session runs in.
  • Devin Review counts toward the review’s billing organization.
  • Devin Desktop, Windsurf JetBrains, and Devin CLI count toward the user’s billing organization.
Administrators can assign a user’s billing organization in Settings > Members or through the API. Without an explicit assignment, it resolves to the first organization the user can access through direct membership or an identity provider group assignment. A user’s billing organization also determines which local agent controls apply to them. To assign a billing organization through the API, use the user settings endpoint. Its billing_org_id field remains supported:

​
Organization endpoints

Use https://api.devin.ai as the base URL. See ACU limits for authentication and permissions.
These endpoints are in beta (/v3beta1) and are not included in the published OpenAPI specification.

​
Get an organization’s limits

Returns HTTP 200 with the organization’s limit in cycle_acu_limit:
cycle_acu_limit is omitted when no organization limit is set.
Responses may also include deprecated cloud_agent and local_agent fields. Use cycle_acu_limit in new integrations.

​
Update an organization’s limits

Request body — set a limit
Request body — remove the limit
The endpoint returns HTTP 204 No Content on success. Do not include cycle_acu_limit and either deprecated agent block in the same request.

​
Delete an organization’s limits

Removes the organization’s ACU limit, equivalent to setting cycle_acu_limit to null. The endpoint returns HTTP 204 No Content on success. Removing an organization limit leaves user-level limits and your enterprise’s billing terms in effect.

​
Errors

​
Example: set an organization budget

Set a 5,000 ACU limit for an organization:

​
Frequently asked questions

New work billed to that organization is blocked until an administrator raises or removes the limit, or usage resets in the next monthly billing window.
Allow about five minutes for changes to take effect across products. Limit changes are recorded in the enterprise audit log.