Skip to content

Cursor Admin API: connect your team

Idun Cockpit reads Cursor usage through your team’s Admin API, with a key a team administrator creates in the Cursor dashboard. The Admin API gives usage per person and per day, models and spend, but not the text of conversations. On Cursor Enterprise, the Cockpit also reads conversations, through Cursor’s OpenTelemetry export, with nothing to install on workstations. It is one of the sources of the real AI usage audit.

  • A Cursor team, with an administrator who can create API keys.
  • For conversations: the Cursor Enterprise plan, and the collection address and access token we give you at the start of the audit.
  1. Create an Admin API key

    In the Cursor dashboard, the team administrator creates a key for the Admin API.

  2. Send it to us

    Send the key through the channel agreed at the start of the audit, never by email.

Data What it tells you
Members Who is in the team, with their role.
Daily usage Per person: lines of code changed, number of requests.
Usage events Per request: the model, tokens and what it cost.
Spend What the team spent in the current billing cycle.

Cursor sends the text of requests and responses from its own servers to the collection address we give you. Nothing is installed on workstations.

  1. Create the destination

    A team administrator opens “Team Settings”, then “OpenTelemetry Export”. They create a destination with the collection address and access token we give you, test the connection, then enable the destination.

  2. Allow conversation content

    On the same page, they turn on “Allow conversation content export” for the team, then “Conversation content” on the destination. Requests and responses are then sent; tool inputs and outputs stay off.

  3. Check that data arrives

    After a first conversation in Cursor, the Cockpit’s Data sources screen shows the source and the date of its last send.

  • Measured: each request and each response of Cursor’s agents, in the editor, the CLI and the SDK. Cursor removes the secrets it recognizes from the text before sending.
  • Not retroactive: only conversations after the export is turned on are sent.
  • Not in Privacy Mode (Legacy): a team in this mode cannot allow the conversation export, and a member’s conversations in this mode are never sent.
  • Not covered: Tab and inline edit, which do not go through a conversation with the agent.

Outside Cursor Enterprise, and to measure usage from before the export was turned on, an official script is needed on developers’ workstations. We decide on it together at the start of the audit, and developers are told beforehand.

Without the export or the script, what does the Cockpit measure?

Section titled “Without the export or the script, what does the Cockpit measure?”

Adoption and cost: who uses Cursor, how much, with which models, and for what spend. Not the tasks handed to Cursor.

To see what the tool shows on your own tools, book a call.