How Cursor Pricing and Credits Actually Work (2026)

Cursor sells one product across seven tiers. The four individual tiers (Free, Pro, Pro+, Ultra) differ mainly in how much monthly model compute you get. The two Teams seats (Standard and Premium) add the admin, security and governance controls a company needs, and Enterprise layers on custom contracts. The table below lays out all seven.

In 2025 Cursor moved paid plans from a fixed "fast requests" count to a compute allowance measured in model usage. Each paid plan includes roughly its price in model API spend per month (Pro ≈ $20 of usage). You spend it as you prompt; bigger models and longer context cost more per request.

When the allowance runs out you have three options: fall back to included/rate-limited usage (slower, but no extra charge), enable usage-based pricing to keep going at API rates or upgrade to a higher tier with a larger allowance.

• Included usage: keeps working after the allowance, but throttled at peak times.
• Usage-based pricing: opt-in; you pay model API rates beyond the allowance. Set a spend cap.
• Upgrade: Pro+ and Ultra simply include more monthly compute.

Cursor's June 2026 Teams pricing update split included usage into two pools: Auto + 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. for first-party Cursor models and Auto and Third-Party API for third-party models. The update also introduced a Premium seat for heavy agent users.

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. 3On Teams, watch the Auto + 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. pool separately from third-party API model usage, and check which Cursor Router mode is the team default: only Cost keeps the bundled Auto pricing.
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.