You can now cap how much of your enterprise’s monthly included AI credits a cost center can use. This is available through the REST API today. Management in the cost center settings UI is coming soon.

Editor’s note (July 1, 2026): Clarified that this currently only applies to the REST API.

Your Copilot licenses come with monthly included AI credits that pool together across your enterprise. This included usage pool is exhausted before any additional usage is spent. Without a control in place, one cost center can spend credits during that phase that another cost center’s licenses paid for. An AI credit pool stops a cost center from using more included AI credits than its own assigned Copilot Business and Copilot Enterprise licenses fund, so each group stays within what it paid for and your chargeback boundaries hold.

An AI credit pool is separate from a cost center budget. The cap governs the included usage pool of AI credits, limiting how much of the shared pool a cost center can draw. A cost center budget governs the metered phase, capping charges after the pool is exhausted. You can use both on the same cost center.

You toggle the AI credit pool on when you create or edit a cost center containing at least one user or enterprise team. GitHub calculates the pool limit automatically from the licenses assigned to that cost center and adjusts it as you add or remove licenses, so you never set or maintain a number yourself. You can also decide what happens when a cost center reaches its cap: block further included usage or let it continue as additional spend if your enterprise allows overages.

This is available for Copilot Business and Copilot Enterprise on GitHub Enterprise Cloud and supports the enterprise teams and cost center user-level budgets releases. Together they make up GitHub’s initial suite of spend controls for AI usage at scale.

To learn more, see Budgets for usage-based billing and About cost centers.

Join the discussion or submit feedback within GitHub Community.