Cursor

The Cursor connector imports team usage from Cursor: a log of every request your team made.

Each entry already carries what it cost, how many tokens it used, the developer who made it and the model it ran on — nothing has to be shared out or estimated. Spend and tokens on your dashboard come straight from the request that caused them, so spend by person and by model are both exact rather than apportioned.

Enterprise teams only

Admin API keys are available to Enterprise teams — you must be a Team Admin to create one.

Get an Admin API key

  1. Sign in to the Cursor dashboard as a Team Admin.
  2. Open Dashboard → Settings → Advanced → Admin API Keys.
  3. Create an Admin API key (it starts with crsr_, with the admin:* scope).
  4. Copy the key — it is only shown once.

See also Cursor's Admin API docs.

Add a Credential

  1. Open Settings → Cloud Connections → Cursor
  2. Click + Add Credential
  3. Enter a display name and paste the Admin API key
  4. Click Submit

Add a Cloud Account

  1. From Settings → Cloud Connections → Cursor, click + Add Cloud Account
  2. Select the credential you just added
  3. Click Submit

Once connected, the initial import pulls up to 90 days of history (configurable on the cloud account), then imports month by month. Your data can take up to 24 hours to complete the initial import.

Attribution notes

  • Service accounts — when a request comes from a bot or automation rather than a person, Cloud Ctrl records that identity as the actor. Cursor has no project or workspace concept, so there is no project breakdown.
  • Allowance vs on-demand — each seat includes an allowance of usage. Cloud Ctrl records both kinds, but only on-demand requests add to your spend; allowance-covered requests are recorded with their tokens and $0, which is what Cursor actually charges for them. A developer working entirely inside their allowance costs $0 but may be one of the heaviest consumers on the team.
  • Models — Cursor routes requests to several underlying vendors (OpenAI GPT, Anthropic Claude, xAI Grok, Google Gemini and Cursor's own Composer). Cloud Ctrl groups models into families so spend rolls up per vendor; unrecognised models keep their exact Cursor name in an "unknown" family.
  • Discounts — Cloud Ctrl records the discounted amount you were actually charged, never the pre-discount list price.
  • Seat subscription not included — Cloud Ctrl ingests on-demand (usage-based) spend only. The fixed seat subscription ($40/user/month Standard, $120/user/month Premium) is not included, because the Cursor Admin API exposes neither the seat price nor the seat tier. To reconcile your full Cursor invoice, add the seat subscription separately.
  • Reconciling with your bill — on-demand spend reconciles to the cent, but Cursor bills on a subscription cycle that doesn't start at midnight UTC, so a calendar-month view in Cloud Ctrl differs from a Cursor cycle view by whatever usage falls in the offset. Match your date range to your Cursor cycle to compare like for like.
  • Cost centres and projects — Cursor doesn't provide these. Use Tag Mapping to map user emails or team names to the cost centres or projects you use elsewhere in Cloud Ctrl.