《Cursor Docs》-Legacy Cursor plans
Legacy Cursor plans are the plans Cursor sold before The X Subscription: Hobby, Start, Pro, Pro+, Ultra, and Teams with Standard and Premium seats. They keep working as they are. New customers start on The X Subscription, and this page is for anyone still on a legacy plan who wants to know how it works and how it compares.
Read More《Cursor Docs》-SSO
SAML 2.0 SSO is available at no additional cost on Teams and Enterprise plans. Use your existing identity provider (IdP) to authenticate team members without separate Cursor accounts.
Read More《Cursor Docs》-SCIM
SCIM 2.0 provisioning automatically manages your team members and directory groups through your identity provider. Available on Enterprise plans with SSO enabled, contact sales to get access.
Read More《Cursor Docs》-Team Pricing
There are two business plans: Teams and Enterprise (Custom). Teams offers two types of seats: Standard ($40/user/mo) and Premium (5x usage at $120/user/mo).
Read More《Cursor Docs》-Members, Roles, and Seat Types
Cursor Teams use roles for permissions and seat types for usage limits.
Read More《Cursor Docs》-Dashboard
The dashboard lets you access billing, set up usage based pricing, and manage your Team.
Read More《Cursor Docs》-Analytics API
The Analytics API provides comprehensive insights into your team's Cursor usage, including AI assisted coding metrics, active users, model usage, and more.
Read More《Cursor Docs》-Usage Analytics
Usage Analytics are available for Team and Enterprise customers.
Read More《Cursor Docs》-AI Code Tracking API
The AI Code Tracking API lets you track AI generated code contributions across your team's repositories, including per commit AI usage and granular accepted AI changes.
Read More《Cursor Docs》-Admin API
The Admin API lets you programmatically access your team's data, including member information, usage metrics, spending details, and model access.
Read More《Cursor Docs》-Regions
Some of our model providers have location based restrictions, which means certain models may not be available in your region. When this happens, those models won’t appear in Cursor, but you’ll still be able to use all other available models without interruption.
Read More《Cursor Docs》-Request-Based Pricing (Legacy)
This page covers Cursor's legacy request based pricing model that was used before the transition to usage based pricing.
Read More《Cursor Docs》-Organization API
The Organization API lets you perform actions that apply across teams linked to an organization, such as moving users between those teams, reporting on pooled usage across teams, managing organization groups, and reading or updating model access. It uses an Organization API key and the same HTTP patterns as the team Admin API.
Read More《Cursor Docs》-Cyber Safeguards
Cyber Safeguards settings are available on the Enterprise plan and are configured per Organization Group at Organization → Groups . These are not billing groups or SCIM directory groups.
Read More《Cursor Docs》-Billing Groups
Billing groups allow Enterprise admins to understand and manage spend across groups of users. This functionality is useful for reporting, internal chargebacks, and budgeting.
Read More