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 adds enforceable cost governance above routing: overlapping team, project, and key budgets can stop an agent even when its model route remains healthy. It makes budget hierarchy, alert enablement, and BYOK inclusion part of production reliability planning, since alerts do not prevent overruns and default accounting may omit external-key spend.