Integrations · Agents

Track Cursor cost by project and person.

Cursor Enterprise pushes its usage over OpenTelemetry, with its own names for the same fields. Token Controller maps them, and Cursor cost lands next to every other agent.

  • DoorTelemetry push from Cursor Enterprise
  • Brings inTokens, cost, model, person, repository
  • Cost lands onProjects, by repository

From Cursor to the cost sheet.

Session files are not read, so the repository decides the project.

  1. 1

    Point the exporter

    Set Cursor Enterprise's OpenTelemetry exporter to your ingest URL with the organization token.

  2. 2

    Map repositories

    Add each repository to its project in the web app.

  3. 3

    Upload the bill

    Upload Cursor's bill as CSV once per period. The close checks it against what Cursor reported.

AgentTicketSummaryCostLKCursorSF-1Checkout button states$8.30
A Cursor session at the sample organization.
# Cursor Enterprise: point its OpenTelemetry exporter here endpoint https://app.tokencontroller.com/api/v1/ingest/otlp header Authorization: Bearer tc_org_… # the organization token is under Settings in the web app
ProviderArrived byBillCursorCSV$195.85ReconciliationAmountToken entries on projects and tickets$195.85Organization overhead, on no project$0.00Residual, what no token entry explains$0.00Equal to the Cursor bill$195.85
Cursor's bill comes in as CSV. At the close it must equal what Cursor reported.

What telemetry carries.

Numbers and identifiers only

Tokens, cost, model, person, repository, and session and message IDs. No prompt text.

Fields mapped for you

Cursor uses its own names for the same fields. Token Controller maps them, so Cursor reads like any other agent in reports.

Compare agents

Agent harness reports set Cursor next to Claude Code, Codex and the others for the same work.

In the docs

Start alone in a few minutes. Add your team when the first month closes.

No card for the free plan. Fourteen days to try the Team plan.