Bỏ qua đến nội dung chính
Back to home
AI Tech 2 min read

Vercel Introduces Per-User Spend Limits on AI Gateway

Vercel now enables teams to set USD spending limits for individual users on AI Gateway, helping control costs from autonomous coding agents and protecting team budgets.

Tier 2 · sources 52% confidence Reviewed
Sources vercel.com

Vercel has added per-user budget limits to its AI Gateway platform, enabling engineering teams to enforce individual USD spending caps for each team member rather than relying solely on shared team-wide limits.

Granular Cost Controls for Autonomous Workloads

According to Vercel's announcement, this mechanism applies a spending ceiling across all API keys and app tokens associated with an individual's account. Once spending hits the configured threshold, AI Gateway automatically rejects any new incoming requests until the budget cycle resets or the limit is increased. This feature is designed to control runaway expenses from unattended automated tasks such as coding agents, while preventing a single user from consuming the entire team's budget.

Budget Configurations and Alerting

The system supports two user budget configurations: default budgets and custom budgets:

* Default Budgets: Apply individually to members who do not have a dedicated configuration, including newly onboarded team members. * Custom Budgets: Assigned to specific individuals and explicitly override the default threshold.

Both budget types default to a monthly reset cycle, with additional cadence options including daily, weekly, or never resetting. The system also delivers automated email alerts when spend reaches 50%, 75%, and 100% of the allocated limit.

Multi-Tier Enforcement and Backward Compatibility

Vercel emphasized that per-user budgets do not replace existing budget tiers configured at the API key, project, or team levels. Every request routed through AI Gateway must satisfy all applicable limits simultaneously; violating any single constraint will cause the request to be blocked.

Newly created API keys are attributed to the creator by default, though ownership can be transferred to the team level for shared production workloads. Legacy API keys created prior to this update remain assigned to the team to preserve backward compatibility. Notably, costs incurred through Bring Your Own Key (BYOK) configurations are excluded from per-user budget quotas.

CLI Integration and Access Management

To configure limits via the command line, teams must update to Vercel CLI version 59.6.2 or later, which supports identifying members by email, username, or user ID. Team owners can manage these rules directly or delegate administrative privileges by assigning the 'AI Gateway Budget Manager' role in team governance settings.