Vercel AI Gateway adds per-user dollar budgets across API keys and app tokens

Vercel has added per-user spending limits to its AI Gateway, giving teams a direct way to cap how much each individual member can spend on model usage. According to the company's changelog, a user budget covers every API key attributed to that person as well as their app tokens, and once the limit is exhausted the gateway rejects new requests until the budget resets or someone raises it.

How budgets are configured

The controls live in the Users view on the Budgets page, and there are two types. A default budget applies separately to every member without a custom limit, including people who join the team later, so each individual receives a distinct allowance rather than drawing from one shared pool. A custom budget overrides the default for a single person, and removing it returns them to the default.

Refresh periods default to monthly, but Vercel says they can be changed to daily or weekly, or set never to reset. Email alerts are also supported, notifying users when they hit 50%, 75% or 100% of their allocation.

Layered on top of existing limits

User budgets do not replace the API key, project and team budgets Vercel already offered. A request has to stay within every budget that applies to it, and tripping any one of those limits blocks it, so a per-user cap acts as an additional constraint rather than a substitute for coarser controls.

Attribution matters here. API keys are credited to the user who created them by default, so Vercel advises reassigning keys that belong to production applications or other shared workloads to the team from the API Keys page, keeping their spend out of the creator's budget. Keys created before this feature shipped were attributed to the team for backwards compatibility, meaning teams that want existing usage tracked at the user level will need to rotate to new keys.

One further exclusion: spend through Bring Your Own Key (BYOK) credentials does not count toward user budgets.

CLI and permissions

The latest Vercel CLI exposes the same controls. After running vercel upgrade, a default user budget can be set with vercel ai-gateway budgets defaults set user --limit 50 --refresh-period monthly, and a per-member override with vercel ai-gateway budgets set user [email protected] --limit 100 --refresh-period monthly. Members can be identified by email address, username or user ID.

Team owners manage user budgets by default, and they can delegate the ability by granting other members an AI Gateway Budget Manager permission from team member settings.

Why it matters

Vercel positions the feature as a guardrail for autonomous coding agents and other workloads that spend money without a human watching, where one runaway session can drain a team's shared allocation. Per-user caps push spend control down to the level of individual people, where accountability usually sits in an organisation, while layered enforcement keeps key-, project- and team-level limits intact. Two caveats are worth flagging: legacy keys sit outside the scheme until they are rotated, and BYOK traffic is invisible to it, so teams relying on either will still need complementary tracking.