The short version (June 2026): Cursor's paid plans no longer hand you a fixed number of requests. Each tier includes a dollar-denominated usage pool (Pro $20, Pro+ $60, Ultra $200 a month), and a separate, heavily subsidized "Auto" mode that stays unlimited on every paid plan. You burn the pool only when you manually pick a frontier model like Claude Opus or run Max Mode. Once the pool is gone, you either fall back to unlimited Auto, or, if usage-based pricing is on, keep going and pay overage at raw API rates with no markup. That last sentence is where the surprise bills come from.
Cursor's pricing is one of the most misread billing models in the AI coding space, and the confusion is structural, not a failure to read the docs. The plan looks like a flat $20 subscription. Underneath, it behaves like a metered API account with a prepaid balance. People sign up for the first mental model and get billed under the second. The threads write themselves: a developer on r/cursor went from a $28 month to a $500 charge in three days, and the top comment was simply "I signed up because the pricing made sense, and they just changed it overnight." This is a guide to what actually happens to your money, model by model, so the bill stops being a surprise.
What changed, and why the old mental model breaks
Until June 2025, Cursor metered you in "fast requests": a fixed count of premium actions per month, then you waited or paid a flat per-request overage. That model was easy to reason about. You knew you had, say, 500 fast requests, and you watched the counter.
In June 2025 Cursor replaced fast requests with usage-based credit pools tied to actual API token costs. Now every paid tier includes a dollar amount of model usage instead of a request count. The number of "requests" you get is no longer fixed, because a request against a cheap model and a request against Claude Opus cost wildly different amounts of the same pool. The same $20 might buy you hundreds of mid-tier requests or a few dozen frontier-model sessions. The counter people used to watch is gone, replaced by a balance that drains at a rate you set every time you pick a model.
What each plan includes, exactly
| Plan | Price | Included model-usage pool | Auto mode | Tab completions |
|---|---|---|---|---|
| Hobby | Free | Limited trial usage | Limited | Limited |
| Pro | $20/month | ~$20 of API model usage | Unlimited | Unlimited |
| Pro+ | $60/month | ~3x the Pro pool | Unlimited | Unlimited |
| Ultra | $200/month | ~20x the Pro pool | Unlimited | Unlimited |
| Teams | $40/user/month | Per-seat pool, org usage reporting | Unlimited | Unlimited |
Two things in this table do the heavy lifting. First, tab completions are unlimited everywhere and never touch the pool, so the autocomplete experience most people associate with Cursor is effectively free. Second, Auto mode is unlimited on every paid plan and is the single most important fact for keeping your bill flat. We will come back to it.
One nuance worth flagging so you are not caught out reconciling figures: Cursor's own pricing materials describe the included usage on higher tiers as somewhat larger than the sticker price (the Pro+ and Ultra pools are quoted above the subscription amount), because Auto-mode usage draws from a separately subsidized pool priced below standard API rates. The safe way to read it: the pool you can spend on manually-selected frontier models is roughly your subscription price, and Auto on top of that is generous and unlimited.
Auto versus picking a specific model
This is the whole game. Cursor lets you either let it choose the model ("Auto") or pin a specific one (Claude Opus, a GPT-5 variant, and so on), optionally with Max Mode for a bigger context window.
- Auto mode routes each request to a cost-efficient model Cursor manages, priced at heavily discounted internal rates (roughly $1.25 per million input tokens and $6 per million output for the managed pool). It is unlimited on paid plans and does not drain your included credit pool. If you never leave Auto, your bill is your subscription price, full stop.
- Manually selecting a frontier model bills against your pool at that model's real token rate. Opus-class models cost several times more per token than the Auto pool, so a handful of long Opus sessions can move more of your balance than a full week of Auto work.
- Max Mode widens the context window, which means more input tokens re-sent on every turn. It is a multiplier on top of model choice: same model, bigger context, faster drain.
The mechanism behind the drain is the same one that makes every agentic tool expensive: an agent re-sends the entire growing conversation plus tool outputs on each turn, so cost climbs faster than turn count. We unpack that arithmetic in the agentic token-cost measurement guide. In Cursor terms, a long Opus session in Max Mode is the combination that turns a $20 plan into a three-figure invoice.
Why bills surprise people
Three patterns produce nearly every shock invoice, and all three are visible in the community threads.
1. Pinning a frontier model by default. The cheapest way to drain credits is to manually select Opus or a top Claude model for every task and forget to switch back. Auto would have handled most of those tasks for free. One r/cursor user reported their per-call Opus cost climbing from about $0.08 to $1.40 over ten days for identical work as context and thinking budgets grew. The model selector is a spending dial most people treat as a quality dial.
2. Usage-based pricing left on, with no cap. When your included pool is exhausted you reach a fork: stop and fall back to unlimited Auto, or keep going on the model you pinned and pay overage. If usage-based pricing is enabled and you have not set a spend limit, the second path is the default and the overage bills automatically in arrears. The $28-to-$500 poster had usage-based pricing enabled without realizing the pool had a floor under it.
3. Reading "unlimited" as unlimited-everything. Auto is unlimited. Frontier models are not. Developers who budgeted for a flat $20 because the marketing said unlimited were reading the unlimited that applies to Auto and tab completion, not the metered pool that applies to manual model selection. The words are accurate; the scope is narrower than it reads.
How to track and cap it
The fix is not "use Cursor less." It is to make the meter visible before the invoice arrives.
- Set a spend limit in Settings then Billing. This is the single highest-value action. With a configured limit, Cursor stops billable overage at your ceiling instead of letting it run; without one, overage accrues automatically. Pick a number you would not flinch at and treat it as a circuit breaker.
- Default to Auto, escalate deliberately. Make Auto your resting state and switch to a pinned frontier model only for tasks that genuinely need it (subtle multi-file refactors, long-context reasoning). Switch back when done. This keeps the pool for the work that earns it.
- Watch the usage dashboard, not the invoice. Cursor exposes spend in-app. The teams who never get surprised are the ones who glance at the burn mid-month, while there is still time to change behavior, rather than discovering it on the statement.
- For teams, roll usage up per person and per repo. The per-seat number on a Teams plan hides a distribution that usually spans an order of magnitude across engineers. The policy layer for that, tiers, auto-throttle, chargeback, is in the per-engineer cost-cap playbook.
Where Cursor sits among the other tools
Cursor's credit-pool meter is one of four common shapes in AI coding tools. Windsurf uses daily and weekly quotas, Claude Code uses rolling time windows, and GitHub Copilot moved to per-token credits on June 1, 2026. The cheapest tool for you is whichever meter matches how you actually work, which we lay out in the four-meter comparison, and the Copilot specifics are in the Copilot usage-based billing breakdown. Cursor's pool model is the most flexible (you decide where the budget goes) and, for the same reason, the most exposed to a few heavy frontier sessions draining a month's balance in days.
The neutral layer underneath all of this
Whether you are a developer trying to keep one Cursor seat predictable or a team running Cursor, Copilot, and Claude Code side by side, the underlying need is the same: a normalized view of usage and cost that does not depend on each vendor's dashboard. A credit pool, a daily quota, and a 5-hour window are three different units that cannot be compared or rolled up without a layer above the tools that records every unit of consumption and attributes it to a person, project, or budget. That tracking-and-metering layer is what UsageBox is, and it is deliberately neutral. It does not replace Cursor's billing or tell you which model to use; it gives you the cost-per-task, per-engineer, and per-repo visibility, with caps and showback, that the individual tools were never built to provide across each other. If you would rather build that ledger yourself, the patterns are the same ones in the unexpected-bills writeup; if you would rather not own the plumbing, that is what we exist for.
The number to leave with
On Cursor, your bill equals your subscription price right up until the moment you pin a frontier model or flip on Max Mode, and then it tracks raw token cost with no ceiling unless you set one. Auto is the free lane; manual model selection is the metered lane; usage-based pricing with no spend limit is the open tab. Set the cap, default to Auto, and watch the meter mid-month, and the $500-in-three-days story stops being yours.
Sources
- Cursor Docs: Models & Pricing
- Vantage: Cursor Pricing Explained (2026)
- CloudZero: Cursor AI Pricing in 2026, the credit system and what it costs
Related reading
- Credits, Quotas, or Time-Windows: How AI Coding Tools Actually Bill You. Where Cursor's pool fits among the four meters.
- GitHub Copilot's Usage-Based Billing (2026). The per-token credits model Copilot switched to on June 1.
- Measuring AI Coding Agent Token Cost. Why agent sessions burn credits faster than turn count suggests.
- Capping AI Coding Cost Per Engineer. The team policy layer for caps, throttle, and chargeback.
- When Customers Complain About Unexpected Bills. The transparency patterns that prevent surprise invoices.