On this page
How much Cursor includes depends on which plan family is in use. Mixing the two is the most common way to misread the help page: a weekly pool on The X Subscription is not the same thing as the monthly Pro-style pools on legacy plans. Everything below follows Cursor’s Usage and limits help page, as of October 26, 2026 (Beijing time). Per-tier request counts and dollar allowances are not published as fixed numbers on that page; for reference only, check the live Usage / Spending UI. Those per-tier digits have not been checked on this site. Feedback from live accounts can go through the site-owner contact link in the footer.
The X Subscription: one weekly Cursor-model pool
The X Subscription covers Free, Plus, Premium, Super, Ultra, and Teams seats.
Every paid plan includes one weekly pool of usage for Cursor models—Grok 4.7, Grok 4.6, Grok 4.5, and Composer 2.5. That pool is shared across Cursor, Grok Bot, and the Grok apps. Third-party models are not drawn from that pool. On Premium and above, third-party models are billed at API list price from your prepaid credit.
To check usage, open Usage at grok.com/dashboard. It shows how much of the weekly pool you have used, the next reset date, and prepaid credit. Editor settings show the same remaining usage.
When you hit the limit, you can keep working from prepaid credit, wait for the weekly pool to reset, or upgrade. Cursor points to its Usage-based charges docs for how top-ups work. The included pool refreshes weekly; prepaid credit does not reset with that weekly refresh. Each top-up stays available until you use it or until it expires (currently 365 days after purchase).
Legacy Cursor plans: two monthly pools
Legacy Cursor plans cover Hobby, Start, Pro, Pro+, Ultra, and Teams Standard and Premium seats.
Included usage is split into two monthly pools:
| Pool | What it covers |
|---|---|
| Cursor Models | Grok 4.7, Grok 4.6, Grok 4.5, and Composer 2.5 |
| Other Models | Third-party models, charged at model provider prices |
Pro, Pro+, Ultra, and Teams include both pools. Start covers the Cursor Models pool only. Cursor’s help page also points to separate Start-for-India plan details; treat those as plan-specific, not as the default global Start rules.
Check usage on the Spending tab in the dashboard: real-time usage for both pools, remaining allowance, and any on-demand charges.
When you hit a limit, enable on-demand usage (pay-as-you-go) or upgrade. Usage resets monthly with your billing cycle; the reset date is on the Spending tab. For teams, every member resets together on the team billing cycle.
Hitting the limit, resets, and getting more
On either plan family, unused included usage does not roll over.
Ways to stretch or extend usage, as Cursor lists them:
- Prefer Cursor models (Grok 4.7 / 4.6 / 4.5 and Composer 2.5)—they draw from the included pool.
- Add prepaid credit on The X Subscription, or enable on-demand usage on legacy plans, to pay for additional requests at API rates.
- Upgrade to a higher plan for a larger included allowance.
Your model choice still affects how fast the included pool drains; Cursor says so explicitly, without publishing a public multiplier table on this help page.
Max Mode
Current plans do not include Max Mode. On legacy request-based plans, Max Mode is billed at the model’s API rate plus 20%.
Cursor Router, Auto, and your own API key
Cost mode (classic Auto) bills as a Cursor-model request and draws from your included pool, whichever model actually serves the turn. On Teams and Enterprise with Cursor Router on, Balance and Intelligence bill at the routed model’s list price: a route to a Cursor model draws from the included pool; a route to a third-party model bills as third-party usage—from prepaid credit on The X Subscription, or from the Other Models pool on a legacy plan. Individual plans have Cost mode only.
A few billing notes from the same help page:
- Composer 2.5 carries no Cursor Token Rate on any plan.
- Eligible third-party routes from Balance or Intelligence also incur the Cursor Token Rate on Teams and Enterprise; Cost mode requests are exempt, as are third-party models listed as exceptions on Models & Pricing.
- Subagents can run a named third-party model while the picker still shows Auto, Grok, or Composer—those requests bill as third-party usage at that model’s list price.
Bring your own API key: on individual plans, those requests do not count toward included usage or prepaid credit; your provider bills you directly. On Teams and Enterprise, requests with your own key still carry the Cursor Token Rate of $0.25 per million tokens when the model includes it (exceptions are listed on Models & Pricing). On The X Subscription that charge comes from team prepaid credit; on a legacy Teams plan it sits under Other Models and, when that allowance is gone, bills as on-demand if on-demand is enabled—otherwise requests stop until the next billing cycle.
Related reading
Comparing coding-agent allowances across vendors, these guides use the same “how the meter works, not invented quotas” approach: