How Cursor's usage limits and on-demand pricing work, and how to check your Cursor usage

Cursor runs two sets of plans side by side. Its legacy plans page says "New customers start on The X Subscription", a bundle whose "subscription, bill, usage, and top-ups are managed for that workspace at grok.com/dashboard" (What is The X Subscription?). Existing customers can stay on a legacy plan, and "Switching to The X Subscription is optional and permanent."

Sources for the table: Cursor's pricing page, Models and pricing for the annual prices, Teams pricing and Legacy Cursor plans. The pricing page also says "Third-party models are not included in the monthly prices shown and must be purchased separately". The legacy page says each new tier gives "at least twice as much coding usage with Cursor models as the legacy plan it replaces". Only Enterprise has "pooled usage shared between all users".

In Cursor's words: "Each paid plan includes one pool of usage for Cursor models. The pool is shared across everything on your subscription: Agent in the editor, CLI, Cloud Agents, Grok Bot, and the Grok apps. It refreshes weekly". "Cursor models" means Grok and Composer. Three things follow from that.

• A heavy week empties the pool for that week only, and a quiet week does not carry anything forward, because "Unused included usage does not roll over on either kind of plan". The reset is weekly, which is different from the rolling 5-hour windows that Claude Code and Codex use.
• Anything you do with a third-party model never touches the pool. It is paid for separately from the first request.
• On a Teams plan, each seat has its own pool, so one engineer running out does not affect anyone else, and an idle seat's pool cannot be used by a busy one.

Running low does not make the tool worse: Cursor says "Requests are never downgraded in quality or speed." When the pool is empty, you either wait for the weekly reset or pay from credit.

On The X Subscription

Extra usage is paid from prepaid credit. Credit pays for third-party models from the first request, and for Cursor's own models once the weekly pool is used up. "You're charged when you buy credit or when an automatic top-up runs, not in arrears", and Auto Top-up is "off until you turn it on". Credit lasts "until used or until it expires (currently 365 days after purchase)".

You cap the spending with a monthly additional usage limit. When you reach it, usage "pauses until the next month or until you raise it, even if credit remains". Cursor also says "usage can briefly exceed your spend limit", because the cap is not applied instantly.

On a legacy plan

On legacy Pro, Pro+ and Ultra, on-demand usage "must be explicitly enabled in your settings", and extra requests are "billed at API rates with no markup, in arrears each month". On legacy Teams Standard and Teams Premium, "On-demand usage is enabled by default. Team admins can disable it or set spend limits in the dashboard." On the legacy Start and Hobby plans there is no extra usage: "AI features pause until the pool resets".

The Cursor Token Rate, on team plans

On Teams and Enterprise plans, eligible third-party model requests carry a Cursor Token Rate of "$0.25 per million tokens" on top of the model's own price, including requests made with the team's own API key. It does not apply to Cursor's own models, or to third-party models "whose cache-read price is strictly below $0.10 per million tokens across every pricing tier". "Individual plans don't pay the Cursor Token Rate."

Limits for a team

On a Teams plan, Cursor's Teams pricing page says "Admins set one monthly additional usage limit for the whole team (no limit or a fixed amount), plus a default monthly limit per member and per-member overrides from the Members page". The spend-limits help page describes it differently, listing member-level limits under Enterprise, so check your own admin screen. Team admins can also turn on spend alerts, which send an email when the team's additional usage reaches a threshold. Cursor is clear that "Spend alerts don't stop usage", and individual plans do not have them.

As an individual

On The X Subscription, "Your remaining usage and next reset date are shown in your editor settings and under Usage at grok.com/dashboard". Your spend limit and top-ups are on the billing page of the same dashboard. On a legacy plan, Cursor's usage limits help page says to "go to the Spending tab in your dashboard" at cursor.com/dashboard.

As a team admin

Cursor's team analytics are "available for Team and Enterprise customers". They show each person's chats, Tab suggestions accepted, and "Agent Lines of Code: Lines of code written by the Agent and accepted", with filters for "up to 10 users and 90 continuous days", and data only from people running "client version 1.5 or higher". The analytics page shows activity, not money. Spend is in the billing section of the team dashboard, and the Teams pricing page says admins can see per-member spend through the Admin API.

Cursor's pages disagree about who can use the API. The analytics page says "Available only for Enterprise customers", while the dashboard doc says "All API endpoints are available on both Team and Enterprise plans, except for the AI Code Tracking API which requires Enterprise plan." If you are on Teams, try it before you build on it.

Cursor's dashboard shows Cursor and nothing else. If the same engineers also use Claude Code or Codex, that spending is in Anthropic's and OpenAI's own consoles, and the three totals are never added up in one place. OpenReason Intel, a dashboard for Claude Code and Codex usage, does not read Cursor. The guide on seeing Claude Code, Codex and Cursor spend in one place covers what each vendor shows today, and the guide on tools that track AI coding spend across a team lists the tools that read Cursor's data now.