In This Article
Key Takeaways
- Effective July 1, 2026, Cursor Teams seats bill at $40/seat/month (Standard) and a new $120/seat/month Premium tier, with annual plans at $32 and $96.
- Every seat now carries two separate usage pools: one for Cursor's first-party models (Auto and Composer 2.5) and one for third-party API usage on outside models.
- The Premium seat includes five times the usage of Standard at three times the cost — aimed squarely at heavy agent users.
- The split makes it clear where your spend goes. Teams that lean on Cursor's own models get more predictable bills; teams that route heavily to Claude or GPT should watch the third-party pool.
Cursor changed how it charges teams, and the change is more interesting than the headline price. As of July 1, 2026, a Standard Teams seat costs $40 per seat per month on the monthly plan (or $32 billed annually), and there is a new Premium seat at $120 per month (or $96 annually). But the price is not the story. The story is that Cursor now divides each seat's included usage into two separate buckets — one for its own models and one for everyone else's — and that split tells you a lot about where the AI coding market is heading.
If you manage an engineering team on Cursor, this affects your next invoice. If you are learning to build with agentic editors, it is a clean case study in how AI tools pass through the cost of the models underneath them. Let us walk through what changed, why, and what to do about it.
What actually changed
Three things moved at once. First, the seat prices were set explicitly: Standard is $40/seat/month monthly or $32 annually, and the new Premium seat is $120/seat/month monthly or $96 annually. Second, a Premium tier now exists at all — previously Teams was effectively one seat type. Third, and most important, each seat's included usage is now split into two pools instead of one shared allowance.
The rollout is staged. According to Cursor, the changes applied immediately to new customers and take effect for existing customers on billing cycles starting July 1, 2026. That means many teams will see the new structure land on their first renewal after that date rather than overnight. As StartupHub reported, Cursor framed the whole move around billing predictability — the recurring theme in its pricing changes over the past year.
The two pools, explained
Here is the core mechanic. Every Teams seat now includes two separate pools of included usage:
- A first-party models pool — included usage for Cursor's own models, specifically Auto and Composer 2.5. This is the work done by models Cursor builds and runs itself.
- A third-party API pool — usage consumed when you route requests to outside models such as Anthropic's Claude or OpenAI's GPT through Cursor.
Before, a seat had one allowance and it did not much matter which model you called; you drew down the same balance either way. Now the two are metered separately. The practical effect: work you send to Cursor's own models no longer competes for the same budget as work you send to third-party models. Cursor controls the cost of its first-party models directly, so it can be generous there. It pays market API rates for third-party models, so that pool behaves more like a metered pass-through.
Standard vs Premium: the math
The Premium seat is built for one kind of user: the person running agents hard all day. Cursor describes it as five times the included usage of the Standard seat at three times the cost. That is a favorable ratio if — and only if — you actually consume the extra allowance. Cursor says the first-party pool on a Premium seat should cover a full month of heavy agent usage for 99% of users.
Cursor Teams seats at a glance
| Standard seat | Premium seat | |
|---|---|---|
| Monthly price | $40 / seat / mo | $120 / seat / mo |
| Annual price | $32 / seat / mo | $96 / seat / mo |
| Included usage | Baseline | 5× Standard |
| Cost multiple | 1× | 3× |
| Best fit | Light to moderate agent use | All-day heavy agent use |
Because teams can mix seat types freely, you do not have to pick one for everyone. The sensible pattern for most shops: put your handful of power users on Premium and keep everyone else on Standard. Paying $120 for a seat that touches Cursor a few times a day is waste; paying $40 for a seat that would blow through its pool by the second week is a different kind of waste. Match the seat to the person.
Why Cursor split the pools
Split billing solves a real problem Cursor has been wrestling with publicly for over a year: when a tool resells someone else's model, it is exposed to that model's price and rate limits. If a single shared allowance covers both your own cheap-to-run models and expensive third-party calls, then a few heavy Claude users can drain the pool for everyone, and the vendor eats unpredictable cost. Separating the pools lets Cursor be generous with what it controls and precise with what it does not.
This is the same dynamic we wrote about in our Claude Code vs Cursor cost comparison: the price you pay for an AI coding tool is increasingly a bet on which models it can run cheaply. Tools with strong first-party models can offer more headroom; tools that are thin wrappers over third-party APIs cannot. Cursor's split makes that structural reality visible on your invoice for the first time.
The pattern to watch across the whole category
Cursor is not alone here. Every agentic editor — Cursor, Windsurf, Claude Code, Cline — is quietly deciding how much of its own model stack to build versus how much to resell. First-party models mean pricing control and fatter included tiers; reselling means exposure to someone else's rate card. When you compare tools now, look past the sticker price and ask what share of the work runs on the vendor's own models. That ratio predicts how stable your bill will be next year. See our 2026 agentic editor comparison for how the field lines up.
What it means for your team
The immediate consequence is that your bill now has two dials you can read independently. If your first-party pool is barely touched but your third-party pool is always empty, your team is leaning on outside models — Claude, GPT — and you are paying market rates to do it. That is not wrong, but it is a choice worth making on purpose. You might get comparable results on Composer 2.5 for a large share of routine work and reserve the expensive third-party calls for the tasks that genuinely need them.
If you are teaching yourself agentic coding, this is a useful moment to understand token economics from the inside. The reason a tool can hand you "generous" included usage on its own model and meter you tightly on someone else's is the same reason API prices differ across providers. Our free Cursor course walks through how to work efficiently inside the editor, and the LLM price calculator lets you see what routing the same workload to different models actually costs.
What to do this week
Four steps. First, find your renewal date — the new structure lands on your first billing cycle on or after July 1, 2026, not necessarily today. Second, pull last month's usage and see how it splits between first-party and third-party models; that tells you which pool is your constraint. Third, price out whether Premium's 5×-usage-for-3×-cost math beats Standard overage for your two or three heaviest agent users specifically. Fourth, if the third-party pool is your bottleneck, test whether Composer 2.5 handles a meaningful slice of that work so you can shift load to the pool Cursor subsidizes — model both routing options with the API cost estimator first.
None of this requires a dramatic reaction. The pricing is not punitive, and mixing seat types keeps you flexible. Cursor has simply handed you a clearer picture of where your money goes — and that is only useful if you look at it.
Understand what your AI tools actually cost
Our free calculators and courses help you read token bills, compare model prices, and route work to the right model — no signup required.
Explore the Free ToolsSources: Cursor, “Improvements to Teams Pricing”; StartupHub, “Cursor Teams Upgrades Pricing for Predictability”. Prices are as published by Cursor and effective July 1, 2026; confirm current terms with Cursor before budgeting. Analysis by Precision AI Academy.
Common questions
How much does a Cursor Standard seat cost now? $40 per seat per month on the monthly plan, or $32 per seat per month billed annually, effective July 1, 2026.
What is the new Premium seat? A $120/seat/month tier ($96 annually) that includes five times the usage of the Standard seat at three times the cost. It is designed for users who run agents heavily all day.
What are the two usage pools? Each seat now has a separate allowance for Cursor's first-party models (Auto and Composer 2.5) and for third-party API usage on outside models like Claude and GPT. They are metered independently.
Do I have to move everyone to Premium? No. Teams can mix seat types freely, so the usual move is to put a few power users on Premium and keep the rest on Standard.