Cursor lists Enterprise as custom-priced, with pooled usage; it does not publish a standard Enterprise price in the cited pricing table. Cursor recommends Enterprise for organizations that need pooled usage, invoicing, priority support, SCIM, or advanced security controls, and directs prospective customers to contact sales. The public pricing information cited here does not state a standard per-seat rate, minimum seat count, contract length, or minimum spend, so get those terms in a written quote. (Models & Pricing; Team Pricing)
The published Enterprise usage-pricing entry is “API list price plus the Cursor Token Rate on eligible models.” The available documentation excerpt does not explain how that pricing interacts with the included team pool—specifically, whether it describes consumption within the pool, charges after the pool is exhausted, or both. Confirm the pool allowance, metering, and any additional charges with Cursor before budgeting. (Models & Pricing)
Keep three possible budget lines distinct: the custom Enterprise subscription, model usage made through Cursor, and model API traffic from your own production application. Cursor describes its APIs as agent workflows, not as a standalone model-inference or chat-completions API. Do not assume an Enterprise subscription includes inference for your application. (Cursor APIs Overview)
What Cursor Enterprise pricing includes publicly
Cursor’s published plan table describes Enterprise as Custom, with Pooled usage. Its Enterprise usage-pricing entry says “API list price plus the Cursor Token Rate on eligible models.” These are separate pieces of the published pricing description: the subscription price is custom, while eligible model usage has a stated pricing basis. The excerpt does not establish how that basis is applied against the pool or when it results in an additional invoice charge. (Models & Pricing)
| Budget item | What the cited public documentation says | What to confirm in your quote |
|---|---|---|
| Subscription | Enterprise is listed as Custom. | Total fee, currency, billing unit and cadence, minimum spend, and any other commercial conditions. |
| Usage pool | Enterprise usage is described as Pooled across the team. | Included amount, how usage is measured, and what happens when the pool is exhausted. |
| Eligible model usage | The Enterprise table lists API list price plus the Cursor Token Rate for eligible models. | Which models are eligible, how this pricing is applied to pool usage, and when any additional charge is billed. |
| Seats and commitment | The cited public Enterprise entry does not specify a seat minimum or contract length. | Minimum paid seats, contract term, renewal, and seat changes. |
| Invoicing and support | Cursor names invoicing and priority support among reasons to consider Enterprise. | Invoice schedule, payment terms, and the support commitments in your contract. |
Cursor also directs prospective Enterprise customers to contact sales. Ask for a written quote and usage schedule; the cited public information is not enough to calculate a complete Enterprise budget. (Team Pricing)
Model charges: Cursor usage, BYOK, and production APIs
Eligible model usage through Cursor
The Enterprise pricing table gives an eligible-model usage basis of API list price plus the Cursor Token Rate. The excerpt does not clarify whether that entry is specific to Cursor-managed requests, BYOK requests, or both, nor how those charges interact with the included pool. Ask Cursor to specify the applicable models, rates, metering, pool treatment, and any charges after the pool is used. (Models & Pricing)
For BYOK, Cursor’s documentation says the model provider bills the model cost. It also says eligible third-party model requests made with your own key carry a Cursor Token Rate of $0.25 per million tokens for input, output, and cached tokens. The available excerpt does not settle how those BYOK charges are treated within the Enterprise pool, so confirm that point for your quote. (Bring your own API key)
Illustration, not an Enterprise bill estimate: If 40 million tokens of BYOK requests were eligible for that stated rate, the Cursor Token Rate component would be 40 million ÷ 1 million × $0.25 = $10. This calculation excludes the model provider’s separate model charge and does not establish how the $10 relates to an Enterprise pool or invoice.
Your own production application
Cursor’s API overview describes APIs for Cursor agent workflows and distinguishes them from a standalone model-inference or chat-completions API. That does not establish that an Enterprise editor subscription provides an endpoint for serving model responses from your application. If your application calls a model provider directly, get the applicable production API rates and terms from that provider, and keep them as a separate budget line unless your contract documents another arrangement. (Cursor APIs Overview)
Cursor’s Enterprise service-account documentation says service accounts are included at no extra cost and that their activity consumes usage from the team pool. Before relying on them in a deployed workflow, confirm which authentication and agent-invocation capabilities support your use case, what usage they consume, and what uses are permitted. (Service Accounts)
Questions to resolve before budgeting
Ask Cursor sales to address these points in the quote or accompanying usage terms:
- What is the total subscription price, currency, billing unit, and cadence? Are there minimum seats, spend, or contract term?
- What amount is included in the pooled usage, and how is consumption measured?
- For eligible models, how is API list price plus the Cursor Token Rate applied to usage in the pool? What happens when the pool is exhausted, and when are additional charges billed?
- Which models are eligible, and does the usage-pricing entry apply to Cursor-managed requests, BYOK requests, or both?
- For BYOK requests, which party bills each charge, and how does the Token Rate interact with the Enterprise pool?
- Which models, API-key configurations, and workflows are available to your organization? What administrator controls or restrictions apply?
- For service accounts or Cloud Agent workflows, what capabilities and permitted uses apply, and how do they consume the pool?
- Is your application’s production model API billed directly by its provider, or does a separate documented arrangement apply?
- What are the invoice, renewal, cancellation, support, and tax terms?
Bottom line: Treat Cursor Enterprise as a custom quote, not a published per-seat price. The published usage entry gives an eligible-model pricing basis—API list price plus the Cursor Token Rate—but the cited excerpt does not explain how those charges interact with pooled usage or when additional charges apply. Keep the subscription, model use through Cursor, and your production application’s API traffic distinct until Cursor and the relevant provider confirm the applicable terms.
Sources
Models & Pricing | Cursor Docs
Bring your own API key | Cursor Docs