How to Check Cursor Usage and Costs (3 Methods)

A Cursor Teams bill has two halves, a fixed charge for seats and an on-demand charge for anything past each seat’s included allowance. Cursor’s help center notes that on-demand usage is on by default for Teams. Nobody has to sign off before that second half grows.

Checking Cursor usage got harder in summer 2026, when the Usage page on Teams plans switched to a token view. According to a Cursor staff reply on the Cursor forum, dollar figures moved to the Spending tab and to Members > On-Demand.

Cursor admins now have three ways to read seats, usage, and spend for a team. The Cursor usage dashboard is enough for one team’s numbers. Torii puts Cursor seats and billed spend in one view beside your other apps, while the Cursor Admin API sends the raw data into whatever reporting you build yourself.

What Drives Your Cursor Bill?

Seats are the fixed part of the bill, and Cursor’s Team Pricing docs list a Standard seat at $40 per user a month and a Premium seat at $120 with 5x the included usage of a Standard seat. Annual billing lowers those to $32 and $96, per Cursor’s June 2026 pricing announcement. Our guide to managing Cursor Business and Enterprise plans covers choosing between them.

The same pricing page says Cursor bills per active paid seat, so the count follows who is on the team that cycle, and Unpaid Admins (billing-only admins who don’t take a seat) are never billed. Enterprise plans work differently. They pool usage, bill by invoice or PO, and carry precommitted usage that doesn’t roll over, so the precommitted amount is the figure to track against.

Each seat’s included usage comes in two pools, Cursor Models and Other Models, which don’t transfer between members and reset every billing cycle. Past that allowance, requests move to on-demand usage, billed in arrears (charged after the usage happens). Third-party models bill at their list API price plus the Cursor Token Rate of $0.25 per million tokens, while first-party Composer and Grok models skip it (Cursor Team Pricing docs).

The June announcement names the main lever plainly: “Model choice is the most important determinant of costs.” (Cursor blog). It adds that “a small number of power users on any team tend to drive the majority of spend and unpredictable on-demand costs.” Cursor’s Developer Habits Report backs that up, with the bottom half of developers accounting for just 4.55% of AI spend.

Use the Cursor Usage Dashboard

Cursor’s team dashboard at cursor.com/dashboard holds every number below, but only Admins and Unpaid Admins can see its billing and analytics. A developer on a Member seat can sign in to the same dashboard to check their own usage and remaining included usage, with no billing view.

Source: Cursor Help, Cursor Docs, and Cursor forum staff replies, checked October 2026.

1. Sign In as an Admin or Unpaid Admin

Any Admin or Unpaid Admin login works for every step below, including the billing pages. For a finance lead who never writes code, the Unpaid Admin role gives full billing access without adding a paid seat.

2. Open the Spending Tab for This Cycle’s Totals

The Spending tab is the first stop for Cursor spending in the current cycle. Per Cursor’s help center, it shows real-time usage for both pools, the remaining allowance, any on-demand charges, and the reset date.

3. Open Members > On-Demand for Per-Person Spend

Per-person dollars sit under Members > On-Demand, where Teams admins see each member’s on-demand total for the cycle. The few heavy users behind most of the overage show up in that list.

4. Count Seats and Seat Types in Members

The Members list shows each person’s seat type, and the context menu next to a name handles the upgrade to Premium or the Remove option. Before removing someone, check whether they used credits this cycle, since that seat stays billed until the cycle ends.

5. Read Usage and Usage Analytics for Activity

On Teams plans the Usage tab now reports tokens, and the token view still shows which models a team leans on. To total spend from it, Cursor staff on the forum suggest exporting the Usage CSV and summing its Cost column.

Usage Analytics adds charts such as Active Users, Daily Usage, and Usage Leaderboard, each with a CSV download, and its filters cover up to 10 users and 90 continuous days (Cursor Analytics docs). The charts measure activity rather than dollars. Only users on client version 1.5 or higher are counted.

6. Split Included From On-Demand in Billing & Invoices

The Billing & Invoices page splits Cursor billing for the cycle into two sections, Included Usage covered by the subscription and On-Demand Usage charged above it. On-demand usage gets its own invoices and line items, separate from the subscription invoice.

Invoices download from the billing page through Manage Subscription, which opens the Stripe billing portal, and only team admins can reach it. Keep those invoices with the annual or Enterprise agreement they bill against, and our roundup of Cursor contract management tools covers tracking that contract.

7. Set a Spend Limit and a Spend Alert

Spend limits sit on the Spending tab once on-demand usage is enabled. Changes take effect immediately. On Teams the limit is team-level, so when it’s reached every member on on-demand usage loses AI features, and per-member limits are Enterprise-only. The Only Admins Can Edit Usage Settings toggle under Permissions, on the same tab, keeps other members from raising the cap.

Cursor’s spend limits page warns that “Enforcement is not instant, so usage can briefly exceed your spend limit.” Add a spend alert at a lower threshold, team-level or member-level, and Cursor emails you when on-demand spend crosses it, though the alert never stops usage.

Use Torii to Track Cursor Seats and Spend

The Cursor dashboard covers one Cursor team, while finance and IT usually need Cursor seats and spend beside every other app the company pays for, the job AI spend management tools are built for. Torii reads seats through its Cursor connector and billed on-demand cost through its AI Module.

1. Start a Free Two-Week Proof of Concept

Request Torii’s free two-week proof of concept to get the Torii account that Cursor will connect to, and have a Cursor admin ready for the next step.

2. Connect Cursor With an Admin API Key

The connection starts with an Admin API key created in your Cursor dashboard. In Torii, open Integrations, choose the Cursor tile, select Connect, and enter the key. A green checkbox appears once the sync completes.

The connector works on Cursor Teams plans as well as Enterprise, reading each user’s role, status, and license (see the Cursor integration page). Torii syncs one Cursor account, and seat changes still happen in Cursor.

3. View Cursor Seats and Spend in Torii

Cursor seats land on Torii’s Licenses page, whose Current tab shows total licenses, the license breakdown, and total cost. Seats still assigned to people who have left the company show up there as wasted licenses.

With the AI Module turned on, Torii syncs Cursor’s billed on-demand cost once a day through the same key. The module’s Cursor page shows Subscription (the seat charge from billed invoices) beside On-demand usage, with the combined USD total for the last 30 days and 12 months.

The cost sync reports billed cost at the organization level, so Torii shows no per-user Cursor dollars. Torii’s cost allocation spreads the app’s expenses across the users it reads from Cursor and rolls them up by department, cost center, or division.

Use the Cursor Admin API

The Cursor Admin API returns members, daily activity, cycle spend, and usage events, enough to rebuild the dashboard’s numbers in a warehouse or spreadsheet. Calls go to https://api.cursor.com with Basic Authentication, sending the API key as the username and a blank password.

1. Create an Admin API Key

Open API Keys in the Cursor dashboard, choose New API Key with the admin:* scope, and copy the key right away, since Cursor won’t show it again. Teams plans can create Admin API keys too, even though Cursor’s APIs overview still files the Admin API under Enterprise.

2. List Members and Seats With /teams/members

A GET /teams/members call returns each member’s id, email, name, role, and isRemoved flag, which covers headcount and roles. The docs list no seat-type field, so Standard versus Premium still comes from the Members page.

3. Pull This Cycle’s Spend per Member With /teams/spend

The POST /teams/spend endpoint returns per-member spend for the current billing cycle only, with spendCents for on-demand charges and overallSpendCents for on-demand plus included usage. Past cycles drop off, so schedule a snapshot just before each reset.

4. Pull Daily Activity With /teams/daily-usage-data

Daily activity comes from POST /teams/daily-usage-data, which takes a startDate and endDate in epoch milliseconds, 30 days at most per call (Cursor Admin API docs). Rows carry fields such as agentRequests and mostUsedModel. Leave out page and pageSize, and the call returns only members who were active in the range. The usageBasedReqs and subscriptionIncludedReqs fields count raw events rather than billable units, so don’t multiply them by a price.

5. Reconcile to the Cent With /teams/filtered-usage-events

For line-level detail, POST /teams/filtered-usage-events returns each event’s model, token counts, and chargedCents, with up to 1,000 events per page. The docs spell out the check: “To reconcile event-level costs with /teams/spend totals, sum the chargedCents field across events.”

# Read-only calls. Needs curl and jq.
export CURSOR_API_KEY="your-admin-api-key"
API="https://api.cursor.com"

# 1. Members, roles, and removed flags
curl -s -u "$CURSOR_API_KEY:" "$API/teams/members" | jq

# 2. Per-member spend for the current billing cycle (in cents)
# Paginated: repeat with page=2 and up, to totalPages
curl -s -u "$CURSOR_API_KEY:" -X POST "$API/teams/spend" \
  -H "Content-Type: application/json" \
  -d '{"page": 1, "pageSize": 100}' | jq

# 3. Daily usage for all members, last 7 days (epoch milliseconds, 30 days max)
END=$(($(date +%s) * 1000))
START=$((END - 7 * 24 * 60 * 60 * 1000))
curl -s -u "$CURSOR_API_KEY:" -X POST "$API/teams/daily-usage-data" \
  -H "Content-Type: application/json" \
  -d "{\"startDate\": $START, \"endDate\": $END, \"page\": 1, \"pageSize\": 1000}" | jq

A small Teams plan can run on the Spending tab, one team spend limit, and an alert set below it, with no other tooling. Once finance wants Cursor in the same report as the rest of the software budget, Torii holds that view. A team building its own dashboards can script the four endpoints instead. Readers comparing third-party trackers can start with our roundup of tools to track Cursor usage and spend.