Cursor usage limits, weekly included usage and prepaid credit on Teams and Enterprise plans, explained

Cursor now sells Teams on a plan it calls The X Subscription: “Teams has three paid seat tiers and one free seat"¹. A Premium seat is $30 per user per month with “the Premium weekly usage pool”; a Super seat is $100 with “the Super weekly usage pool, 3.75x Premium”; an Ultra seat is $200 with “the Ultra weekly usage pool, 12.5x Premium”; a Free seat is $0 and carries no team usage allowance¹. Each paid seat has “its own weekly pool for Cursor models”, and “the pool refreshes weekly"¹, on its own clock, “separate from your billing cycle"¹⁷. Third-party models “aren’t included” in any tier: they bill from a prepaid balance the whole team shares, at public list API prices plus the Cursor Token Rate¹⁵.

The structure Cursor sold from June 1, 2026, a Standard seat at $40 and a Premium seat at $120 with two included pools resetting monthly, is now documented as legacy: “Teams created before The X Subscription have two paid seat types, Standard ($40/user/mo) and Premium ($120/user/mo, with 5x the Standard allowance)“¹. If your team predates The X Subscription, that is the structure you are on, and it is explained on its own page.

Cursor publishes no annual price for these tiers. “Seat tier is separate from role”: Members and Admins “can have any seat tier, and one team can mix tiers"¹. Cursor “bills per active paid seat, not pre-allocated seats”, and “adding a member mid-cycle creates a pro-rated charge for the rest of the billing period"¹. Prices are exclusive of applicable taxes¹⁸, and subscriptions are sold only directly, through X Subscription Corp, with no authorized resellers¹⁸. Cursor puts no number on the Premium pool, only a name and the multiples above it. What it does document is how the pool is consumed, which is the part that decides your invoice.

Included usage and additional usage

Two units, and only one of them is money:

• Included usage is the allowance inside a seat. Each paid seat has “its own weekly pool for Cursor models (Grok 4.7, Grok 4.6, Grok 4.5, and Composer 2.5)“¹; third-party models “aren’t included"¹. Usage is metered in tokens at each model’s list price per million tokens, and “different models draw from the pool at different rates"³. The pool belongs to the seat: “seats don’t share weekly pools with each other, and usage doesn’t transfer between team members"¹. It refreshes weekly, separate from the billing cycle¹¹⁷, and “unused included usage does not roll over on either kind of plan"⁴.
• Additional usage is what a team spends to keep working past the pools. It is paid from a prepaid balance shared by the whole team⁵: admins “buy credit with one-time top-ups” or turn on Auto Top-up, which tops the balance back up when it drops below a threshold¹, and “top-ups add prepaid credit to your subscription” that is not part of the included weekly pool⁵. Third-party models bill from it at public list API prices with no markup⁵¹³, plus the Cursor Token Rate of $0.25 per million tokens on “eligible third-party model requests”, which applies on Teams and Enterprise plans only and exempts the first-party models⁸; the rate “is charged on top of the model’s API price and paid from the team’s prepaid credit"⁸. Prepaid credit does not reset with the weekly pool⁴, and “each top-up stays available until used or until it expires"¹⁷.

When a weekly pool runs out mid-week, the choices are the vendor’s own list: “Wait for the reset. Your pool refreshes weekly.”; “Use prepaid credit. Keep working at the same per-model rates with top-ups or Auto Top-up.”; “Upgrade your plan. Move to a higher tier for a larger weekly pool.“³ For third-party models there is no pool to exhaust: those requests bill from prepaid credit from the first one¹. Requests are never downgraded in quality or speed³. The dollars start at the wall, and on Teams the wall is per seat and per week.

Which plan you are on

The individual Free, Plus, Premium, Super and Ultra plans¹⁸ are not covered on this page. Cursor uses the Premium, Super and Ultra names for those personal plans as well as for the Teams seat tiers above, so check whether a price you have been quoted is per user on a team or for a personal plan. Legacy request-based plans are being retired: a subscriber can keep one until the next renewal and is then migrated to usage-based pricing²³.

How the seat model changed in 2026

Under the per-seat model, one member’s heavy week is one member’s problem, and one member’s quiet week is nobody’s gain. The changes this year moved the walls twice and, on Enterprise, offered a way around them, without changing the per-seat shape on Teams.

• May 4, 2026. Enterprise admins gained model and provider allow lists and block lists, soft spend limits that warn instead of blocking, automatic alerts to users reaching 50%, 80% and 100% of a limit, and usage analytics filtered by user or product surface¹⁴.
• June 1, 2026. Teams pricing was restructured into two included-usage pools per seat, with a Standard seat getting more usage at the same price and a new Premium seat at “5x the included usage of the Standard seat, at only 3x the cost"². The stated reason outlived the structure: “a small number of power users on any team tend to drive the majority of spend and unpredictable on-demand costs"².
• July 22, 2026. Auto became Cursor Router, with Cost, Balance and Intelligence modes, available on Teams and Enterprise, on by default for Teams¹⁶. “Cost mode bills as a Cursor-model request and draws from the weekly pool, with no Cursor Token Rate”; “Balance and Intelligence bill at the list price of the model each request is routed to”, and a third-party route in those modes incurs the Token Rate¹⁵.
• August 12, 2026. Grok 4.6 arrived on every paid plan²² and sits in the first-party Cursor Models pool³.
• August 21, 2026. The Pricing Policy was last updated¹³: model fees are total tokens times the model’s rate, model pricing is “subject to change in accordance with the Model provider’s list pricing”, and on-demand fees are billed monthly in arrears on actual consumption¹³. The newer billing docs describe additional usage paid from prepaid credit⁵; where the two read differently for your team, the Order Form and your invoices are the place to check.
• The X Subscription. The current structure: three paid weekly-pool seat tiers, a Free seat, and a team-shared prepaid balance¹. The vendor has published no date for the change, so this page does not give one.

Three details that matter more than the dates:

1. On Teams, the pool belongs to the seat, by the week. “Seats don’t share weekly pools with each other, and usage doesn’t transfer between team members"¹. A member at the wall and a member with an untouched pool are the same team, the same week, and the same invoice.
2. A spend limit stops the person’s paid usage, not the bill. When a member reaches a spend limit, “paid additional usage stops for that specific user” until the limit is raised or the next period starts, though “included weekly usage on The X Subscription keeps working"⁶. Enforcement is not instant, so usage can briefly exceed the limit⁶. The team’s limit “counts paid additional usage you consume, not the prepaid credit you buy”, and buying more credit does not raise it⁶.
3. The refresh does not wait for anyone. The weekly pool refreshes “separate from your billing cycle"¹⁷; the billing cycle itself starts on the date you subscribe and renews from there¹⁷. Usage a member did not use by the refresh is not theirs the following week, and on Teams it was never anyone else’s.

Why the invoice may look different

A team that budgeted for two monthly pools per seat now has one weekly pool per seat, no third-party allowance, and a prepaid balance in place of on-demand billing¹⁵. What the invoice does with that depends on who is on which tier and what they run.

The pool multiples are Cursor’s¹; the price multiples are this page’s arithmetic from the seat prices above, $100 and $200 against $30. Cursor no longer publishes a dollar range for what a given kind of user spends; it sizes by tier instead: “Premium suits new Agent users, Super suits daily Agent users,” and “Ultra suits power users running several agents or Automations"³. The members whose usage sits a tier above their seat are the tail, and on a per-seat plan the tail is exactly the set of members who reach the wall, now weekly.

What actually drains included usage

Model choice first. The docs publish a per-million-token price for every model, “different models draw from the pool at different rates"³, and a Fast variant costs more per token than the standard one: on Grok 4.6, twice as much³. Routing is next: “Cost mode bills as a Cursor-model request and draws from the weekly pool, with no Cursor Token Rate”; “Balance and Intelligence bill at the list price of the model each request is routed to”, and “Balance and Intelligence use your usage limits faster than Cost"¹⁵. Grok 4.6 offers four effort levels, low through xhigh, so the same prompt can cost very different amounts of compute²². Total tokens include input, output, and cache reads and writes¹³. Two things that look like seat usage are not: Bugbot on Teams “bills from the team’s prepaid credit” rather than from the seat’s weekly pool¹⁹, and on Enterprise, service accounts consume the team’s usage pool without consuming a seat²⁰. Opting in to regional data residency adds a 10% uplift on model pricing for eligible models³.

“a small number of power users on any team tend to drive the majority of spend and unpredictable on-demand costs.” Cursor, announcing the June 1 Teams pricing²

What an administrator can do

Each control below does one thing and stops at a definite point.

• Roles and seat tiers. Members have no access to billing settings or the admin dashboard; Admins see team analytics and “configure top-ups and the team’s monthly additional usage limit"⁹. A Free seat is “for members who don’t need a team usage allowance”, and any Member or Admin can hold one⁹¹. Whether Members can change usage and spend settings themselves depends on the “Only Admins Can Edit Usage Settings” toggle⁶. Where it stops: a role decides who may set a ceiling, not where usage goes.
• The team’s additional-usage limit. Admins “set one monthly additional usage limit for the whole team (no limit or a fixed amount)“¹, effective immediately⁶. Dynamic Spend Limits scale it with the seat count⁶. It “counts paid additional usage you consume, not the prepaid credit you buy”, and buying more credit does not raise it⁶. Where it stops: at the limit, “additional usage pauses until the next month or until you raise it, even if credit remains"⁶; included weekly pools keep working⁶.
• Per-member and group limits. The Teams docs describe “a default monthly limit per member and per-member overrides from the Members page"¹; group overrides remain Enterprise⁶. Member overrides, group overrides and the team’s general limit apply with the highest applicable limit winning⁶, and soft limits warn instead of blocking¹⁴. On pooled Enterprise accounts a member limit applies to total usage, not just on-demand⁶. Where it stops: a per-member limit decides when that member’s paid usage stops. It does not move what a quiet member left unused.
• Top-ups and Auto Top-up. Admins “buy credit with one-time top-ups” or turn on Auto Top-up, which tops the balance back up when it drops below a threshold¹; “top-ups add prepaid credit to your subscription” and sit outside the included weekly pool⁵. Where it stops: credit funds additional usage past the pools. It does not enlarge any seat’s weekly pool⁵.
• Spend alerts. Email or Slack notifications when “additional usage spend” reaches a threshold, team-level or member-level, with the admin choosing who is told⁷². Where it stops: “Spend alerts don’t stop usage"⁷, and they count additional usage only, prepaid-credit usage on The X Subscription, never included usage⁷.
• The dashboard. It “shows how much of your weekly pool you’ve used, the next reset date, and your prepaid credit"⁴; admins see team usage under Usage at grok.com/dashboard¹, the billing view splits into “Included Usage, covered by your subscription, and On-Demand Usage, charged above it"⁵, and plan, payment method, invoices and prepaid credit live at grok.com/dashboard/billing¹⁷. Where it stops: it shows. It does not decide.
• Analytics. A daily usage chart over the preceding 365 days, filters of up to ten users and 90 continuous days, CSV download per chart, and data collected only from clients on version 1.5 or higher¹⁰. Enterprise admins can filter by user or by product surface¹⁴. Where it stops: the same place.
• Model controls. Admins can force Router as a soft default or a hard lock²¹, and set allow lists and block lists at the model and provider level¹⁴. Where it stops: a cheaper model slows the meter for everyone equally. It does not change who runs out first.
• The Admin API. The page states no plan requirement for the API as a whole; the write endpoints are marked Enterprise only¹¹. It returns per-user on-demand spend in cents and total spend including included usage, daily per-user usage over at most 30 days, per-request usage events with model, tokens and charged cents, and it can set a per-user spend limit¹¹, at a default rate limit of 20 requests a minute and a recommended polling cadence of once an hour¹¹. Where it stops: it reads usage and writes ceilings. There is no call that moves allowance.
• Pooled usage. Enterprise’s answer to the per-seat wall: a shared pool instead of fixed per-user allocations¹². The stated reason is that without it “unused capacity from team members can’t be redirected to those doing the most demanding work"¹². The pool is a commitment for the contract period, tracked across the full term rather than month by month¹². Where it stops: precommitted usage not used within the term does not roll over¹³, and the same per-member limits still decide when a member stops⁶.

Five things to check before the next weekly refresh

1. Confirm how additional usage is funded, and who can change it. On The X Subscription there is no on-demand switch: there is a prepaid balance, topped up manually or by Auto Top-up¹. An empty balance with Auto Top-up off means every seat stops at its weekly pool; a funded balance means the monthly additional-usage limit needs setting before the first member crosses it, because a member past a limit is paused until the next period⁶. Set the admin-only toggle if Members should not be the ones deciding⁶.
2. Re-seat on the weekly structure, not the monthly one. Pools refresh weekly¹ and the third-party allowance is gone¹, so a member who fit the old two-pool month may sit differently now. Cursor’s own sizing: “Premium suits new Agent users, Super suits daily Agent users,” and “Ultra suits power users running several agents or Automations"³; the dashboard shows the pool used and the next reset date per seat⁴.
3. Check the default routing and the model lists. Balance and Intelligence bill at the routed model’s list price while Cost mode draws from the pool as a Cursor-model request with no Token Rate¹⁵, a Fast variant costs more per token, twice as much on Grok 4.6³, and third-party tokens carry the Token Rate on top⁸. Cost mode and a block list are two of the few levers that work without changing anyone’s behavior.
4. Look at the distribution, not the average. The analytics charts export to CSV¹⁰, the Admin API returns each user’s spend in cents for the current cycle¹¹, and spend alerts can be set per member⁷. A small number of power users drive the majority of spend²; the question is which of your seats they are, and which seats are sitting on an untouched weekly pool.
5. If you are on Enterprise, know the term. The pool is committed for the contract period¹², unused precommitted usage does not roll over¹³, an invoice is issued for it at term end¹³, and if active users exceed the licensed seat count in a true-up period, extra seats and proportional usage are invoiced¹³. Renewal is automatic unless written notice is given at least 30 days before the expiry date¹³.

The part nobody has solved

Every native control, the additional-usage limit, the per-member defaults and overrides, the alerts, the model lists, is a ceiling. Ceilings stop spending, and none of them moves unused included usage to the member who ran out. On Teams the shape is stated directly: “seats don’t share weekly pools with each other, and usage doesn’t transfer between team members"¹, and the pool “refreshes weekly"¹, so what the monthly structure forfeited once a cycle this one forfeits every week. Enterprise pooling removes the per-seat wall and replaces it with a contract-term commitment and the same per-member ceilings¹²⁶. Both results are true in the same organization, in the same week: a pool refreshing unused on one seat, a blocked engineer on the next. The same is true of the other vendors’ controls, which ship their own ceilings.

We are building Spillway Ops for that missing route: allowance that would otherwise refresh unused flows to the members who ran out, so spend falls without anyone losing a tool. It reads usage metadata and sets per-user limits through vendor admin APIs with no repository access, no prompt contents, no code. The Cursor connection is planned. On Enterprise, the Admin API’s per-user spend reads and per-user spend limit writes are the documented path¹¹; the Teams docs now describe per-member limits and overrides on Teams as well¹. If the move to The X Subscription is about to be a conversation at your company, we would genuinely like to hear how it goes.