Cursor Pricing & Usage Limits: What You Actually Get

Cursor's pricing page is clean and simple, but the reality of using it day-to-day is more nuanced. This guide breaks down what you actually get on each plan, how the request limits work in practice, and when it makes sense to upgrade or look for alternatives.

The Three Tiers at a Glance

Feature	Free	Pro ($20/mo)	Business ($40/user/mo)
Price	$0	$20/month	$40/user/month
Fast requests	50/month	500/month	Unlimited
Slow requests	Unlimited	Unlimited	Unlimited
Premium models	Limited	Yes	Yes
Team features	No	No	Yes
Priority support	No	No	Yes
SSO / SAML	No	No	Yes

info

Prices are as of mid-2025 and may vary by region. Cursor occasionally adjusts pricing, so check the official site for the latest numbers.

The Free tier is genuinely useful for evaluation, but most developers who use Cursor daily hit the 50-request cap within a few days. The real decision is usually between Pro and Business, or whether to bypass Cursor's limits entirely with your own API keys.

What Are Fast vs Slow Requests

This is the single most confusing part of Cursor's pricing. Not all AI interactions are created equal.

Fast Requests

Fast requests go to Cursor's priority queue and use premium models like Claude Sonnet 4, Claude Opus, GPT-4o, and o3-mini. These are the interactions that feel instant and use the best models.

What counts as a fast request:

• Every message sent in the AI Chat panel (Cmd+L)
• Every inline edit using Cmd+K
• Every Composer session that generates or modifies code
• Every AI-powered action that hits a premium model

tip

Tab autocomplete via Cursor Tab does not count against your fast request limit. Cursor Tab uses Cursor's own Cheetah model and is included free on all plans.

Slow Requests

Once you exhaust your fast requests, you drop to slow requests. These still work, but with two catches:

1. Queue delays: Your request goes into a lower-priority queue. During peak hours, this can mean waiting 10-30 seconds or longer for a response.
2. Model restrictions: Slow requests typically route through cheaper, faster models like GPT-4o mini rather than Claude Sonnet 4.

For most developers, hitting the slow queue is a workflow killer. You send a message, wait, context-switch to something else, and by the time the response arrives you've lost your train of thought.

What Actually Counts as One Request

A common misconception is that one request equals one word or one line of code. It doesn't.

One request = one interaction with the AI.

• Typing a message in chat and pressing Enter: 1 request
• Using Cmd+K to edit a function: 1 request
• Running a Composer session that modifies 5 files: 1 request
• Asking the AI to explain a code block: 1 request

The size of the response doesn't matter. A one-line answer and a 200-line refactor both cost one request.

Pro Plan: The Sweet Spot for Individual Developers

At $20/month, the Pro plan is where most Cursor users land. Here's what 500 fast requests per month actually looks like in practice.

Daily Budget Breakdown

500 requests / 22 working days = ~22 fast requests per day

For a developer using Cursor heavily:

• Morning: 3-4 chat messages reviewing yesterday's work
• Mid-day: 5-6 Cmd+K edits, 2-3 Composer sessions
• Afternoon: 4-5 chat messages debugging, 2-3 inline edits

That's roughly 18-22 requests per day. It works, but there's no buffer. A heavy refactoring day can burn 50+ requests in a single afternoon.

When You Hit the Limit

Forum posts about running out of requests are common. Here's what happens:

1. You get a notification in Cursor that you've used your fast requests
2. Subsequent requests go to the slow queue
3. You can still work, but the experience degrades significantly

warning

There is no way to buy additional fast requests mid-month on the Pro plan. Your only options are to wait for the next billing cycle, upgrade to Business, or switch to using your own API keys.

Business Plan: Unlimited Fast Requests

The Business plan at $40 per user per month doubles the price but removes the request anxiety entirely.

What You Get Beyond Unlimited Requests

Feature	What It Does
Team billing	One invoice for the whole team, seat management
Admin dashboard	Usage analytics, seat allocation, spending controls
SSO / SAML	Connect to your existing identity provider
Audit logs	Track who used what and when
Shared codebase indexing	Better AI context for team projects
Priority support	Faster response from Cursor's support team

For teams of 3+ developers, the Business plan often pays for itself in reduced friction. No one has to ration their requests or worry about hitting a cap during a critical sprint.

The Math for Teams

Team of 5 on Pro: 5 x $20 = $100/month, 2,500 total fast requests
Team of 5 on Business: 5 x $40 = $200/month, unlimited fast requests

If your team consistently hits limits on Pro, Business is the obvious next step. The per-seat cost is higher, but the productivity gain from unlimited usage usually justifies it.

The Claude Max Workaround

A significant number of heavy Cursor users bypass Cursor's limits entirely by subscribing to Claude Max directly from Anthropic and bringing their own API key into Cursor.

Claude Max Pricing

Plan	Price	Claude Usage
Claude Pro	$20/mo	5x more than free
Claude Max (Tier 1)	$100/mo	20x more than free
Claude Max (Tier 2)	$200/mo	Essentially unlimited

How to Use Your Own API Key in Cursor

// Cursor Settings > Models > Anthropic API Key
{
  "anthropic.apiKey": "sk-ant-api03-..."
}

Once configured, you can select Claude models in Cursor, and usage counts against your Anthropic quota instead of Cursor's limits.

info

Using your own API key means you pay Anthropic directly for usage. Costs vary by model and usage volume, but heavy users often find it cheaper than Cursor Business at scale. The tradeoff is you lose Cursor's team features and admin controls.

When This Makes Sense

• You primarily use Claude and rarely touch GPT or Gemini models
• You're a solo developer or small team without complex admin needs
• You want more control over which models you use and how much you spend
• You consistently burn through Cursor's 500-request Pro limit

How to Check Your Usage

Cursor doesn't make usage tracking obvious, but there are a few ways to monitor where you stand.

In the Cursor Interface

1. Open the Chat panel (Cmd+L / Ctrl+L)
2. Look at the bottom of the panel for a usage indicator
3. Some versions show remaining requests directly in the model dropdown

Account Dashboard

1. Go to Cursor Settings (Cmd+, / Ctrl+,)
2. Navigate to Account or Billing
3. View current usage and billing cycle dates

tip

Set a calendar reminder for 3-4 days before your billing cycle resets. If you're close to the limit, you can switch to slow requests or your own API key for non-critical tasks to preserve fast requests for important work.

Rough Self-Tracking

If the interface isn't showing clear numbers, you can estimate:

Start of month: 500 requests
Day 10: Count how many days you used Cursor heavily
Estimate: ~20 requests per heavy day, ~5 per light day

It's imprecise, but it helps you gauge whether you're on track to run out.

Free Tier: Evaluation Only

The Free tier gives you 50 fast requests per month. This is enough to:

• Test Cursor Tab autocomplete
• Try a few chat interactions
• Evaluate whether the AI suggestions are useful for your workflow

It is not enough for daily development work. Most developers on the Free tier either upgrade within a week or stop using Cursor.

Free Tier Limitations Beyond Requests

• No access to Claude Opus or o3-mini
• No Composer multi-file editing
• No background agents
• No custom model configuration
• Limited context window sizes

If you're on the fence, use the Free tier to test specific workflows. Don't expect to complete real projects on it.

When to Upgrade: Decision Framework

Situation	Recommendation
Evaluating Cursor	Stay on Free
Using Cursor 1-2 hours/day	Pro plan
Using Cursor 4+ hours/day	Pro plan + monitor usage
Hitting 500-request limit regularly	Business plan or Claude Max
Team of 3+ developers	Business plan
Need SSO / audit logs	Business plan
Primarily use Claude	Consider Claude Max + own API key
Mix of models and team features	Business plan

tip

The Pro plan is the right starting point for almost every individual developer. Upgrade to Business when the request limit becomes a workflow blocker, not before. The Claude Max route is best for power users who know they want Claude exclusively.

Summary

Cursor's pricing is straightforward on the surface but has real implications for daily workflow. The Free tier is for evaluation. The Pro plan at $20/month fits most individual developers but requires some request management. The Business plan at $40/user/month removes limits entirely and adds team controls.

The key metric to watch is how many fast requests you use in a typical week. If you're consistently above 100 per week, you're on track to hit the Pro limit. At that point, either upgrade to Business or set up your own API keys to avoid the slow-queue penalty.

Understand your usage, pick the plan that matches it, and don't let request limits dictate how you work.