Skip to main content
Organization-level limits cap the total ACU usage attributed to one organization, per product category: Each organization in an enterprise can have its own limits, allowing administrators to allocate budgets across teams or projects. You can also manage organization-level Devin limits from the web app; see Enterprise billing. Organization-level limits are independent of user-level limits — a request is blocked if either has been reached. See ACU limits for authentication, permissions, and PATCH semantics shared by all endpoints on this page.

​
Billing organization attribution

Each user’s Local Agent usage is counted toward a billing organization, which determines which organization’s Local Agent limit applies. The billing organization is resolved in this order:
  1. Explicit assignment: An administrator sets billing_org_id on the user’s ACU settings through the API.
  2. Automatic resolution: If there is no explicit assignment, the first organization the user can access through direct membership or an identity provider group assignment is used.
A user’s primary billing org also determines which local agent controls apply to them. Explicit billing organization assignments are managed with the legacy user endpoints — the billing_org_id field there is not deprecated, only the limit field is:

​
Organization endpoints

​
Get an organization’s limits

Response body
An agent block is omitted when no limit is set for that product category.

​
Update an organization’s limits

Request body — set Local Agent and Devin limits
Request body — clear only the Local Agent limit Set local_agent to null without changing the Devin limit:
The endpoint returns HTTP 204 on success.

​
Delete an organization’s limits

This clears both the Local Agent and Devin limits for the organization.
The endpoint returns HTTP 204 on success.

​
Example workflows

​
Set up organization-level Local Agent limits

Set an organization-level budget for combined Devin Desktop, Windsurf JetBrains, and Devin CLI usage:

​
Set up organization-level Devin limits

Set a Devin cloud session budget for an organization:

​
Frequently asked questions

Billing organization attribution determines which organization’s Local Agent limit includes a user’s Devin Desktop, Windsurf JetBrains, and Devin CLI usage. If it is not assigned explicitly, it resolves automatically to the first organization the user can access.
New work is blocked on the products in that category for the organization’s users — Local Agent products for the local_agent limit, Devin cloud sessions for the cloud_agent limit — until the limit is adjusted or usage resets in the next monthly window.