How Cursor Pricing and Credits Actually Work (2026)

Cursor sells individual and business plans. The India-only Start plan sits between Free and Pro with local INR billing and a narrower product scope. Pro, Pro Plus, and Ultra add third-party model allowances. Teams seats add administration and shared controls, while Enterprise uses a custom contract. The table keeps the current entry prices in one place.

Current paid individual plans use two monthly pools. Cursor ModelsCursor's plan and usage pool for models it labels as Cursor Models, kept separate from the third-party Other Models pool. Press Enter for the full definition. covers Grok 4.6A Cursor and SpaceXAI frontier model for complex coding and knowledge work; it is a selectable model and is separate from the Grok Bot product. Press Enter for the full definition., Grok 4.5, and Composer 2.5The current Composer release, better at long-running tasks and at judging when a job needs a light touch versus deep work. Press Enter for the full definition. with generous included usage. Other ModelsCursor's pool of supported third-party models from providers such as Anthropic, Google and OpenAI, with separate plan access and usage from Cursor Models. Press Enter for the full definition. covers third-party models at their API prices. Start includes no Other Models allowance; Pro includes $20, Pro Plus $70, and Ultra $400.

When included monthly usage runs out, Cursor does not switch the request to a slower or lower-quality model. Eligible plans can add on-demand usage at the same published rates or upgrade for more included usage. Start has no on-demand option, so its next step is Pro or higher.

• On-demand usage: opt in on an eligible plan and continue at the same rates, with a spend limit you control.
• Upgrade: move to a tier with more included usage.

The two pools answer different model choices. A direct request to Grok 4.6A Cursor and SpaceXAI frontier model for complex coding and knowledge work; it is a selectable model and is separate from the Grok Bot product. Press Enter for the full definition., Grok 4.5, or Composer 2.5The current Composer release, better at long-running tasks and at judging when a job needs a light touch versus deep work. Press Enter for the full definition. draws from Cursor ModelsCursor's plan and usage pool for models it labels as Cursor Models, kept separate from the third-party Other Models pool. Press Enter for the full definition.. Selecting a specific third-party model draws from Other ModelsCursor's pool of supported third-party models from providers such as Anthropic, Google and OpenAI, with separate plan access and usage from Cursor Models. Press Enter for the full definition. at that model's API rate. Both pools reset with the monthly billing cycle and appear separately in the usage dashboard.

Auto does not map cleanly onto either pool as a label. Auto Cost has a fixed per-token price regardless of which model is used. Auto Balance and Auto Intelligence bill at the routed model's API rate, and third-party routes add the Cursor Token Rate on Teams and Enterprise. The Cursor Router guide covers the selection controls; this page keeps the billing result explicit.

You control Cursor cost in two ways: cap what you can spend, and lower what each task burns. Set a spend cap so the bill can never run away, then trim token use per request. These seven steps cover both, from the hard limit down to day-to-day model choices.

1. 1Set a hard usage-based spend cap in Settings so you can never be surprised.
2. 2Use a smaller or cheaper model for routine edits; reserve the strongest models for hard problems.
3. 3Watch the Cursor ModelsCursor's plan and usage pool for models it labels as Cursor Models, kept separate from the third-party Other Models pool. Press Enter for the full definition. and Other ModelsCursor's pool of supported third-party models from providers such as Anthropic, Google and OpenAI, with separate plan access and usage from Cursor Models. Press Enter for the full definition. balances separately, and check which Cursor Router mode is the team default.
4. 4Use Premium seats for the small group of heavy agent users instead of upgrading every teammate by default.
5. 5Keep context tight: fewer open tabs and scoped @-context cost fewer tokens per request.
6. 6Batch related work into one agent session instead of many cold starts.
7. 7Watch the usage dashboard for the first month to learn your real burn rate.

For developers who code daily, Pro typically pays for itself if it saves even ~20 to 30 minutes a week. The honest caveat: if you lean heavily on the most expensive models all day, Pro's allowance won't be enough, and Pro+ ($60) or usage-based pricing is the realistic cost. Budget for your actual model mix rather than the sticker price.

There is no fixed per-request price to anchor to; the allowance is measured in dollars of model compute, not a request count. So picture the day instead. A couple of large agent runs on a frontier model, plus a long planning conversation, can quietly draw down a meaningful slice of a Pro allowance in a single sitting. That is why heavy users feel the burn well before month-end: the spend tracks how much compute each prompt actually consumed, and the most capable models on long context consume the most.

The plan-then-execute cost loop

A reliable pattern keeps cost and quality in balance: plan with a frontier model, then execute with ComposerCursor's own fast coding model, tuned for the editor and priced well below frontier models; the recommended day-to-day model for executing a plan. Press Enter for the full definition.. You spend a little on the most capable model to produce a tight, reviewed plan, then hand the mechanical edits to the cheaper, fast Composer model. The expensive thinking happens once, up front, where it determines whether everything downstream is right; the bulk of the token volume runs at the cheaper rate.

1. 1Plan the change with a frontier model so the approach is correct before any code moves.
2. 2Review and tighten the plan: this is the cheapest place to catch a wrong direction.
3. 3Execute the plan with ComposerCursor's own fast coding model, tuned for the editor and priced well below frontier models; the recommended day-to-day model for executing a plan. Press Enter for the full definition., which carries the high token volume at a lower rate.
4. 4Reserve frontier-model turns for the genuinely hard reasoning, not the bulk edits.