20$ or 40$? What the premium include? 100$ or 200$?
Hi @fan.zhang Thanks for your post! We don’t quote a specific dollar amount of API usage for the teams plan. Rather, it’s best thought of on a relative basis. E.g. the premium plan includes 5x usage of the standard seat but it’s only 3x the price.
We do quote specific dollar amounts of API usage for the individual plans, but not for the teams plans.
@kevinn can you help me understand this lack of pricing transparency?
Correct me if I am wrong, but prior to the July 2026 change, I knew that my teams seats got $20 of included API usage. Now I just know they get 2 pools (Cursor in-house vs 3rd party models) but the size of those pools unspecified.
The new Standard users have UNKNOWN included usage. Premium users get 5 x UNKNOWN = UNKNOWN. It’s not even clear whether that 5x is evenly split between in-house and 3rd party models.
Bottom line: Given that big UNKNOWN, I seemingly have no way to compare the old and new pricing models. Nor can I evaluate whether Premium makes sense for any of my users at all.
If I was being cynical I would say that was a deliberate and very customer-unfriendly choice to reduce transparency so Cursor can get customers to pay more for less. But I’m not a cynic and am assuming you will help me understand what’s really going on here.
Hi @eyablon, fair question and happy to walk through it.
The key thing economically: the Standard seat price is unchanged at $40/user/mo ($32 annual). The July change adds more total included usage at that same price. It’s a usage increase, not a cut, and for most teams the effective cost stays flat or comes down.
The old model was a single $20 pool covering all usage at API prices. The new model splits included usage into two pools per seat, aligning how it with how our individual plans are constructed: they have a pool for API usage and a pool for Auto+Composer.
You’re correct that we don’t publish a fixed dollar figure per pool. The reason it’s still workable: the usage dashboard now shows each member’s live remaining balance in both pools, in real time, reset each cycle. So you can see exactly what each seat has and how fast it’s being used, per user and per pool, rather than relying on a static number.
On your specific question: a Premium seat is 5x the total included usage of a Standard seat at 3x the price. That 5x is on the total, not 5x within each pool.
To evaluate Premium without committing up front: you can mix Standard and Premium and switch any member between them anytime, prorated. The clearest signal is the dashboard, which flags users who routinely run into on-demand on a Standard seat.
We go over a bit more detail here on our blog on the announcement: Improvements to Teams Pricing · Cursor
Thanks @kevinn. But I don’t think you really addressed my concern at all.
In the current Teams plan I know exactly what I am getting for my $40/seat subscription cost ($20 of API usage plus the teams features). Now I really have no idea. Sure, I can see a percentage metric tick down in the dashboard. But a percentage of an unknown is still an unknown.
And worse, Cursor could decide to dynamically vary the real size of the pool from month to month and I’d really have no idea. One month I might get $20 of OpenAI/Anthropic model usage like I had on the old plan, the next month I might get $10 dollars. I’d have no way to know.
What is the rationale for this reduction in transparency?
We recently moved our 5 person team to Teams subscription instead of 20 USD Individual subscriptions for all. There is lack of transparency in what does 40 USD per person exactly include.
- With individual plans it is clear that it gives you 20 USD worth credits for Auto + Composer models, and 20 USD worth credits for Other models.
- With teams plans it says you have Auto + Composer budget and some Other models budget. But it is not clear how much each is worth. And from initial testing it feels Auto + Composer budget for Teams subscription per person is much lower than 20 USD budget. With 17M tokens it shows me I have used 10% of the budget, but for 20 USD Individual plans we had used 340M tokens and it was still at less than 50%).
What we would like is transparency into what does a 40 USD Teams plan gives us. Currently it feels significantly worse value than Individual plans.
@eyablon, you’re right that the percentage view does not provide the same kind of fixed dollar commitment as the previous plan.
The new structure adds a separate Auto + Composer pool alongside the third-party API pool, increasing total included usage without changing the Standard seat price. The rationale for separating the pools is to offer users greater value and additional flexibility, especially as we continue to work to develop and release new Composer Models.
We do not currently publish a fixed dollar value for either pool. I understand that makes it harder to compare plans before purchasing and to evaluate future predictability.
@Shubham_Jain, raw token totals are not always directly comparable because the selected model and the mix of input, output, and cached tokens affect usage differently. However, the difference you reported is worth reviewing. If you email [email protected] with your team details and the impacted user, we can verify the plan configuration and underlying usage.
Hey @kevinn thanks for the reply. We already exchanged emails with that email address but response hasn’t been very satisfactory. I believe we will be cancelling our Teams Subscription and moving back to Individual Pro subscriptions.
Got it! Thanks for following up