Pooled usage

Pooled usage gives your Enterprise team a shared usage pool instead of fixed per-user allocations. Everyone draws from a single committed amount that spans your contract period, so agent usage is available wherever it's needed most.

Why pooled usage matters

Without pooled usage, unused capacity from team members can't be redirected to those doing the most demanding work. Pooled usage removes that constraint, letting your full budget serve your team's highest-priority projects.

Fewer interruptions

Without pooled usage, a developer working on a critical project can hit their cap while other allocations sit unused. With a shared pool, the team's committed budget is available to whoever needs it.

Dynamic spend alerts and limits

Admins can configure team-wide Dynamic Spend Limits that automatically scale with team size. Pair these with Spend Alerts to get email notifications when usage reaches configurable thresholds, so you stay informed without blocking anyone's work.

How it works

Your team commits to a total usage amount for your contract period. All team members share this pool, and usage is tracked cumulatively across the contract term. Dynamic spend limits and alerts give you ongoing governance while the shared pool remains the primary budget constraint.

Key details

• Shared pool: All team members draw from a single committed budget.
• Cumulative tracking: Usage is tracked across the full contract term, not month by month.
• Spend alerts: Get notified when team or member spending reaches thresholds you set. See Spend Alerts for configuration.
• Dynamic limits: Team-wide spend limits that scale automatically as your team grows or shrinks. See Dynamic Spend Limits.
• Admin controls: Only admins can adjust pooled usage settings. See the Dashboard for management tools.