Set per-user budgets on AI Gateway
AI Gateway can now cap each user's aggregate spend across attributed API keys and app tokens, giving unattended coding agents a hard cost boundary.
AI Gateway now supports **per-user dollar limits** across attributed API keys and app tokens. Requests are rejected at the limit; resets can be daily, weekly, monthly, or disabled, with alerts at **50%, 75%, and 100%**.
Set a default allowance for every user, then override it for heavy agent users. Production or shared keys should be attributed to the team, and CLI management requires **Vercel CLI 59.6.2+**.
AI Gateway now supports **per-user dollar limits** across attributed API keys and app tokens. Requests are rejected at the limit; resets can be daily, weekly, monthly, or disabled, with alerts at **50%, 75%, and 100%**. Set a default allowance for every user, then override it for heavy agent users. Production or shared keys should be attributed to the team, and CLI management requires **Vercel CLI 59.6.2+**. User limits stack with API-key, project, and team budgets, so any applicable cap can block a request. BYOK spend is excluded, and older keys remain team-attributed unless rotated.
Per-user limits turn shared gateway budgeting into an enforceable allocation mechanism for individual agent users, with configurable resets and threshold alerts. This narrows cost governance from team or project totals to attributed usage, but its stacked caps can reject requests unexpectedly unless operators model every applicable limit. BYOK exclusion and legacy team attribution leave important spend outside this control.