AI Gateway now supports team and project spend budgets
AI Gateway can now enforce spend caps across a team, project, or API key, giving agent workloads layered cost controls instead of relying on per-key limits alone.
AI Gateway budgets now cover **team, project, and API key** scopes. Every applicable budget must have room; hitting any limit rejects further requests until the cap resets or is raised.
Set defaults for projects or keys, then add explicit overrides for expensive agents. Use **50%, 75%, and 100% alerts** to catch rising spend before a hard limit interrupts a run.
AI Gateway budgets now cover **team, project, and API key** scopes. Every applicable budget must have room; hitting any limit rejects further requests until the cap resets or is raised. Set defaults for projects or keys, then add explicit overrides for expensive agents. Use **50%, 75%, and 100% alerts** to catch rising spend before a hard limit interrupts a run. Alerts are informational and disabled by default. **BYOK spend is excluded by default**, so enable or account for it separately if the budget must reflect total model usage.
This closes part of the gateway cost-control loop by turning observed spend into scoped warnings and fail-closed caps. It adds an implementation constraint for agents: overlapping team, project, and key budgets can stop a run even when one scope has room. Because alerts require activation and BYOK is excluded by default, teams cannot treat configured caps as complete cost coverage without checking both settings.