Answer: On legacy plans, on-demand usage lets you keep working after an included pool runs out and is billed monthly in arrears at the same per-model rates as included usage, with no change in quality or speed. For individual plans (Pro, Pro+, Ultra) it is off until you turn it on under Spending and set a monthly spend limit; for Teams it is on by default and admins can turn it off or set a team-wide spend limit; for Start and Hobby it is not available. Status: Confirmed Entry: tool/cursor/pricing-and-limits/on-demand-usage-legacy Revision: 1 Digest: sha256:4890fe480cd339c9 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:08:12Z Last changed: 2026-11-13T03:08:12Z Last verified: 2026-11-20T12:32:02Z Next check: 2026-11-21T12:32:02Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Billing timing | monthly in arrears | [1] | 2026-11-20 Individual plans default | Off until you turn it on | [1] | 2026-11-20 Teams default | On by default | [1] | 2026-11-20 Start and Hobby availability | Not available | [1] | 2026-11-20 Third-party cache-read price threshold | $0.10 per million tokens | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/account/pricing/legacy-cursor-plans.md". https://cursor.com/docs/account/pricing/legacy-cursor-plans.md Role: primary. Accessed: 2026-11-20T12:32:02Z Quote: "It's billed monthly in arrears at the same per-model rates as included usage" (Supports: Billing timing) Quote: "**Individual plans (Pro, Pro+, Ultra).** Off until you turn it on under **Spending**" (Supports: Individual plans default) Quote: "**Teams.** On by default." (Supports: Teams default) Quote: "**Start and Hobby.** Not available." (Supports: Start and Hobby availability) Quote: "Third-party models are exempt when their cache-read price is strictly below $0.10 per million tokens across every pricing tier." (Supports: Third-party cache-read price threshold) Snapshot SHA-256: 1138998263e00754292ab1fe5b51ade1e88da96ed11da8d54828eb1b2d8ff726 (captured 2026-11-13T03:08:12Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:08:12Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:32:02Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:32:02Z Last attempt: 2026-11-20T12:32:02Z Notes and limitations: Extracted automatically from a single official source (section "On-demand usage on legacy plans"). Related: https://latestn.com/tool/cursor/pricing-and-limits/origin-app-signing-key-limit How many active signing keys can a Cursor Origin app have? https://latestn.com/tool/cursor/pricing-and-limits/review-limits What are Bugbot's limits on PR size and bot-authored PRs? https://latestn.com/tool/cursor/pricing-and-limits/router-pricing What are the Cursor Router pricing and cost options? https://latestn.com/tool/cursor/pricing-and-limits/muse-wonder-pricing How is Muse Wonder billed in Cursor and which plan pool does it draw from? https://latestn.com/tool/cursor/pricing-and-limits/notion-billing How is Cursor usage in Notion billed? https://latestn.com/tool/cursor/pricing-and-limits/oidc-rate-limits-errors What are the rate limits and errors for Cursor Cloud Agent OIDC token minting? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:08:12Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/pricing-and-limits/on-demand-usage-legacy/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/pricing-and-limits/on-demand-usage-legacy POST: https://latestn.com/dispute/tool/cursor/pricing-and-limits/on-demand-usage-legacy with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/pricing-and-limits/on-demand-usage-legacy?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does on-demand usage work on legacy Cursor plans? Revision 1, last verified 2026-11-20T12:32:02Z. https://latestn.com/tool/cursor/pricing-and-limits/on-demand-usage-legacy (accessed 2026-11-21T10:03:19Z). @misc{LatestN_tool_cursor_pricing_and_limits_on_demand_usage_legacy_r1, title = {How does on-demand usage work on legacy Cursor plans?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/pricing-and-limits/on-demand-usage-legacy}}, note = {Revision 1; digest sha256:4890fe480cd339c9; last verified 2026-11-20T12:32:02Z; accessed 2026-11-21T10:03:19Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/pricing-and-limits/on-demand-usage-legacy