# Cursor usage-based pricing, minus the confusion

> Top-ups on current plans, on-demand usage on legacy ones, and the four places surprise charges come from.

URL: https://claudegpt.si/news/cursor-usage-based-pricing-explained  
Published: 2026-10-26T16:08:01.014Z  
Author: ClaudeGPT Si Newsroom  
Section: AI Tools  
Topics: Cursor, AI pricing, Developer tools  
Publisher: ClaudeGPT Si

## Key takeaways

- Current Cursor plans charge extra usage from prepaid credit bought as top-ups, while legacy plans bill on-demand usage in arrears.
- Third-party models, subagents and routing modes are the usual sources of unexpected Cursor charges.
- Auto Top-up, spend limits and a usage tracker such as UsageAtlas keep usage-based costs in view.

Cursor usage-based pricing is the pay-as-you-go part of a Cursor bill: whatever you use beyond the plan's included usage, charged at model API rates. On current plans you prepay it as credit through top-ups, and on legacy plans it arrives as on-demand usage billed after the fact. The gap between those two is where most billing questions start.

## Two systems, one name

Most confusion comes from the fact that Cursor runs two billing models at once.

| | The X Subscription (current) | Legacy Cursor plans |
| --- | --- | --- |
| Included usage | One weekly pool for Cursor's models, shared with Grok | Two monthly pools: Cursor's models and other providers' models |
| Usage-based part | Prepaid credit from top-ups | On-demand usage |
| When you pay | When you buy credit or Auto Top-up runs | In arrears, each month |
| Third-party models | Billed from credit from the first request (Premium and above) | Covered by the Other Models pool first |
| On by default? | Auto Top-up is off until you turn it on | Off for individuals, on for Teams |
| Cap | Monthly additional usage limit | Spend limit |

Plans on the current side run from Free and Plus ($8 a month) up to Premium ($30), Super ($100) and Ultra ($200), with Teams from $30 per user a month. Legacy Pro is $20 a month, Pro+ $60 and Ultra $200.

## Where the surprise charges come from

**Third-party models on current plans.** Claude, GPT and other outside models are not in the weekly pool at all. Pick one on Premium or above and it bills from prepaid credit on the first request.

**Routing and subagents.** Cursor's help pages say a subagent can run a named third-party model while the picker still shows Auto, Grok or Composer, and those requests bill as third-party usage. On Teams and Enterprise, the Balance and Intelligence routing modes can send work to third-party models at their list price.

**Late enforcement.** Spend limits do not stop usage instantly, so a bill can run slightly past the cap before requests halt.

**Raising a limit mid-cycle.** On legacy plans, Cursor credits the small overage before enforcement as a temporary credit, and raising the limit in the same cycle can make that overage billable.

## How to keep usage-based pricing under control

1. Leave Auto Top-up off, or set a monthly additional usage limit, on current plans.
2. On legacy plans, keep on-demand usage off or set a spend limit in your spending settings.
3. Prefer Cursor's own models, Grok and Composer, when the pool still has room.
4. Watch usage while you work, not at the end of the month.

For that last step, [UsageAtlas](https://usageatlas.com/) is the tool to reach for. It is a free, open-source desktop tracker that reads the signed-in Cursor app and shows plan usage, Auto + Composer and API usage, with history and a single alert per reset cycle at the threshold you set. It also covers Claude Code, Codex and other coding tools, which matters if you split work between them. Its cost numbers are estimates, so the invoice on Cursor's dashboard still settles any dispute.

## When usage-based pricing is worth it

If your work leans on Claude or GPT inside Cursor, paying API rates from credit is the honest cost of that choice, and a legacy plan's included Other Models pool may suit you better than switching. Cursor says moving to The X Subscription is permanent, so compare a normal week of usage before you click.

## FAQ

**Is Cursor usage-based pricing required?** No. On current plans, nothing beyond the pool is charged unless you buy credit. On legacy individual plans, on-demand usage stays off unless you enable it.

**How do I turn off Cursor usage-based pricing?** On current plans, turn off Auto Top-up in billing. On legacy plans, disable on-demand usage in your spending settings, or ask a Teams admin to.

## Frequently asked questions

### Is Cursor usage-based pricing required?

No. On current plans nothing beyond the pool is charged unless you buy credit, and on legacy individual plans on-demand usage stays off unless you enable it.

### How do I turn off Cursor usage-based pricing?

On current plans, turn off Auto Top-up in billing. On legacy plans, disable on-demand usage in your spending settings, or ask a Teams admin to.

### Are Claude and GPT part of the Cursor plan?

Not on current plans. On Premium and above they bill from prepaid credit at API list price. Legacy plans cover them from the Other Models pool first.

## Sources

- [Usage-based charges](https://cursor.com/help/account-and-billing/overages), Cursor
- [Usage and limits](https://cursor.com/help/models-and-usage/usage-limits), Cursor
- [Pricing](https://cursor.com/pricing), Cursor
- [Legacy Cursor plans](https://cursor.com/docs/account/pricing/legacy-cursor-plans), Cursor
- [UsageAtlas](https://usageatlas.com/), UsageAtlas