> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devin.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Organization-level ACU limits

> Set monthly ACU budgets for Devin organizations, manage limits through the API, and understand how usage is attributed to each organization.

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](https://app.devin.ai/settings/organizations) (see [Enterprise billing](/admin/billing/enterprise#setting-organization-acu-limits)) 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](/admin/billing/user-acu-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](/enterprise/local/controls) apply to them.

To assign a billing organization through the API, use the [user settings endpoint](/admin/billing/legacy-user-acu-limits#user-endpoints). Its `billing_org_id` field remains supported:

```bash theme={null}
curl -X PATCH "https://api.devin.ai/v3beta1/enterprise/users/user_abc123/consumption/acu-limits" \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"local_agent": {"billing_org_id": "org-xyz789"}}'
```

## Organization endpoints

Use `https://api.devin.ai` as the base URL. See [ACU limits](/admin/billing/acu-limits#manage-limits-with-the-v3-api) for authentication and permissions.

<Note>
  These endpoints are in beta (`/v3beta1`) and are not included in the published OpenAPI specification.
</Note>

### Get an organization's limits

```http theme={null}
GET /v3beta1/enterprise/organizations/{org_id}/consumption/acu-limits
```

Returns HTTP `200` with the organization's limit in `cycle_acu_limit`:

```json theme={null}
{
  "cycle_acu_limit": 5000
}
```

`cycle_acu_limit` is omitted when no organization limit is set.

<Note>
  Responses may also include deprecated `cloud_agent` and `local_agent` fields. Use `cycle_acu_limit` in new integrations.
</Note>

### Update an organization's limits

```http theme={null}
PATCH /v3beta1/enterprise/organizations/{org_id}/consumption/acu-limits
```

**Request body — set a limit**

```json theme={null}
{
  "cycle_acu_limit": 5000
}
```

**Request body — remove the limit**

```json theme={null}
{
  "cycle_acu_limit": null
}
```

| `cycle_acu_limit` | Effect |
| - | - |
| Positive integer | Sets the organization's total ACU budget for each monthly billing window |
| `0` | Blocks new usage for the organization |
| `null` | Removes the organization limit |
| Omitted | Leaves the limit unchanged |

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

```http theme={null}
DELETE /v3beta1/enterprise/organizations/{org_id}/consumption/acu-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](/admin/billing/user-acu-limits) and your enterprise's billing terms in effect.

### Errors

| Status | Meaning |
| - | - |
| `400` | A `PATCH` request mixes `cycle_acu_limit` with `cloud_agent` or `local_agent` |
| `403` | The token lacks the required permission |
| `404` | The organization was not found in your enterprise |
| `409` | `cycle_acu_limit` is not available for this organization; contact your account team |
| `422` | Invalid request value; `cycle_acu_limit` must be a non-negative integer or `null` |

## Example: set an organization budget

Set a 5,000 ACU limit for an organization:

```bash theme={null}
curl -X PATCH "https://api.devin.ai/v3beta1/enterprise/organizations/org-xyz789/consumption/acu-limits" \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"cycle_acu_limit": 5000}'
```

## Frequently asked questions

<AccordionGroup>
  <Accordion title="What happens when an organization reaches a limit?">
    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.
  </Accordion>

  <Accordion title="How quickly do limit changes take effect?">
    Allow about five minutes for changes to take effect across products. Limit changes are recorded in the enterprise audit log.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.