OpenAI's Codex pricing page includes a time-limited Codex usage promotion for Pro tiers. The UI must show the end date and avoid evergreen claims.
high impact · checked 2026-05-21 · confidence high
View sourceCursor pricing should be evaluated by included usage, on-demand billing behavior, model choice, and whether you need individual or team features. This page compares plan fit, usage-pool tradeoffs, and upgrade triggers while linking every factual row to Cursor sources and last-checked dates.
Plan fit: Pro. Limit risk: low. Intensity score: 29. Mode: subscription.
Open pricing guideEvery row is rendered with provider names as plain text, source links, last-checked dates, confidence, and caveats. Prices and usage limits can change; verify official sources before purchasing.
| Tool | Plan | Monthly | Best fit | Source / freshness | Caveat |
|---|---|---|---|---|---|
| Cursor | Hobby | Free | trial, light use | Source Checked 2026-05-21 · high | Exact request pool can change; keep source link visible. |
| Cursor | Pro | $20/mo | individual paid usage | Source Checked 2026-05-21 · high | Every plan includes a set amount of model usage; on-demand usage can bill in arrears after included amount is consumed. |
| Cursor | Pro+ | $60/mo | daily agent users | Source Checked 2026-05-21 · high | 3x applies to usage pool, not guaranteed unlimited usage. |
| Cursor | Ultra | $200/mo | agent power users | Source Checked 2026-05-21 · high | 20x applies to usage pool; on-demand usage behavior must be explained. |
| Cursor | Teams | $40/user/mo | teams, admin controls | Source Checked 2026-05-21 · high | Team plan adds collaboration/admin features; do not imply more individual usage than source states. |
| Cursor | Enterprise | Custom | larger organizations, pooled usage, security/admin | Source Checked 2026-05-21 · high | Custom pricing; calculator should request a manual quote instead of estimating exact enterprise cost. |
Cursor pricing should be evaluated by included usage, on-demand billing behavior, model choice, and whether you need individual or team features. This page compares plan fit, usage-pool tradeoffs, and upgrade triggers while linking every factual row to Cursor sources and last-checked dates.
Show plan rows with price_display, billing_period, usage_or_limit_notes, region/tax caveat, source_url, last_checked, confidence, and correction link.
Compare light solo developer, heavy agent user, team lead, and API-heavy builder scenarios. State assumptions and link to calculator result.
Explain that prices, usage pools, reset windows, model access, taxes, regional availability, and enterprise terms may change. Link to changelog and contact correction route.
Pricing changes are part of the product, not a footnote. Check the dated changelog before making a plan decision.
high impact · checked 2026-05-21 · confidence high
View sourcehigh impact · checked 2026-05-21 · confidence high
View sourcemedium impact · checked 2026-05-21 · confidence high
View sourceYes. This is an independent guide and is not affiliated with or endorsed by Cursor. Brand names are used only to identify the product being discussed.
No. Calculator and table outputs are estimates based on public assumptions. Your actual bill or account limits may vary by region, plan, taxes, promotions, and provider policy changes.
Check plan price, included usage or credits, reset behavior, model access, team controls, overage or on-demand terms, source link, and last-checked date.
Paid plans can still have capacity, credit, model, or reset-window constraints. Heavy agent sessions, long context, cloud tasks, or advanced models may consume more capacity.
No. P0 should not connect to provider accounts or collect tokens, billing credentials, API keys, or private usage dashboards.
Use the contact or correction link with a source URL. Updated facts should create or update a changelog entry.