Verified decision guide
Cursor Spending Controls: Disable or Cap On-demand Usage
Prevent Cursor on-demand charges, understand delayed enforcement and team limits, and keep Cursor Models and Other Models pools separate.
Direct answer
Disable on-demand usage to stop paid continuation
In the Cursor dashboard, turn off on-demand usage if you want requests to stop after included usage is exhausted. On-demand requires explicit opt-in and is invoiced separately from the subscription. If you allow it, set a spending limit for the applicable billing account.
A spend limit is not an instantaneous execution stop. Cursor documents delayed enforcement and a temporary credit for limited overshoot. Raising the limit in the same cycle can make that previously credited usage billable, up to the new cap.
Settings and account scope
- Open the correct personal or team account in the dashboard. Inspect Spending and Billing & Invoices to separate included usage from on-demand charges.
- Disable on-demand to avoid continuation. If you intentionally enable it, edit the spend limit in Spending. “No Limit” removes the cap.
- Check who can change the limit. Teams can restrict editing through Only Admins Can Edit Usage Settings.
| Account | Control scope |
|---|---|
| Pro / Pro+ / Ultra | Personal monthly on-demand limit. |
| Teams | Team cap; reaching it stops on-demand for all members. |
| Enterprise | Team, member and group settings. The highest applicable member limit wins; changing a default does not lower existing overrides. |
| Enterprise with pooled usage | Member limits constrain total usage, not only on-demand. Do not apply personal-plan assumptions. |
If overshoot was credited, leave the limit unchanged or disable on-demand to retain that credit. It is not a permanent refund.
Two pools stay separate
Cursor Models and Other Models are distinct included pools on Pro, Pro+ and Ultra; India Start has Cursor Models only. Exhausting one does not transfer the other into it. Cursor documents selecting Cursor Models as an alternative when that pool still has capacity. Router can consume either pool according to the actual routed model.
On-demand controls govern paid continuation; they do not merge pools or establish equal dollar allowances. Usage resets with the billing cycle without rollover; teams share their cycle date. Pro, Pro+ and Ultra include Tab completions separately. Start does not offer on-demand usage. Disabling paid continuation is not a promise every model remains usable.
Teams/Enterprise third-party requests also incur the Cursor Token Rate, including third-party Auto routing; first-party models are exempt. Do not budget these requests as universally markup-free.
Unknowns
Unknown — undisclosed The reviewed docs do not define separate spend caps for each model pool or an exact enforcement-delay duration. They do not guarantee that every unused pool bypasses an Enterprise member stop. Unknown — account_dependent Inspect your actual plan, routing, overrides and remaining usage. No community-derived included-dollar quota is used here.
Sources and freshness
- Cursor spending limits
- Cursor usage-based charges
- Cursor usage and separate model pools
- Cursor models and pricing
Review weekly and before budget changes; recheck enforcement credits, pool routing, and Enterprise overrides.
For current plans and allowances, see the product guide.