Auto’s pricing definitions changed — do not switch tools yet
What drives a bill is usually not the unit price but which requests count toward usage. Switch before you have checked that, and you may land on the same problem elsewhere.
Updated 2026-10-22
Top up once and call Claude, GPT and Chinese models with one key — Starter from $9/month, or pay-as-you-go packs with no subscription.
- Billed per token — live rates on /models
- Pay by card (Visa / Mastercard), Apple Pay, Google Pay or crypto
- Self-service: top up and activate instantly
Four things to check
Which requests count
Whether completions, background indexing and retries are billable explains a rising bill better than the unit price does.
Where old and new rules split
Changes carry an effective date; before and after are two different ledgers. Read the bill in segments, not as a monthly average.
Were you opted in
Auto-style switches are often on by default. Confirm which setting you are actually on before judging the bill.
Matters more than cheap
The unpredictability of usage billing is itself a cost. A fixed ceiling is friendlier to a budget.
Why bill changes are so often unreadable
In a usage-billed product the bill is set by three things: the unit price, the set of requests that count toward usage, and your actual usage pattern. When a vendor makes a change, usually only the first gets discussed publicly — while a change in the second moves the bill more. If background indexing or automatic retries move from non-billable to billable, the bill rises noticeably even with the unit price untouched.
So when you see a pricing announcement, look first for the section defining what counts as usage, not the price table. One dated example: as of 2026-10-14, the Cursor help page for The X Subscription states that third-party models in Cursor, such as Claude or GPT, are not included in your plan and are billed at API list prices from the first use, paid from your prepaid credit.
About the effective date
Changes like this usually come with a transition window during which old and new rules may coexist. Go by the announcement and billing page inside your own account — third-party retellings frequently get the date wrong, and segmenting a bill on the wrong date can produce exactly the opposite conclusion.
What to do
Open the billing page and confirm which rule set you are on and when the next cycle starts.
Export your current usage detail and keep it. After the switch you will want a "before" baseline to compare against.
Export again and compare by request type. Whichever category the increase concentrates in is your answer.
Understand the definitions before deciding to switch
What is confirmed
As of 2026-10-14, the following can be checked word for word in Cursor's official help center and docs: the old Auto mode was split into three modes, Cost, Balance and Intelligence; all Auto modes bill at the list price of the model each request is routed to; and Cursor Router will launch for Teams and Enterprise plans first, while individual plans (Hobby, Pro, Pro+, Ultra) will receive the update a few months after launch. Your own account's switch date is shown in the in-account announcement and on the billing page.
What this page does not state
This page states no specific unit prices, multipliers or discount figures. The official wording is that requests bill at the list price of the model they are routed to, and what each model costs is in the official Model pricing table. Numbers like these distort easily when retold, and getting one wrong would directly mislead your budgeting. Use the official price list and the billing page in your own account.
Two cost models
Usage-based billing
Cheap when you use little, and elastic. The cost is an unpredictable bill, and a definitional change alters your cost structure directly.
Fixed-ceiling billing
A clear daily ceiling, predictable cost, easy to budget. The cost is having to prioritise your own work at peak times.
A checklist you can actually run
First, find the effective date in the official announcement and split your bill into two segments around it. Second, find the definition of what counts toward usage and walk it against the operations you actually trigger. Third, check the current state of any Auto-style switch on your account and confirm whether you chose it or inherited it. Fourth, if usage detail is available, export it and group by request type to see where the increase concentrates. After those four steps you will know whether to change habits, change tier, or change plan.
QCode is a different cost model
QCode offers two ways to buy as an individual. A Personal Plan gives a daily allowance that resets at 00:00 Beijing time, with self-service booster packs if a day runs short (those reset separately at 02:00 the next day). If you don't want a monthly plan, buy Pay-as-you-go Packs: you get one lump sum, drawn down as you use it within 7 days.
The advantage of a Personal Plan is a predictable budget that does not deform when a vendor revises its billing definitions. The drawback deserves stating too: if your usage is small, usage-based billing may well be cheaper. Which is better depends on your intensity — neither is better for everyone.
FAQ
Will my bill definitely go up after the change?
Not necessarily. It depends which request categories your usage falls into. Splitting the bill by effective date and grouping by request type answers this better than reading the announcement does.
Why did my bill rise when the unit price did not?
Most often the set of requests counting toward usage changed. Whether background indexing, automatic retries and completion requests are billable typically moves the bill more than the unit price itself.
Should I turn Auto off?
First confirm whether it is currently on, and whether you chose it or inherited it. Turning it off may save money, or may just move the work onto you. Decide after the grouped usage comparison.
How does QCode bill?
By a Personal Plan's daily allowance: it resets at 00:00 Beijing time, and if a day runs short you can buy a booster pack yourself, which resets separately at 02:00 the next day. If you don't want a monthly plan, you can buy Pay-as-you-go Packs: one lump sum, drawn down as you use it within 7 days. The characteristic is predictable cost.
Is a fixed allowance always cheaper than usage billing?
No. If you use very little, usage billing may be cheaper. A fixed allowance is valuable for predictability — it suits steady usage and people who do not want their bill moving with a vendor’s rule changes.
Do I need to change my toolchain to use QCode?
It depends what you use today. QCode exposes endpoints compatible with the mainstream protocols, so in most cases it is a configuration change; check how your specific client connects.
Sources
Pricing rules follow the vendor’s official announcement and the billing page in your account. This page offers only a method for checking; it does not repeat specific figures from third-party retellings.
If you want a predictable bill
A fixed daily allowance resetting at 00:00 Beijing time — it does not move when a vendor revises its pricing definitions.
Related reading
Claude Code vs Cursor comparison
Which billing model suits which situation.
Cursor X Subscription and third-party model pricing
Verbatim cursor.com sentences from 2026-10-13: third-party models at API list price, no allowance on Premium and above, Token Rate and own-key billing.
OpenAI models leaving Cursor on November 12? The proposed date and your options
OpenAI's proposed 2026-11-12 transition period, what Cursor's own-key setup does not cover, and ways to keep using GPT models for coding.
Crypto payment guide
Nine coins, 56 networks, zero platform fee for AI coding API credits.
Third-party pricing rules follow their official announcements and the billing page in your account, and may change at any time. This page provides no specific price figures, only a method for checking.