Cursor usage dashboard
for engineering teams.

How to check your Cursor usage

Your own usage is on cursor.com/dashboard, under Usage or Spending, and in the editor's settings. It shows each pool's remaining allowance, any on-demand charges and the cost of each request; the reset date is on the Spending tab. Cursor splits usage into two pools:

Cursor publishes no number for a plan's included usage: the models you pick decide how fast it runs out. What each plan includes is on Cursor pricing.

• Cursor Models: Cursor's own pool, with models such as Composer and Grok.
• Other Models: third-party models, charged at each model's API price.

The Cursor team analytics dashboard

On Teams and Enterprise, cursor.com/dashboard/analytics shows admins every user's data and members their own, from Cursor 1.5 or later. Filter by up to 10 users and 90 days, and download any chart as a CSV. It shows:

• AI share of committed code: the lines changed in commits, and the share Cursor generated.
• Agent edits and Tab completions, suggested and accepted.
• Messages sent, by mode (Agent, Ask, Cmd+K) and by model.
• Active users, and daily usage over the past 365 days.
• A usage leaderboard of the top users and their favorite model, which every member can see.

Cursor Admin API

An admin creates a key under cursor.com/dashboard, then API Keys, and calls https://api.cursor.com with it as the basic-auth username. Cursor's API overview lists the Admin API for Enterprise teams. Three endpoints cover usage:

• POST /teams/daily-usage-data: per user and day, lines added and accepted, Tab accepts, agent, chat and Cmd+K requests, and the most used model. Up to 30 days per call, aggregated hourly.
• POST /teams/filtered-usage-events: each request with its model, its input, output and cache tokens, and its cost.
• POST /teams/spend: each member's spend in the current billing cycle.

curl -X POST https://api.cursor.com/teams/daily-usage-data \
  -u YOUR_API_KEY: \
  -H "Content-Type: application/json" \
  -d '{
    "startDate": 1710720000000,
    "endDate": 1710892800000,
    "page": 1,
    "pageSize": 1000
  }'

Cursor Analytics API

The Analytics API, for Enterprise teams only, returns the dashboard's numbers as JSON: team totals under /analytics/team/ and one row per person under /analytics/by-user/. It covers agent edits, Tab use, daily active users, models, MCP servers, skills, commands and the leaderboard, up to 30 days per call. The AI Code Tracking API, in alpha, goes down to each commit: lines from Tab, from the agent and from people.

curl -X GET "https://api.cursor.com/analytics/team/dau?startDate=14d&endDate=today" \
  -u YOUR_API_KEY:

curl -X GET "https://api.cursor.com/analytics/by-user/agent-edits?page=1&pageSize=50" \
  -u YOUR_API_KEY:

Cursor usage tracking with Zest

Cursor's dashboard and APIs describe Cursor. They don't show the Claude Code or Codex sessions the same engineer runs, or which sessions ended in a merged pull request. Each engineer installs the Zest extension in Cursor with one click (setup). It reads Cursor's local chat history (composer conversations and agent transcripts) and syncs each session with its models and timings; optionally, it adds each session's tokens and cost from Cursor's usage dashboard.

Cursor is the agent our own team runs least: it co-authored 7 of the 3,192 commits in our two repos from July 5 to October 3, 2026. What this page says about Cursor comes from Cursor's docs and the extension's code, not from our usage.

• Skills and MCP tools in each Cursor session, rolled up per engineer in the AI Stack view.
• Cursor next to Claude Code, Codex and Copilot on the same dashboard, so Claude Code vs Cursor or Cursor vs GitHub Copilot is answered on your own team's work.
• With the Zest GitHub App, each engineer's Cursor sessions sit next to the pull requests they opened and merged.
• Redaction runs on the engineer's machine before upload; no code diffs are sent.