AI integration
Cursor and Pacia
Cursor usage read from its team API and trended alongside your other AI tooling, so the adoption question is answered across every provider at once rather than one vendor dashboard at a time.
What Pacia reads from Cursor
Team usage and active user counts
Adoption over time, per team where mapping exists
Connecting it
Connect from AI Adoption → Providers 3 min
An organisation owner supplies a Cursor team API key. It is encrypted at rest and never returned in any API response.
Usage accumulates daily
Cursor keeps its own provider row and trend; the overview recomputes combined rates from the underlying counts rather than averaging averages.
Limits, stated up front
Every integration page on this site lists what the integration does not do. Finding that out during a trial is worse for both of us than finding it out now.
Aggregate team analytics only — no prompts, completions or code.
The metrics each AI provider exposes genuinely differ, which is why they are never blended into a single misleading adoption number.