Cursor spend per developer

In short: paste a Cursor Admin API key on the Sources page. FiscaLLM reads every usage event of your team, with the member's email, the model, tokens and cost, and shows it next to your other AI tools.

Beta. This source is built and tested against the format Cursor publishes, but has not yet been run against a live account. If something looks off, open an issue.

Set it up

Create an app in FiscaLLM (free).
In Cursor: team Settings, Advanced, Admin API Keys, Create new API key. Only team admins can create one. (open)
Paste the key on the app's Sources page under Cursor and press Connect. The key is checked, stored encrypted, and used only to read usage. The last 30 days are read at once, then new usage once a day.

What is read

Who: The team member's email.
Cost: What Cursor charged for each request; for requests covered by the plan, Cursor's model cost.
Prompts, code and responses are never read or stored.

Limits

Needs a Cursor team and an admin to create the key.
Read once a day, and when you press Sync now. Cursor's own data is about an hour behind.

Using more than one AI tool? Each one is a source you turn on in the same app, and the overview shows the cost of each tool, developer and model side by side. See all integrations.

Questions

What does it need?

A Cursor team (Teams or Enterprise) and an Admin API key, which a team admin creates in the team settings. Nothing is installed on developers' machines.

Which amount is shown?

What Cursor charged for each usage-based request. For requests included in the plan, the model cost Cursor reports, which shows what that usage is worth.

How fresh is it?

Read once a day and whenever you press Sync now. Cursor's own data is about an hour behind, so the last two hours come with the next sync.

Cursor already has a usage page. Why this?

To see Cursor next to the other AI tools your team uses, such as Claude Code and Codex, per developer, with budget alerts. If your team uses only Cursor, its dashboard may be enough.