Cursor Teams Pricing: Seats, Usage Pools & On-Demand Billing

Teams is the self-serve plan, billed per seat, with SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition., usage analytics, BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. reviews and cloud agents. Enterprise is a custom contract that adds priority support, invoicing, SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition., pooled usage and advanced security controls. CMEK and a HIPAA BAA are also Enterprise-only. Of all that, invoicing and pooled usage change the finance picture most.

Self-serve plans are paid by credit or debit card, and Cursor's pricing page lists invoice and purchase-order billing under Enterprise only. Cursor points larger teams to enterprise@cursor.com for volume discounts.

Under about twenty seats, a card and a team-wide limit cover most finance needs, and Enterprise mostly adds paperwork you don't need yet. Headcount doesn't settle the question, though. If anyone at your company has to raise a purchase order to buy software, you need Enterprise at any size.

Included usage works differently on The X SubscriptionThe subscription Cursor is sold through: one plan for Grok, Cursor and X, with Free, Plus, Premium, Super and Ultra tiers, per-seat Teams, a weekly included pool for Cursor models shared with Grok, and third-party models billed at API list price from prepaid credit. Press Enter for the full definition. and on legacy seats. On The X Subscription:

• Each paid seat has its own weekly pool for Cursor models, shared across Cursor and Grok for that person.
• Cursor models are currently Grok 4.7Cursor and SpaceXAI's current lead Cursor model, in the weekly pool at $2 per million input tokens and $6 per million output, with a 256k context window and a 500k variant; above 256k input tokens it bills at 2x the standard rate. Press Enter for the full definition., Grok 4.6A Cursor and SpaceXAI model for complex coding and knowledge work, still in the Cursor model pool and succeeded by Grok 4.7; 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..
• Pools are per seat. They don't transfer between teammates, and they refresh weekly.
• Super holds 3.75x the Premium pool, and Ultra holds 12.5x. A Free seat costs nothing and has no team allowance.
• Third-party models aren't in the pool. Every request to one is paid from the team's prepaid balance, at the model's public API list price plus the Cursor Token Rate if the model is eligible.

Legacy Standard ($40/user/mo) and Premium ($120/user/mo) seats split included usage into two monthly pools instead: Cursor ModelsOn legacy Cursor plans, the monthly usage pool for Cursor's own models (Grok 4.7, Grok 4.6, Grok 4.5 and Composer 2.5), kept separate from the third-party Other Models pool. The X Subscription replaces it with one weekly pool. Press Enter for the full definition., with the same Cursor models, and Other ModelsOn legacy Cursor plans, the monthly pool for supported third-party models from providers such as Anthropic, Google and OpenAI, separate from Cursor Models. On The X Subscription third-party models are billed from prepaid credit instead. Press Enter for the full definition., for third-party models at their API prices. Legacy Premium carries 5× the Standard allowance, admins can hold a free Unpaid Admin seat, and every member's usage resets together on the team billing cycle.

Because each pool belongs to one person, the team average tells you little. Look at the distribution instead: the people who run out of their pool every cycle are your candidates for a bigger seat. Pooling one budget across everyone is an Enterprise feature, covered in pooled usage.

That table is also the strongest argument for standardizing on a model instead of letting everyone pin a favorite. It lists 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. at $0.50 per million input tokens and $2.50 output, against $4 and $20 for GPT-5.6 Sol, a promotional rate through November 21, 2026. A gap that size between two reasonable choices can move a monthly bill more than seat mix does. On The X SubscriptionThe subscription Cursor is sold through: one plan for Grok, Cursor and X, with Free, Plus, Premium, Super and Ultra tiers, per-seat Teams, a weekly included pool for Cursor models shared with Grok, and third-party models billed at API list price from prepaid credit. Press Enter for the full definition., 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. also draws from the weekly pool first, while GPT-5.6 Sol is paid from prepaid credit from the first request.

On The X SubscriptionThe subscription Cursor is sold through: one plan for Grok, Cursor and X, with Free, Plus, Premium, Super and Ultra tiers, per-seat Teams, a weekly included pool for Cursor models shared with Grok, and third-party models billed at API list price from prepaid credit. Press Enter for the full definition., a member whose weekly pool runs out keeps working on Cursor models at their token rates, paid from the team's prepaid balance, with no drop in service or quality. Additional usage stops when the balance is empty or the team's monthly additional usage limit is reached, whichever comes first. Admins refill the balance with one-time top-ups, or with Auto Top-up when it falls below a threshold.

Legacy seats use on-demand usage instead. It is on by default for Teams and billed monthly in arrears at the same per-model rates as included usage, and admins can turn it off or cap it with a team-wide spend limit.

On a legacy team, check that default on day one if finance is nervous, because it decides whether the monthly bill has a ceiling before anyone chooses one. Leaving on-demand on with a team-wide limit keeps service running under a number you picked. Turning it off makes included usage a hard stop, which arrives mid-sprint for whoever hits it first.

The two plan families also bill at different times. Prepaid creditBalance bought by top-up or Auto Top-up on The X Subscription that pays for third-party models from the first request, and for Cursor models beyond the weekly pool, at the same per-model rates. Press Enter for the full definition. is charged when you buy it, while legacy on-demand usage is billed after the month ends, so a legacy team learns the shape of a heavy month afterward. Per-user spend tracking in the admin dashboard closes that gap if somebody reads it weekly instead of at invoice time.

On Enterprise, yes. Enterprise admins can set member-level limits, group limits through directory sync and a default per-member cap. Cursor's help center says a member with limits from several sources gets the highest one that applies.

On Teams, Cursor's own pages disagree. Its team pricing and members docs say admins of a team on The X SubscriptionThe subscription Cursor is sold through: one plan for Grok, Cursor and X, with Free, Plus, Premium, Super and Ultra tiers, per-seat Teams, a weekly included pool for Cursor models shared with Grok, and third-party models billed at API list price from prepaid credit. Press Enter for the full definition. can set a default monthly limit per member and per-member overrides from the Members page. Its help center and the X Subscription docs describe one monthly limit for the whole team, set as a fixed amount or an amount per seat. On a legacy team, the spend limit is team-wide. Check your own members page before you promise finance a per-person cap.

Spend alerts don't fill the gap. They send email once additional usage passes a threshold you set, but they never pause usage, so treat them as a warning and keep the limit as the control.

Teams and Enterprise pay a $0.25 per million tokens Cursor Token Rate on eligible third-party model requests. Cursor says it covers custom model execution, such as Tab and Apply, plus infrastructure and processing costs. It applies to input, output and cached tokens, including requests made with your own API key. Cost mode requests, Cursor models such as Grok and 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., and the third-party models on Cursor's excluded list are exempt. Balance and Intelligence incur it only when Cursor Router sends a request to an eligible third-party model.

Give it its own row in a finance model, for two reasons. Cached tokens count, so a long thread that mostly reads from cache still accrues the rate. It also applies to requests made with your own API key, which breaks the usual build-versus-buy assumption: the provider bill moves to your account, but this line stays. The Cursor Token Rate page has the exemptions and the arithmetic.

Cursor bills per active paid seat, not a pre-allocated seat count, and your renewal date stays the same through every change. Adding a member mid-cycle creates a pro-rated charge for the rest of the period. An upgrade applies right away and charges the pro-rated difference, and a downgrade applies at the end of the period. Removing a member frees the seat for the next person who joins; to stop paying for it, reduce seats in billing, effective at the end of the period.

Pro-rating removes most of the forecasting problem, but removals raise an accounting question that Cursor's pages answer two ways. The members page promises pro-rated credit for removed members on the next invoice. The team pricing page, described above, has you reduce seats to stop paying at the end of the period and says nothing about a credit. Either way, a team that over-provisions in March sees the correction on a later invoice, not as money returned. The fixed renewal date keeps a procurement calendar intact.