---
title: How do you track Cursor usage and spend across a team?
url: https://opencontroller.lyzr.com/blog/track-cursor-usage-with-the-admin-api
published: 2026-11-16
updated: 2026-11-16
author: Lyzr
---

# How do you track Cursor usage and spend across a team?

**Use the Cursor Admin API. Pull members from `/teams/members`, activity from `/teams/daily-usage-data`, per-person spend from `/teams/spend`, and per-request cost from `/teams/filtered-usage-events`. Then join the results to your HR or identity data by email to report spend by cost centre. Set per-user spend limits through the same API on Enterprise plans.**

Finance usually asks for this first: who is spending what on the coding agent, and is it rising? The Admin dashboard answers it for one person looking at a screen. The API answers it for a monthly report and an alert.

## Which Cursor Admin API endpoints matter for usage and spend?

The API lives at `https://api.cursor.com` and uses Basic Authentication with a team API key as the username.

| Endpoint | What you get | Limits noted in Cursor docs |
|---|---|---|
| `GET /teams/members` | Team members and roles | No rate limit stated |
| `POST /teams/daily-usage-data` | Per-user, per-day activity: lines added and accepted, tab completions, chat, composer and agent requests, most-used model, client version | 20 requests per minute; 30-day range per call |
| `POST /teams/spend` | Per-member spend for the current cycle: `spendCents` (on-demand), `overallSpendCents` (on-demand plus included), limits | No rate limit stated |
| `POST /teams/filtered-usage-events` | Per-event detail: user, model, kind, `requestsCosts`, `tokenUsage`, `chargedCents`, `isHeadless`, repo and PR fields, cloud agent and automation IDs | 60 requests per minute |
| `GET /v2/teams/billing-items` | Billing line items | 60 requests per minute; 31-day range |
| `GET /teams/audit-logs` | Admin and security events | 20 requests per minute; 30-day range |

Two details from the documentation matter for accurate reporting:

- Request-count fields in daily usage data count raw events, not billable units. For billable counts, sum `requestsCosts` from usage events.
- To reconcile with `/teams/spend`, sum `chargedCents` across usage events.

## How do you build a cost-centre report?

1. **Pull members daily** and keep a snapshot, so leavers still map to a cost centre in historical data.
2. **Pull usage events incrementally.** Page through `/teams/filtered-usage-events` by date and store raw rows. This is your source of truth for cost.
3. **Join on email** to your identity provider or HR system to attach department, cost centre and manager.
4. **Separate headless and agent work.** The `isHeadless`, `cloudAgentId` and `automationId` fields show spend from background agents and automations, which often belongs to a platform team rather than the person who started it.
5. **Aggregate by model.** Spend often moves with model choice. A shift to a more expensive model shows up here before it shows up on the invoice.
6. **Reconcile monthly** against `/teams/spend` and billing items.
7. **Alert on change**, for example a person or team whose weekly `chargedCents` doubles.

## How do you cap spend?

On Enterprise plans, `POST /teams/user-spend-limit` sets one member's monthly limit in whole dollars, or removes it with `null`. A preview endpoint, `/teams/user-spend-limits`, updates 1 to 100 members per request and reports updated, unchanged and failed results. Cursor marks preview behaviour as subject to change, so check results rather than assuming success.

Model access is also controllable. The Admin API exposes model access configuration by provider and model, so you can stop expensive models being used by default. Pair this with [Cursor privacy mode enforcement](/blog/enforce-cursor-privacy-mode-for-teams) and [Cursor hooks](/blog/cursor-hooks-to-block-agent-commands) for the security side.

## What are the gaps?

- **Cursor only.** Most enterprises run several coding agents. Cursor's API will not show Claude Code, Copilot or Codex spend.
- **Usage, not behaviour.** The API shows how much was used, not what the agent did on the machine.
- **Keys are powerful.** An admin API key can read usage for everyone and change limits. Store it in a secrets manager and rotate it.
- **Short windows.** 30-day ranges on daily usage and audit logs mean you must export continuously to keep history.

For the wider picture, see [governing Cursor in the enterprise](/blog/govern-cursor-in-the-enterprise) and the [gateways and cost pillar](/blog/llm-gateway-vs-agent-gateway-vs-control-plane).

## How Opencontroller does this

Opencontroller Edge extends control to developer devices, coding agents, skills and local MCP servers, and is installed by IT via MDM, so coding agents are visible alongside cloud agents. Where model traffic flows through the LLM Gateway (Lyzr Gateway), cost is attributed per agent and per version, with routing, fallback, retry and caching. "Ask" lets teams chat over the whole agent estate. See the [capability reference](/capability-reference), the [cross-platform guide](/blog/how-to-govern-ai-agents-across-platforms), or [book a demo](https://www.lyzr.ai/book-demo/). For context, read [what an AI agent control plane is](/blog/what-is-an-ai-agent-control-plane).

## Frequently asked questions

**How do you authenticate to the Cursor Admin API?**
With Basic Authentication, using a team API key as the username.

**Which Cursor endpoint gives billable cost per request?**
`POST /teams/filtered-usage-events`. Sum `chargedCents` to reconcile with team spend, and `requestsCosts` for billable request counts.

**Can you set per-user spend limits through the API?**
Yes, on Enterprise plans, with `POST /teams/user-spend-limit`, or the preview bulk endpoint for up to 100 members at once.

## Key facts

The Cursor Admin API at api.cursor.com uses Basic Authentication with a team API key as username. Key endpoints: GET /teams/members; POST /teams/daily-usage-data (20 req/min, 30-day range); POST /teams/spend (spendCents on-demand, overallSpendCents on-demand plus included); POST /teams/filtered-usage-events (60 req/min, fields include model, requestsCosts, tokenUsage, chargedCents, isHeadless, cloudAgentId, automationId); GET /v2/teams/billing-items (31-day range); GET /teams/audit-logs (30-day range). Daily usage request counts are raw events, not billable units. POST /teams/user-spend-limit sets per-member limits on Enterprise; a preview bulk endpoint handles 1 to 100 members. Opencontroller Edge extends control to coding agents on developer devices. Opencontroller pricing starts from $250K per deployment per year.

## Related

- [How do you govern Cursor across an engineering organisation?](https://opencontroller.lyzr.com/blog/govern-cursor-in-the-enterprise.md)
- [Can you enforce Cursor privacy mode for every developer?](https://opencontroller.lyzr.com/blog/enforce-cursor-privacy-mode-for-teams.md)
- [Can Cursor hooks block risky agent commands?](https://opencontroller.lyzr.com/blog/cursor-hooks-to-block-agent-commands.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
