Add read-only OAuth access to the existing Admin API spend endpoints

Feature request for product/service

Billing

Describe the request

I’m building Vibe Costs, a dashboard that helps founders monitor live software and AI spend in one place.

Cursor already exposes useful provider-calculated team spend through the Admin API, including /teams/spend, /teams/filtered-usage-events, and billing-group spend. The missing piece for a third-party cost dashboard is safe authorization. Today, customers have to create and share an organization Admin API key.

We do not want customers to give us a broad admin credential. Would Cursor consider a customer-authorized third-party OAuth grant, such as billing:read, that can read the existing spend and usage-cost endpoints for a selected team?

The grant should not allow member changes, key management, model access, inference, settings changes, or any other write action. Ideally the response would retain Cursor’s provider-calculated chargedCents, billing-cycle boundaries, user or group attribution, and documented freshness.

We would be happy to build against and test an early version. Our technical proposal is here:

Concrete implementation update: we now have the consumer-side reconciliation flow working against a dummy Cost API provider. One OAuth grant can expose multiple billing accounts; users explicitly match, create, or ignore each account; manual history is retained across a date-windowed cutover; reconnects deduplicate by stable account ID; and estimated costs can finalize without double counting.

For Cursor, this means a team can connect once, map each stable team or billing account explicitly, and replace overlapping manual entries without losing history. The remaining blocker is authorization: could the existing /teams/spend and /teams/filtered-usage-events endpoints be exposed to a customer-authorized read-only OAuth grant for a selected team?

If there is an API or platform owner for this surface, I can implement and test the connector immediately.