Skip to main content
Cost-based limits cap usage by monthly spend instead of per-model message counts. They cap what each user and the workspace spend per month and pace usage with weekly and session limits, which message counts can’t do. We recommend switching from request-based limits to cost-based limits for more granular control over usage. Here’s what changes:
  • Before: you capped usage with per-model message limits (Max messages per user, per time window) on each model.
  • After: you cap usage by monthly spend across all models, with per-plan, group, and individual limits and a fallback model.
Per-model message limits keep working alongside cost-based limits, so you can keep them as an extra guardrail.

​
Set up cost-based limits

1. Open usage settings Navigate to Usage and spend limits in your Workspace Settings.
Workspace settings navigation with the Usage section selected
2. Set the workspace spend limit Set a monthly cap for the whole workspace.
Workspace spend limit card with the Adjust limit button
3. Set per-plan limits Under Spend limits per plan, set a default monthly limit for the Standard and Power user plans.
Spend limits per plan with monthly, weekly, and session amounts for the Standard and Power user plans
Then set a Cost limit fallback model, and make sure to add input and output token prices for every model so usage is tracked. Without prices, usage on that model isn’t counted. For these steps and for group and individual limits, see Usage and spend limits.

​
Keep a per-model message limit

Message limits you previously configured per model still apply. You can leave them unchanged, but if you want to rely primarily on cost-based limits, raise them so users don’t hit a message limit before reaching their cost limit. As a baseline for spam protection, we recommend 250 messages per 3 hours per model. 1. Open model settings Navigate to Models in your Workspace Settings.
Workspace settings navigation with the Models section selected
2. Edit each model Open the model’s configuration and set Max messages per user to 250 for 3 hours.
Model configuration with the Max messages per user field and a 3-hour time window
Usage is now capped by monthly spend, with weekly and session pacing, and users fall back to your chosen model when they reach a limit. Counting starts when you configure limits; past usage isn’t counted.
Last updated: June 2026