Agent credit allocation lets enterprise Organization admins control how AI credits are distributed across members of their Organization. By setting per-user credit limits, admins can ensure fair usage, prevent runaway consumption, and keep the Organization within its contracted credit pool.
Your Organization has a total credit pool set by your contract, for examplem 10,000 credits per month. By default, all users draw freely from that shared pool. Credit allocation lets you place caps on individual users to reserve credits for others or enforce usage policies.
There are two levels:
- Organization level. The root pool defined by your billing contract. This cannot be changed from the admin UI.
- User level. Limits you set per member, drawing from the Organization pool.
Users without a limit continue drawing from the Organization's unallocated credits. Users with a limit can only use up to their allocated amount, subject to cap type.
Example: Acme Corp has 10,000 credits per month.
- User A: 1,000 credit hard cap
- User B: 2,000 credit hard cap
- All other users: draw from the remaining 7,000 unallocated credits
Go to your Organization Settings → Usage to display:
- Agent Credits Used This Cycle. Total credits consumed by the org so far, with a progress bar toward the contract limit
- Paid Seats Used. Active paid seats compared to your seat limit
- Agent credit usage by members. A table showing each member's credits used, credit limit, current usage percentage, and limit type
Credits reset on the last day of each billing cycle. Unused credits do not roll over at the user level. Instead, they return to the Organization pool. Organization-level rollover follows your existing contract rules, up to 2× monthly.
- Go to Organization Settings → Usage.
- Click Set Limit.
- Specify the number of credits per user and under Limit Type, whether credit limits are flexible or fixed (users can't do any tasks that require credits after they run out of credits).
- To give each user the same allocation, click the Assign Equal Limits button. For individual allotments, click Configure Individually.
- For any user, enter a value in the Credit Limit field.
- Click Save.
Limits take effect immediately. You can also click Distribute Equally to split the Organization's credits evenly across all members.
You cannot allocate more credits to users than the Organization's total available pool.
You can change limits at any time:
- Increasing a limit takes effect immediately. The user gains access to additional credits right away.
- Decreasing a limit takes effect immediately. If the user has already used more than the new limit, they are immediately at or over their cap If they have a hard cap, Bulider blocks additional usage. If instead, they have a soft cap warns them.
- Removing a limit reverts the user to drawing freely from the Organization's unallocated pool.
When a user exceeds a soft cap, a dismissable banner appears in their workspace notifying them that they have exceeded their credit limit and should contact their administrator. Usage continues from the Organization pool.
When a user with a hard cap attempts an AI operation after exhausting their allocation, Builder displays a modal and blocks the operation. AI features remain unavailable until their limit is increased or the billing cycle resets.
Users can display their own credit context within the product:
- If a limit exists, their usage shows as "X of Y credits used (Z%)" with a progress bar. At 80% or more, Builder displays a warning state.
- If no limit exists, their absolute usage shows with no percentage.
Organization admins receive automated email alerts when users approach or reach their limits:
| Threshold | Trigger |
80% | User has consumed 80% of their allocated credits. |
100% | User has reached their credit limit. |
Builder sends notifications once per threshold per billing cycle, not on every usage event.
If you remove a user from the Organization, Builder returns any credits allocated to them to the Organization's unallocated pool and become available to other members immediately.
At the end of each billing cycle:
- All usage counters reset to zero.
- Limits remain configured as-is. No reallocation is needed each month.
- Unused user-level credits return to the Organization pool. They do not roll over at the user level.