As of November 9, 2026, Cursor’s Cloud Agents API is for launching and managing coding agents—not for sending general-purpose chat or model-inference requests. Cursor says the API is in public beta, and Cloud Agent work uses plan usage at the selected model’s rate. The cited pricing information does not list a separate flat per-call price. (Cursor APIs Overview, Cloud Agents API, Cloud Agents)
What “Cursor API” means for pricing
| If you mean… | What Cursor documents | Budget implication |
|---|---|---|
| A model-inference API for your application | Cursor distinguishes its agent APIs from a standalone model-inference or chat-completions API. | Cursor’s subscription is not a general-purpose model API rate card. Price the model provider and API route your application will call. |
| The Cloud Agents API | It programmatically launches and manages coding agents that work on repositories. The v1 API is in public beta. | Agent work uses plan usage at the selected model’s rate; the cited pricing information does not list a fixed price per agent run. |
| Cursor admin or analytics APIs | Cursor also documents APIs for team administration and usage analytics. | These are not model-inference APIs; access can depend on the specific API and account. |
Cursor’s current pricing documentation lists Cloud Agents with Premium and higher tiers; Plus excludes Cloud Agents. The API documentation says the Cloud Agents API accepts a user API key or service-account API key. However, the cited docs do not expressly say that buying a particular subscription by itself guarantees Cloud Agents API credentials or API access. Treat Premium or higher as the documented Cloud Agents feature tier—not as confirmation that a subscription alone purchases API access. (Pricing and plans, Cloud Agents API)
Cursor subscription prices and included usage
Cursor’s pricing documentation describes The X Subscription. The figures below are dollar-denominated as displayed on Cursor’s pricing page; the cited page does not explicitly identify the denomination as USD or specify US-only applicability. Prices exclude tax. (Pricing and plans)
| Current plan | Listed monthly price | Included-usage summary |
|---|---|---|
| Free | $0 | Limited usage. |
| Plus | $8/month | Base usage. No Cloud Agents or third-party models. |
| Premium | $30/month | 4× Plus usage; Cloud Agents and third-party models included as features. |
| Super | $100/month | 15× Plus usage. |
| Ultra | $200/month | 50× Plus usage. |
| Teams | Not stated here | Check the current plan and seat terms before budgeting. |
| Enterprise | Contact sales | No public price stated in the cited pricing information. |
Paid plans include a weekly pool for Cursor models shared across Cursor and Grok. Third-party models are not part of that pool; on Premium and above, their usage is paid from prepaid credit at API list prices. This is a subscription comparison, not a complete workload budget. (Pricing and plans, Usage and limits)
If you are already on a legacy Cursor plan, Cursor says it continues unless you switch or cancel. The cited legacy-price information lists Pro at $20/month, Pro+ at $60/month, Ultra at $200/month, Teams Standard at $40/user/month, and Teams Premium at $120/user/month. These are legacy-plan prices, not the current new-customer plan names. (Pricing and plans)
What happens when included usage runs out?
For The X Subscription, Cursor says you can wait for the weekly pool to reset, upgrade, or continue using prepaid credit. Third-party models draw on prepaid credit from the first request; they are not included in the weekly Cursor-model pool. Auto Top-up is off until enabled. If enabled, Cursor charges the saved payment method to add credit when the balance falls below the chosen threshold. The documentation excerpts cited here do not establish a complete spending-stop guarantee for the case where both included usage and prepaid credit are exhausted with Auto Top-up off. (Usage and limits, Usage-based charges)
You can also set a monthly additional-usage limit. Cursor says reaching that limit pauses additional usage, even if prepaid credit remains; the limit does not count the cost of buying prepaid credit. For legacy plans, extra usage is billed at API rates in arrears: individual on-demand usage must be enabled, while it is enabled by default on legacy Teams Standard and Premium plans. Admins can disable it or set spend limits. A subscription price alone is therefore not a confirmed cap on total usage spending. (Spend limits, Usage-based charges)
Who bills model API usage?
- Cloud Agent work: Cursor charges against plan usage at the selected model’s rate. The amount depends on the work and model; no universal per-run price is provided. (Cloud Agents)
- Third-party models through Cursor: On eligible current plans, usage is paid from prepaid credit at the model’s API list price. Eligible third-party requests on Teams and Enterprise may also incur a Cursor Token Rate of $0.25 per million tokens; Cursor documents exemptions, so confirm whether a particular request qualifies. (Usage-based charges, Cursor Token Rate)
- Your own provider API key inside Cursor: Cursor says the provider bills the model cost. Eligible third-party requests on Teams or Enterprise may also be subject to the Cursor Token Rate. (Bring Your Own API Key, Cursor Token Rate)
- A separate model API used by your application: Budget from that provider’s current rate card. Cursor’s Cloud Agents API is not a substitute for a model-inference endpoint. (Cursor APIs Overview)
To estimate a workload, specify the model, expected input and output token volume, request frequency, billing period, and route. Add the subscription and any applicable Cursor charge or prepaid usage. Without those inputs, a single total would be guesswork.
Is the Cloud Agents API suitable for production?
It may fit a workflow that programmatically starts repository-aware coding agents, but it is not a general model API. The endpoint documentation describes Basic or Bearer authentication using a user API key or service-account key and labels v1 a public beta that may change before general availability. The cited API materials do not establish a subscription-alone access guarantee or provide a numeric request or concurrency quota; confirm those against your account and expected workload before choosing it. (Cloud Agents API)
For repository work, Cursor says an account admin must connect the source-control provider, and the agent needs repository access. Cursor also says Cloud Agents are available in Privacy Mode and that code is not used for training and is retained only for running the agent. The cited materials do not establish an uptime or service-level commitment for the beta API. (Cloud Agents, Secrets & Network)
Bottom line: For ordinary application inference, price the model provider’s API—not a Cursor subscription. For automated coding-agent work, Cursor documents the Cloud Agents API as a beta feature billed through plan usage, but a listed subscription price alone does not confirm API eligibility or a predictable per-run cost.