Any Plans to Make AI Code Tracking API Available for Teams Plan?

Feature Requests
1

Feature request for product/service

API Keys

Describe the request

I’m reaching out to ask if there are any plans to make the AI Code Tracking API available for the Teams plan in the future.

For teams like ours (currently on the Teams plan with 75+ members), this API would be invaluable for several key reasons:

  • Visibility Governance: It would help us track AI-generated code across the team, ensuring alignment with internal coding standards and compliance requirements.

  • Productivity Insights: Understanding how AI suggestions are adopted (e.g., accepted/rejected ratios, most used features) would let us optimize workflows and train the team more effectively.

  • Resource Allocation: Visibility into AI usage patterns would help us allocate licenses and resources based on actual team needs, avoiding waste and ensuring equitable access.

Right now, this functionality is limited to the Enterprise plan, but for growing teams that need robust oversight without Enterprise-scale budgets, having it in the Teams plan would be a game-changer.

Would love to hear if this is on the roadmap, or if there are alternative ways for Teams plan users to access similar tracking capabilities.

2 Likes
2

I cannot agree more strongly with @songcj. This is the single most critical feature our team of 100+ engineers needs right now.

And we are clearly not alone in this. As evidenced by this previous thread (link), many other teams have already voiced strong support for this exact request, highlighting how essential this API is.

We were fortunate to use this API back when it was available on the Teams plan, and it was incredibly valuable. We were able to track, in detail, what percentage of our committed code was generated by Cursor AI.

This exact data allowed us to prove the clear ROI of Cursor to our management. It was the key justification that enabled us to successfully roll out Cursor licenses to our entire engineering organization (100+ members).

In today’s landscape of competing AI tools, the ability to measure, compare, and analyze the true productivity impact of each tool is essential for an engineering organization’s survival. We need to answer:

  • How deeply are engineers engaging with the tool?

  • Which tools, features, or workflows contribute most to the final production code?

Without this API, we simply cannot measure this ROI. This makes it impossible to justify the cost to non-technical stakeholders and secure our budget. It forces us to consider cheaper alternatives, even if they are less effective.

To be frank, upgrading to the Enterprise plan only for this API is not feasible for us. We don’t currently need the other Enterprise-level features, so the cost-benefit analysis doesn’t work.

Furthermore, without this baseline tracking data, we cannot even begin to properly evaluate the necessity and value proposition of more expensive plans like Enterprise or BugBot.

We also see immense future potential. We want to track AI usage per-commit and correlate it with subsequent system errors, bugs, or code reverts. This would allow us to analyze the safety and true long-term utility of AI suggestions, helping us refine our AI-assisted coding processes.

This API is fundamental for large teams like ours to adopt Cursor deeply and sustainably. We strongly urge you to make it available on the Teams plan again.

1 Like
4

+1 for this

1 Like
5

+1 for this

If teams are interested in getting this usage tracking today, please consider Unbound - https://getunbound.ai/

We show detailed insights on how developers are using cursor. We cover use case discovery, to showing task level completion data, tool use and terminal command runs all through a simple proxy.

An API would be a lot simpler, of course. But an HTTP proxy is the only working solution as of now.

Raj (Founder & CEO, Unbound)

3 Likes