Cursor pricing
for teams, October 2026.

How much does Cursor cost per month?

Every plan includes a set amount of model usage; past it, on-demand usage is billed in arrears at API prices. Per person or seat:

What does Cursor cost a team of 10?

Cursor bills per active seat, and a member added mid-cycle is prorated. On-demand usage past a seat's included usage comes on top, at API prices plus the Cursor Token Rate on third-party models.

What does the Cursor Token Rate add to a heavy month?

Our own team barely runs Cursor (it co-authored 7 of the 3,192 commits in our two repos from July 5 to October 3, 2026), so we have no Cursor bill to show. We can put the token rate on a heavy month of Claude Code tokens: it applies to cached tokens too, and those are almost all of them. Cursor's agent would not send exactly these tokens.

Cursor API pricing per token

Past a plan's included usage, Cursor bills each model per token at its API price. On Teams and Enterprise, the Cursor Token Rate comes on top for third-party models, on included, on-demand and bring-your-own-key usage alike, and when Auto picks one. Claude Opus 5.5 on a Teams seat:

cache read   $0.20 + $0.25 = $0.45
cache write     $5 + $0.25 = $5.25
input           $4 + $0.25 = $4.25
output         $20 + $0.25 = $20.25

Cursor usage limits by plan

Cursor publishes no number for any plan's included usage: every plan includes a set amount, and the models you pick decide how fast it runs out.

Pro, Pro+, Ultra and Teams seats have two pools that reset every billing cycle: Cursor Models (Grok and Composer), with much more included usage, and Other Models, the third-party models at their API price. On Teams, a seat's usage belongs to that person and doesn't move between members.

When a team member uses up the Other Models pool, Cursor switches them to Cursor Models. On-demand usage starts if they keep using other models, or use up the Cursor Models pool too: it runs at the same API rates, billed in arrears and never slowed or downgraded.

On Teams, on-demand usage is on by default, and admins can set a monthly team-wide spending limit; per-member limits need Enterprise.

Cursor's pricing page gives ratios instead of amounts: Pro+ has 3x Pro's Agent limits and Ultra 20x, and a Teams Premium seat 5x a Standard seat's.

What drives a team's Cursor bill

Four things matter most:

• Seats or usage. A seat covers its own included usage, which doesn't move between members, and on-demand usage on top is billed per token. A Premium seat costs 3 times a Standard one for 5x the usage. How a Cursor seat compares with Claude Code's and Copilot's is on Claude Code vs Cursor and Cursor vs GitHub Copilot.
• The pool. Cursor's own models (Grok and Composer) get much more included usage and skip the Cursor Token Rate; third-party models draw on the Other Models pool at their API price.
• Auto. Every Auto mode bills at the list price of the model it routes to.
• Long sessions. The token rate applies to cached tokens too, and on Claude Opus 5.5 it costs more than the cache read itself.

How to see Cursor cost per engineer

Cursor's own tools first:

• Each developer: the usage dashboard and editor settings show included usage per pool.
• Admins: on-demand usage is tracked per user in the admin dashboard, and team analytics chart agent edits, usage by model and active users, each with a CSV download.
• Admin API: POST /teams/spend returns each member's spend this billing cycle, on-demand and in total, with per-user limits on Enterprise.
• Zest: the extension reads each engineer's Cursor sessions and models (and, optionally, tokens and cost from Cursor's usage dashboard) and shows them next to their Claude Code and Codex sessions. More in Cursor usage.

curl -s -X POST https://api.cursor.com/teams/spend \
  -u "$CURSOR_ADMIN_API_KEY:" \
  -H "Content-Type: application/json" \
  -d '{"sortBy": "amount", "sortDirection": "desc", "pageSize": 100}' |
jq -r '.teamMemberSpend[] | [.email, .overallSpendCents / 100, .spendCents / 100] | @tsv'