Cursor request-based

cursor.com · Coding subscriptions · 2 records · JSON

Cursor Coding subscriptions

caveatemailno cardDrequest-rate

cursor.com/docs/models-and-pricing · coding subscription · coding-subs/cursor · JSON · compare

Free tier	Free: USD 0, 'Agent and Chat with limited usage'; third-party models not available unit requests; metered on request-count; the plan ladder was replaced by The X Subscription; Free exists on both the new and the legacy ladder
Price	none stated
Per-object cap	not applicable: a subscription meters usage, not objects
Retention	not applicable
Egress	not applicable: the vendor serves the inference
Identity	email a Cursor or X account
Limits	request-rate one weekly usage pool for Cursor models; legacy plans keep two monthly pools source
Binding	request-rate
Interface	cli the Cursor editor and its CLI; the usage pool covers agent, CLI and cloud agents
Tooling	Cursor editor, Cursor CLI
Composes with	the weekly pool is shared with Grok and the X apps, so Cursor usage is not a standalone budget
Reliability	no reliability event recorded
Notes	This is the largest drift found in the topic. See the history entry.
Evidence rung	documented the restructure is quoted from the vendor's own documentation today. The size of any pool is unpublished in every tier, so no capacity claim is possible. verified_at is the instant its evidence URLs were fetched on 2026-10-22, read from the fetch log, not typed.
Checked	2026-10-23 (live); stale on 2026-11-22

Evidence (3)

date	source	what it proved
2026-10-22	cursor.com/docs/models-and-pricing	The X Subscription is Free USD 0, Plus USD 8, Premium USD 30, Super USD 100, Ultra USD 200; one weekly pool shared across Grok and Cursor; third-party models billed at API list price from prepaid credit on Premium and above
2026-10-22	cursor.com/docs/account/pricing/legacy-cursor-plans	legacy Hobby free, Pro USD 20, Pro+ USD 60, Ultra USD 200, Teams Standard USD 40 per user, Teams Premium USD 120 per user; on-demand usage billed in arrears on legacy individual plans
2026-10-22	cursor.com/pricing	not published

Unknown or withheld values (4)

deademailno cardDrequest-rate

cursor.com/docs/account/pricing/request-based-legacy · coding subscription · coding-subs/cursor-legacy-request-plans · JSON · compare

Free tier	a third, older generation counted usage in requests; superseded unit requests; metered on request-count
Price	none stated
Per-object cap	not applicable: a subscription meters usage, not objects
Retention	not applicable
Egress	not applicable: the vendor serves the inference
Identity	email a Cursor account
Limits	request-rate usage counted in requests rather than tokens source
Binding	request-rate
Interface	cli the same editor, with usage counted in requests rather than tokens
Tooling	Cursor editor
Composes with	a plan generation that a reader may still be paying for and that no current table prices
Reliability	no reliability event recorded
Notes	Recorded as dead for new accounts: the vendor routes new customers to The X Subscription, and the request-based page states that an existing holder is migrated to usage-based pricing at their next renewal. Existing holders keep it working until then, which is not the same as it being purchasable.
Evidence rung	documented the existence of the third generation is documented; its ladder was not read. verified_at is the instant its evidence URLs were fetched on 2026-10-22, read from the fetch log, not typed.
Checked	2026-10-23 (live); stale on 2026-11-22

Evidence (2)

date	source	what it proved
2026-10-22	cursor.com/docs/account/pricing/legacy-cursor-plans	request-based plans are 'an older generation still', linked from the legacy-plans page as a separate document
2026-10-22	cursor.com/docs/account/pricing/request-based-legacy	'If you're on a legacy request-based plan, you can continue using it until your next renewal. At renewal, you'll be migrated to the usage-based pricing model.' The page describes the model in the past tense and states the migration, which is the evidence that no new account can buy it

Unknown or withheld values (2)