Integrations / Cursor
Cursor
Seats paid vs used, spend per person, and the wrapper's cut on the invoice.
Why connect it
Cursor bills per seat plus on-demand usage, and adds its own Token Rate on top of third-party model calls. The Admin API exposes all three, so the questions a leader actually asks — who's using it, who's spending, what's the markup — have numbers.
What you'll see
- Every team member with 30-day activity and last active date
- Spend per member this billing cycle
- The Cursor Token Rate across recent usage events: the wrapper's margin, itemised
- Idle seats and spend concentration as findings
What the credential can and cannot do
Where to get it: cursor.com/dashboard → Settings → Cursor Admin API Keys (team admins). Choose the read-only scope. Starts with key_.
It grants: Read on team members, usage, and spend.
It cannot: With a read-only key, nothing can be changed. GitDoctor never sets spend limits or blocklists.
Whatever you connect lives in an encrypted cookie in your browser and nowhere else. Sign out and it's gone; revoke it at the provider and it stops working immediately.