Cursor

Cursor spend by member and model, from your team's admin API

AI Connects with Admin API key

Costfluent reads your Cursor team's usage-based spend per UTC day, by model and by member. The “AI spend” dashboard, cost reports and budgets work from it, beside your cloud and other AI costs.

Permanent Free plan with no time limit

What arrives

One Cursor team's requests, added up per day

Spend and tokens by model

Cost and tokens arrive per model as Cursor names it, tagged ai:model and ai:model_provider where Costfluent recognises the model. Requests your plan includes arrive at zero cost; seat fees are not in Cursor's admin API and do not arrive.

Members and service accounts

The ai:user tag names the member behind the requests. A service account's requests carry the account as their resource instead.

US dollars, as Cursor charges them

A day's cost is the sum of what Cursor charged for each usage event, in US dollars.

IDs, not email addresses

A member appears by Cursor ID, never by email address or name. A service account appears under its name.

What you do with it

Per member, per model, against a budget

Cursor spend in the AI spend dashboard

Cursor spend counts in the “AI spend” dashboard, by model where Costfluent recognises the model. Cursor charges per request, so its cost per million tokens is a blended rate.

Cursor spend per member

Group a cost report by the ai:user tag, then by SKU, to see what each member spent on which model. Save the view for the next team review.

A budget on Cursor spend

Set a budget on a saved report filtered to Cursor, and follow actual spend and the forecast through the period.

How Costfluent connects

One team, one admin API key

  • A team admin creates the key under “API Keys” in the Cursor dashboard, for a team whose plan includes the admin API, which Cursor lists for “Enterprise” teams. Cursor documents its admin:* scope, which can also change members and settings: where offered, create a key that can only read (read:*), and only for Costfluent.
  • Costfluent stores the key encrypted and uses it for three reads only: the key's team, its member list and its usage events. Email addresses become Cursor IDs while it reads; no member's address or name is stored, logged or shown.
  • A connection syncs once a day by default and can be set as often as hourly. Costfluent reads a page of usage events before saving, so a connection that saves can read your spend.
  • Connecting imports your plan's backfill, at most six months, as far back as Cursor reports usage events. The gear icon beside the connection shows which months have been imported.

Related pages

  • AI cost tracking

    Where AI spend arrives from, the cloud bills and the AI providers, and how its lines are tagged by model.

  • LLM prices

    The price per million input and output tokens of the models on Amazon Bedrock, Azure and Vertex AI, in euro.

  • LLM cost calculator

    Tokens in and out a month give a model's monthly cost in a European region.

  • Budgets

    Set a workspace budget and follow actual spend and the forecast against it.

  • For engineering teams

    Explain cost changes and assign ownership without a FinOps team.

Track your Cursor team's costs

Start on the permanent Free plan and connect your Cursor team with an admin API key.

Permanent Free plan with no time limit

We value your privacy

We use essential storage to operate the site and, only if you allow it, Google Analytics to understand how it is used. Read more in our Privacy policy.

Cookie preferences

Essential cookies Always on

Required for the website to function properly. These cannot be disabled.

Google Analytics

Records page views and four named actions: sign-up and demo clicks, contact form submissions and lead requests. Google's script and its _ga cookies load only after you allow them. We do not send account, tenant, form, or resource identifiers.