Providers / Cursor

AI coding

Cursor API keys and credentials

What every Cursor credential a founder holds does, whether it expires, and what tends to break. Each fact links to Cursor's own docs.

Last checked 2026-11-08 · cursor.com

At a glance

Each credential

Team Admin API key (admin:* scope)

• Not documented
• Can be scoped

Created by a team admin in the Cursor dashboard (API Keys section); copy it immediately. Authenticates with HTTP Basic, with the API key as the username. The docs list 'admin:*' as required for the Admin API and AI Code Tracking API key; other endpoints accept read:* or models:read scopes. Admin API usage and spend endpoints are reads. Keys belong to the organization and keep working when the creator's account changes status. No expiry or rotation rules were stated.

Cursor docs

Analytics API key (Enterprise teams)

• Not documented

Generated from the Cursor dashboard API Keys section. The docs do not state expiry or scope for this key type.

Cursor docs

Cloud Agents API key (user or service account)

• Not documented

Beta. Can be a user key from the dashboard or a service account key from team settings. Available on plans that include Cloud Agents. Expiry and scopes are not stated in the docs.

Cursor docs

Cursor account login

• Not documented

Dashboard login. Subscriptions are monthly with cancellation required at least 24 hours before renewal.

Cursor docs

What usually goes wrong

• Admin key used in a service that stops working after the org changes plan, which removes Admin API access
• Admin key scope set too narrowly, so usage or spend reads return permission errors
• Admin key copied only once and lost when the dashboard page is closed
• Daily usage polled more often than hourly and throttled (about 20 requests per minute per team reported by a third party)
• Subscription cancelled less than 24 hours before renewal and charged anyway

Renewals and billing

• Cursor plan (Free, Plus, Premium, Super, Ultra, Teams, or Enterprise), billed monthly. Pricing page shows monthly prices: Plus $8, Premium $30, Super $100, Ultra $200, Teams $30+ per user, Enterprise custom. Cloud Agents included on Premium and above. Annual billing was not confirmed. Cancel at least 24 hours before renewal to avoid charges.

Team Admin API (HTTP Basic, key as username). POST /teams/spend (spend, per user; includes names and emails) and POST /teams/daily-usage-data (includes email; data aggregated hourly, poll at most once per hour). Admin API listed as Enterprise teams; a forum reply said Business (unconfirmed).

What Cursor's docs don't say

We couldn't confirm these from official docs, so don't rely on them either way:

• Whether /teams/spend or /teams/daily-usage-data accept a read:* scope (docs table says read:* for directory groups only; spend scope not stated)
• Plan required for Team Admin API spend endpoints (docs say Enterprise teams; forum says Business)
• Hourly granularity is taken from the docs statement that Admin API data is aggregated hourly
• Expiry and rotation rules for all Cursor API key types
• Scope of Analytics API key and Cloud Agents API key
• Annual pricing and billing options (pricing page fetch showed monthly only)

Rotating or replacing a Cursor key

The steps are the same for most providers: make the new key, deploy it everywhere the old one is used, check it works, then revoke the old one. Our guides walk through it:

Sources

• cursor.com/docs/account/teams/admin-api
• cursor.com/docs/api
• cursor.com/pricing

Keep track of every Cursor key

StackHangar stores your Cursor keys in an encrypted vault, grouped by the product they belong to, warns you before they expire, and walks you through rotating them. We can't read your secrets.