Cursor & external AI

External AI

Sync Cursor team usage via Admin API or CSV, roll up spend and activity by developer and team, and correlate IDE AI with commits — separate from platform AI credits.

Engineering teams increasingly rely on IDE AI tools alongside platform analytics. Engineering Analytics connects Cursor team usage so spend, token consumption, and activity roll up next to commits and pull requests.

External AI data is kept separate from Engineering Analytics platform AI credits. Administrators map Cursor members to developers and teams for organization-wide attribution — with dev×repo matrices clearly labeled as inferred correlation, not native Cursor telemetry.

What you get

  • Hourly Admin API sync or CSV import for Cursor team daily usage and spend
  • Rollups by developer, team, and organization with mapping via email
  • Dev×repo attribution matrix correlating IDE AI activity with same-day commits
  • Dedicated External AI dashboard with spend and activity trends
  • Ask the AI assistant about Cursor usage alongside delivery metrics

Highlights

Separate metering

Cursor sync does not consume platform AI token credits.

Team rollups

Map members to your developer roster for fair comparisons.

In context

See IDE AI next to commits, PRs, and pipelines.

Related capabilities

Source sync

Connect Azure DevOps or GitHub, import commits, pull requests, work items, pipeline runs, and deployments, then keep everything current with incremental sync.

Leadership dashboards

Executive, engineering, repository, team, vendor, pull request, work item flow, pipeline, and deployment views with trends, KPIs, and activity heatmaps.

CI/CD & delivery

Azure DevOps Pipelines, GitHub Actions, and release deployments in one place — success rates, duration trends, deployment frequency, and delivery gaps.

Start using cursor & external ai in your organization

Create a free workspace, connect your sources, and explore Engineering Analytics with your team's real data.

Get started free Sign in