Cursor team
Use and charges, people as codes, not names. Your Cursor team list. Per person and day: Tab suggestions shown and accepted, accepted lines and agent use. Each model's tokens and charges beyond the plan. Never code or a prompt.
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. It can also change team settings; Valistry calls only the roster, daily usage and usage events 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; Tab suggestions shown and accepted, accepted lines and agent requests per member-day; 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/
Valistry calls only these addresses. It blocks any other call and logs every call.
Connecting it
- Create an API key. In the dashboard, open API Keys. Click New API Key. Open ↗
Valistry calls the roster, daily usage and usage events, and never a write endpoint.
Settings worth turning on in the Cursor dashboard
- Set a team spend limit. Cap the team's on-demand spend each month.
- Set limits per member. On Enterprise, cap each member's monthly on-demand spend.
- Put members in groups. On Enterprise, groups carry spend limits and model access.
Questions about Cursor
What access does Valistry need?A Read-only API key, which a team admin creates in the dashboard.
Which seat price is used?Teams: the $40 list price. Enterprise: the price on your order form.
Can it split Cursor spend by team?Cursor has no team for each seat. Valistry shows spend per person and model.