pages/account/pricing/request-based-legacy.txt

route: /docs/account/pricing/request-based-legacy
title: Request-Based Pricing (Legacy)
description: Learn about Cursor's legacy request-based pricing model and how it differs from current usage-based pricing.

Request-Based Pricing (Legacy)
This page covers Cursor's legacy request-based pricing model that was used before the transition to usage-based pricing.
Overview
The request-based pricing model charged users based on the number of AI requests made rather than token usage. Each license had a monthly allotment of requests. If you exceeded your included usage, you could purchase additional usage on-demand.
Request
A request represents a single message sent to most models, which includes your message, any relevant context from your codebase, and the model's response. View the model table to see request counts for each model.
On-demand usage is available at the model's API rate plus 20%.
Max Mode is available at the model's API rate plus 20%. Max Mode enables larger context windows, subagents, image generation, and access to the latest frontier models on request-based plans.
Models
Legacy customers
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.
Migration support
Our team is available to help with the transition from legacy pricing to the current model. We can provide:
Detailed cost analysis comparing old vs new pricing
Migration timeline and planning
Custom solutions for enterprise customers
Contact [email protected] for migration assistance.