Connect Cursor
Add your Cursor Team Admin API key and Cloud Sessions key so Tokenize can read Cursor usage, budgets, and cloud agent sessions.
Tokenize connects to Cursor with two keys. The Team Admin API key reads your team's members, usage, and spend limits. The Cloud Sessions key downloads transcripts from Cursor's cloud and background agents.
Who can do this: Admins in Tokenize. You also need admin access to your Cursor team.
What each key unlocks
| Key | What it unlocks in Tokenize |
|---|---|
| Team Admin API | The member directory, Cursor usage reports, and reading and changing per-person budgets |
| Cloud Sessions | Transcripts for Cursor cloud and background agent sessions, shown in Sessions |
The Cloud Sessions key only works alongside a working Team Admin API key. Add the Team Admin API key first.
To capture sessions people run in Cursor on their own computers, you also need the desktop app and Cursor hooks.
Add the Team Admin API key
- In the Cursor Dashboard, create a team Admin API key.
- Copy the key.
- In Tokenize, go to Settings → Providers. In the Cursor section, paste the key into API key under Team Admin API and click Save.
Add the Cloud Sessions key
Use a service-account key with Cloud Agents access.
- Open the Cursor Dashboard and select your team.
- Open Integrations or Settings → Service Accounts. Create a service account.
- Grant Cloud Agents read or invoke access.
- Generate a key and copy it.
- In Tokenize, paste it into API key under Cloud Sessions and click Save.
If your team has no service accounts, create a key under Integrations → User API Keys instead. A user key is tied to the account that created it, so a service account is the better choice when you have one. Cursor's authentication documentation has more detail.
Check the connection
After you save, each panel shows the key's last four characters, a status badge, and the results of the access check:
- Team Admin API checks "Member directory", "Usage reports", "Read budgets", and "Change budgets".
- Cloud Sessions checks "Agent listing" and "Session access".
If you see "Cloud-agent capture is off. Add and verify the Cursor Admin API key above." the Cloud Sessions key is fine but the Team Admin API key is missing or failed its check. Add or replace the Team Admin API key.
For badges and error messages, see Provider key errors.