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 onboard your Cursor team to DigiUsher, you create a Team Admin API key in the Cursor dashboard and provide it to DigiUsher. This document describes exactly what access is requested, why it is needed, and what credential to provide.

A Cursor team is required

This feature is not available for individual accounts. You need a Cursor Team (formerly Business) plan or above, with at least one member holding the Team Admin role. Individual plans (Free, Pro) do not expose the Admin API.

Summary of Access Required

Component	Details
Identity	Team Admin API key (prefix `crsr_`) — 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/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, consume tokens, or create, modify, 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 admin key (shown once at creation — store securely)	`api_key`

Roles Required by the Person Performing Setup

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

Network & Email Access (For Regulated Environments)

If your organization restricts outbound internet access or email domains, ensure the following are in place before starting:

Domain allowlist: Add *.digiusher.com to your network/firewall allowlist so that users in your organization can access the DigiUsher platform from their browsers.
Email allowlist: Add digiusher.com as an approved sender domain in your email security gateway. DigiUsher sends onboarding confirmations, alerts, and reports from @digiusher.com addresses.

Setup

Confirm Team & Admin Access

The Admin API operates at the team level, so you must be working within a Cursor team and hold the Team Admin role.

Sign in to the Cursor dashboard with an account that holds the Team Admin role.
Confirm you are working within a Cursor Team plan (not an individual plan).
Confirm your role is Team Admin. If it is not, ask an existing team admin to either grant you the role or perform the next step on your behalf.

Don't see Admin API Keys?

If the Admin API Keys option is not visible under Settings > Advanced, your account is not on a Team plan or above, or you do not hold the Team Admin role.

Create a Admin API Key

Create a dedicated Admin API key for DigiUsher. This key is solely used in a read-only manner.

In the Cursor dashboard, open Settings > Advanced > API Keys.
Create a new admin key and give it a recognizable name, for example digiusher-cost-reader.
If the creation dialog offers a scope selector, choose Read-only.
Copy the generated key value. It starts with crsr_.

Save your credential

The Team Admin API key is shown only once at creation and cannot be retrieved again. Copy and store it securely — you will enter it into DigiUsher in the next section.

Connect in DigiUsher

After completing the steps above, enter the following into DigiUsher to complete the connection:

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

When you connect, DigiUsher validates the key against your Cursor team roster and discovers your team members automatically, so cost can be attributed per user. The first sync backfills roughly the last 3 calendar months of usage-based cost; after that, DigiUsher ingests new cost data daily.

Verification Checklist

Working within a Cursor team (not an individual plan)
You hold the Team Admin role on the team
Admin API key created in the Cursor dashboard with prefix crsr_
Admin API key saved securely
Connection details entered in DigiUsher
*.digiusher.com allowlisted in your network/firewall (if applicable)
digiusher.com allowlisted as an approved sender domain in your email security gateway (if applicable)

Security

What DigiUsher CAN Access (Read-Only)

Your Cursor team roster, used to attribute cost to the correct user
Usage-based cost data per user per day, including model and token usage

What DigiUsher CANNOT Do

Send requests or consume tokens against your Cursor team
Create, modify, or delete API keys, team members, or team settings
Access your source code, prompts, completions, chat history, or repositories
View or modify billing settings, payment methods, seat counts, or plan limits
Make purchases or any changes to your account

The Team Admin API key is stored encrypted at rest and is never returned in DigiUsher API responses.

Developer email addresses are not stored

DigiUsher attributes Cursor cost using the Cursor user ID only. Member email addresses returned by the Cursor API are deliberately not persisted.

Monitoring

Review the API keys in your Cursor team settings to confirm which keys exist and when they were last used. Remove any keys you no longer recognize.

Credential Rotation

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

Avoid ingestion gaps

Always create the new key and update it in DigiUsher before deleting the old one to avoid an interruption in data ingestion.

Confirm the key starts with crsr_. A personal or non-admin key will not work.
Confirm the key was created by a member with the Team Admin role and that it has not been deleted in the Cursor dashboard.
Re-create the key in the Cursor dashboard and re-enter it in DigiUsher.

Cursor API rejected the verification request

Confirm the key is still active and has not been revoked.
Confirm your team is on a Cursor Team plan or above, which is required for Admin API access.

Could not reach the Cursor API

This usually indicates a transient network issue. Retry the connection.
If it persists, confirm that outbound access to api.cursor.com is not blocked by your network policy.

No cost data appearing

If your team has had no Cursor usage in the period, there will be no cost data to show.
Only completed UTC days are ingested. Usage from today appears after the next daily sync.

Need Help?

If you encounter any issues not covered above, contact DigiUsher support at support@digiusher.com and the team will help you get set up.

Connecting a Cursor account