DigiUsher - Connecting a Cursor account

Connect your Cursor team to DigiUsher with a Team Admin API key to track usage-based AI coding spend per developer and per model.

Overview

To connect your Cursor team to DigiUsher, create a Team Admin API key in the Cursor dashboard. Then enter that key in DigiUsher. This page gives the access that DigiUsher asks for, the reason for that access, and the credential that you enter.

A Cursor team is required

This feature does not work with an individual account. You need a Cursor Team plan, which Cursor called Business before, or a higher plan. At least one member must have the Team Admin role. The individual plans, Free and Pro, give no access to the Admin API.

Summary of Access Required

Component	Details
Identity	Team Admin API key (prefix `crsr_`) for programmatic access only
Access level	Read-only. Team roster and usage-based cost data
Data	Daily usage and cost data
Scope	A single Cursor team. The key carries its own team scope

Capability	What It Provides
Billing data	Cost analytics, chargeback and showback, budgeting, forecasting, anomaly detection
Per-user attribution	Cursor spend attributed to each team member
Model breakdown	Cost split by model and token usage

DigiUsher cannot send requests, cannot consume tokens, and cannot create, change, or delete anything in your Cursor team.

Prerequisites

Information to Gather

Item	How to Find	DigiUsher Field
Team Admin API Key	Cursor dashboard > Settings > Advanced > API Keys > create a Team Admin API key. The page shows the key one time only, so save it in a safe place.	`api_key`

Roles Required by the Person Performing Setup

Role / Permission	Why
Team Admin on the Cursor team	Only team admins can create Team Admin API keys.

Network & Email Access (For Regulated Environments)

If your organization restricts outbound internet access or email domains, make sure that these two items are in place before you start:

Domain allowlist. Add *.digiusher.com to the allowlist of your network and your firewall. The users of your organization can then open the DigiUsher platform in their browsers.
Email allowlist. Add digiusher.com as a permitted sender domain in your email security gateway. DigiUsher sends onboarding confirmations, alerts, and reports from @digiusher.com addresses.

Setup

Make Sure You Have a Team and Admin Access

The Admin API works at the level of the team. You must therefore work in a Cursor team and have the Team Admin role.

Sign in to the Cursor dashboard with an account that has the Team Admin role.
Make sure that you work in a Cursor Team plan, and not in an individual plan.
Make sure that your role is Team Admin. If it is not, ask a team admin to give you the role, or to do the next step for you.

Don't see API Keys?

If the API Keys option does not appear under Settings > Advanced, your account does not have a Team plan or a higher plan, or you do not have the Team Admin role.

Create a Team Admin API Key

Create a separate Team Admin API key for DigiUsher. DigiUsher uses this key for read operations only.

In the Cursor dashboard, open Settings > Advanced > API Keys.
Create a new Team Admin API key. Give it a name that you know again, for example digiusher-cost-reader.
If the dialog has a scope control, select Read-only.
Copy the value of the new key. It starts with crsr_.

Save your credential

CAUTION: Copy the Team Admin API key now and save it in a safe place. The page shows the key one time only, and you cannot read it again. You enter this key in DigiUsher in the next section.

Connect in DigiUsher

In DigiUsher, go to Connectors > Add Source and select Cursor. On the Configure step, enter the values in the table. Then go to Connect and click Connect source:

Field	Where to Find
Display Name	Any label you prefer, for example `Cursor Engineering`
Team Admin API Key	The `crsr_...` key from Step 2

At the connection, DigiUsher makes sure that the key works with the roster of your Cursor team, and it finds your team members. It can then attribute the cost to each user. The first sync reads the usage-based cost of the last 3 calendar months: the current month and the two months before it. Every sync after the first one reads only the last 7 days of completed usage. DigiUsher therefore gets the recent corrections, and it does not read the whole month again.

Setup Checklist

You work in a Cursor team, and not in an individual plan
You have the Team Admin role on the team
Team Admin API key created in the Cursor dashboard with the prefix crsr_
Team Admin API key saved in a safe place
Connection details entered in DigiUsher
*.digiusher.com in the allowlist of your network and firewall (if your organization restricts this)
digiusher.com in the allowlist of permitted sender domains in your email security gateway (if your organization restricts this)

Security

What DigiUsher CAN Access (Read-Only)

The roster of your Cursor team, which DigiUsher uses to attribute the cost to the correct user
The usage-based cost data of each user for each day, with the model and the token usage
The email address of the member on each usage event. DigiUsher stores it as the resource identifier of that spend

What DigiUsher CANNOT Do

Send a request or consume tokens in your Cursor team
Create, change, or delete an API key, a team member, or a team setting
Read your source code, prompts, completions, chat history, or repositories
Read or change the billing configuration, the payment methods, the seat counts, or the plan limits
Buy a product or change your account

DigiUsher stores the Team Admin API key encrypted, and it never returns the key in an API response.

Member email addresses are stored

DigiUsher stores the Cursor member email of each usage event as the resource identifier of that cost. It can then attribute the spend to a person in the cost reports and in the chargeback. A row from a service account, a cloud agent, or an automation gets that resource type in place of User.

Monitoring

Open the API keys in the settings of your Cursor team to see the keys that exist and the last time each key was used. Delete every key that you do not know.

Credential Rotation

In the Cursor dashboard, create a new Team Admin API key.
Enter the new key in DigiUsher immediately.
Delete the old key in the Cursor dashboard.

Avoid ingestion gaps

Create the new key and enter it in DigiUsher before you delete the old key. This prevents an interruption of the data collection.

Make sure that the key starts with crsr_. A personal key does not work, and a key without admin rights does not work.
Make sure that a member with the Team Admin role created the key, and that the key still exists in the Cursor dashboard.
Create the key again in the Cursor dashboard and enter it again in DigiUsher.

Cursor API rejected the verification request

Make sure that the key is still active and not revoked.
Make sure that your team has a Cursor Team plan or a higher plan. The Admin API needs this plan.

Could not reach the Cursor API

This is usually a temporary network fault. Try the connection again.
If the fault continues, make sure that your network policy does not block the outbound access to api.cursor.com.

No cost data appearing

If your team used Cursor in no part of the period, DigiUsher has no cost data to show.
DigiUsher reads only completed UTC days. The usage of today therefore appears at a later sync.

Need Help?

If this page does not answer your question, write to DigiUsher support at support@digiusher.com. The team will help you.

Connecting a Cursor account