The short version (updated September 13, 2026): Cursor's current paid plans are usage-budget plans, not unlimited frontier-model subscriptions. Pro is $20/month, Pro Plus is $60/month, and Ultra is $200/month. Each includes usage pools; third-party models draw from the Other Models pool at the model's API rate, and usage beyond the included amount can continue as on-demand usage if you explicitly enable it. The old advice that Auto is the free lane is no longer true: after the Cursor Router launch, all Auto modes bill at the list price of the model each request is routed to. If you are trying to understand a charge, start with Cursor's Billing & Invoices dashboard, not an old request-count mental model.
Cursor has changed its billing model several times, which is why old explanations age badly. The current model is easier to reason about if you separate three things: your base subscription, the included usage pools that reset with the billing cycle, and optional on-demand usage after those pools are consumed. A request's cost depends on the model Cursor routes or you select, so the number of agent turns is not a reliable budget by itself.
Cursor's current plan structure
| Plan | Price | Cursor Models pool | Other Models pool |
|---|---|---|---|
| Pro | $20/month | Included | Included |
| Pro Plus | $60/month | Included | Included |
| Ultra | $200/month | Included | Included |
| Teams Standard | $40/user/month | Team seat with centralized billing and usage analytics | |
| Teams Premium | $120/user/month | Higher Agent limits than Standard | |
Cursor now describes two monthly usage pools. Cursor Models covers Cursor's first-party model set, while Other Models covers third-party models such as Claude, Gemini and GPT models. Selecting a specific third-party model draws from the Other Models pool at that model's API rate. The exact number of useful requests therefore varies with model, context size, cache behavior and output length.
Auto is not free anymore
This is the most important correction to older Cursor pricing guides. Cursor Router introduced Auto Cost, Auto Balance and Auto Intelligence. All Auto modes now bill at the list price of the model the request is routed to. On Teams and Enterprise, when Auto routes to a third-party model, Cursor also documents a Cursor Token Rate on top of the model price. First-party Cursor models are exempt from that token-rate surcharge.
So the safe mental model is no longer "Auto is unlimited; pinned models are metered." It is: the route determines the model, and the model determines how quickly your included usage is consumed. Auto may still optimize the model choice for cost or capability, but it is part of the metered system.
What happens when included usage runs out?
Cursor's current documentation says usage beyond the included amount appears as on-demand usage. On-demand must be explicitly enabled. When it is enabled, additional requests are billed at API rates with no markup (with the documented Cursor Token Rate applying to third-party model requests on Teams and Enterprise).
You have three practical controls:
- Disable on-demand usage. Requests stop once included usage is exhausted.
- Set an on-demand spend limit. This caps what you are willing to pay beyond the subscription for that cycle.
- Upgrade the plan. Pro Plus and Ultra provide higher included usage.
There is an important caveat to the spend limit: Cursor says enforcement is not instantaneous. Usage can briefly exceed the configured limit before the system recognizes it. Cursor credits that limited pre-enforcement overage, but raising the limit later in the same cycle can make some or all of that credited amount billable. Treat the spend limit as a strong billing control, not as a synchronous authorization check on every request.
Why Cursor bills still surprise people
1. Old pricing advice survives longer than the pricing model. If a guide tells you Auto is free/unlimited, it describes an older Cursor model. Under the current Router model, Auto usage is priced according to the routed model.
2. A subscription price is not a hard monthly ceiling when on-demand is enabled. The plan includes usage, but the product can continue above that included amount and create separate on-demand charges.
3. Agent workloads compound context. Long-running agents repeatedly send growing context and tool output. Two sessions with the same number of turns can consume very different amounts of model usage.
4. Model selection changes burn rate. Third-party models have different API prices. Choosing a more expensive model—or Auto routing to one—consumes the same included budget faster.
How to control Cursor spend now
- Check Billing & Invoices during the cycle. Cursor separates Included Usage from On-Demand Usage, so you can see whether you are still inside the subscription allowance.
- Turn on-demand off if predictability matters more than uninterrupted operation. That is the clearest way to prevent paid usage beyond the included pool.
- If you enable on-demand, set a spend limit deliberately. Choose the maximum variable amount you are actually willing to pay, and remember enforcement can lag briefly.
- Treat model choice as a cost control. A cost-oriented Auto route or a cheaper explicit model can preserve included usage longer than routinely using the most expensive frontier model.
- For teams, inspect usage distribution. Centralized team usage analytics matter because a small number of agent-heavy users can dominate the variable component.
What UsageBox can and cannot do here
If your goal is to control your Cursor subscription, use Cursor's own Billing & Invoices page, on-demand toggle and spend-limit controls. UsageBox does not import Cursor seat usage, read Cursor invoices, change Cursor routing, or enforce Cursor's spend limit.
The UsageBox use case starts when you are building your own API or AI product and can emit the usage event yourself. Then an independent meter can preserve customer/workload quantities outside the model provider and outside the payment system, which makes later reconciliation and customer billing easier to defend. That is a separate problem from observing a Cursor seat.
The number to leave with
In the current Cursor model, your subscription buys included usage; it does not make Auto free, and it does not necessarily cap the total bill. All Auto modes bill at the routed model's list price, and enabled on-demand usage can continue after the included pool is exhausted. If you need a predictable ceiling, disable on-demand usage or set its spend limit and monitor the Billing & Invoices dashboard during the cycle.