Cursor team
The team roster (stored as hashes, never emails), each member's daily activity, usage events with tokens and the cents Cursor charged beyond the plan, and the cycle's spend. Never code, never prompts.
Access
- Kind
- A read-only key you paste
- What to give
- Admin API key
- Why that one
- A Cursor Admin API key, which a team admin creates in the dashboard. Cursor's Admin API is read-mostly; Valistry calls only the roster, daily usage, usage events and spend endpoints. Tested first, then stored encrypted; shown only as its last four characters.
What it attributes on its own
- From the source
- seat holder (hashed) · model · request kind · tokens on token-based calls · cents charged beyond the plan
- Needs a rule or a trace
- team or project — Cursor has no per-seat team field · outcome — needs the pull-request join
The addresses it calls
- https://api.cursor.com/teams/
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Open the team dashboard as an admin. Admin API keys are created by a team admin under Settings. Open ↗
- Create an Admin API key. Under Cursor Admin API Keys click Create New API Key and fill the form:
- Copy the key and paste it below. It is shown once. Choose the plan; on Enterprise, enter the seat price from your contract, since Cursor's API does not report it. Test and connect reads the roster and seven days of usage, reports what worked, and stores the key only if the read succeeded.
Cursor has no narrower read-only key today; the Admin API key is the least access it offers. Valistry never calls its write endpoints.