Question 1

How does Cursor's credit-pool pricing actually work?

Accepted Answer

Cursor's Pro and Pro+ plans bill AI coding-agent usage against a dollar-denominated credit pool rather than a flat unlimited-feeling allowance: Cursor bills credits 1:1 with USD, so a $20/mo Pro plan gets a $20 credit pool and a $60/mo Pro+ plan gets a $60 credit pool, roughly 3x. Every agent request you send draws down that pool at its real per-request token cost, calculated across whichever underlying model you've selected (Claude Sonnet-class, Opus-class, GPT-5-class, etc.) — cheaper models and shorter requests burn the pool slowly, pricier models and longer context burn it fast. This replaces Cursor's older flat, unlimited-ish pricing structure with something that tracks actual usage the same way a metered API would, just wrapped inside a monthly subscription pool.

Question 2

What happens when I run out of credits?

Accepted Answer

Once your monthly consumption burns through your credit pool, one of two things happens depending on your account settings: Cursor either bills you overage at the same 1:1 rate with no markup over the underlying per-request token cost, letting you keep working at full speed for the rest of the billing cycle, or — if you haven't enabled usage-based overage billing — you drop down to Cursor's slower, rate-limited free 'Auto' mode for the remainder of the cycle instead of being billed further. Which one applies to you is a setting you control, so it's worth checking before your pool runs low mid-month.

Question 3

Is Cursor Pro+ worth it over Pro?

Accepted Answer

Pro+ costs three times as much as Pro ($60 vs $20 per month) for roughly three times the credit pool ($60 vs $20), so on paper it's a linear scale-up, not a discount. It only pays off if your actual monthly consumption would otherwise blow through the Pro pool and either rack up meaningful overage charges or push you into Cursor's slower Auto-mode limits partway through the month. Heavier daily agent users — lots of requests per day, long input context, or an expensive Opus-class model — burn through the Pro pool fast and are the clearest case for upgrading; light or occasional users who comfortably fit inside a $20 pool gain little from paying 3x for headroom they won't use.

Question 4

Why did my Cursor bill vary month to month?

Accepted Answer

Unlike a flat subscription price that's the same every month regardless of how much you use it, Cursor's credit-pool pricing means your actual bill tracks real usage: more agent requests per day, more active coding days, longer input context per request, or switching to a pricier model all raise your monthly consumption, and if that pushes past your pool size you're billed overage on top of the base plan price. This can catch people off guard because per-request cost depends heavily on token counts, which vary a lot by task — a month of mostly small edits can look nothing like a month of large refactors even if your day-to-day habits feel unchanged, so the bill moves even when your behavior doesn't feel like it changed.

Cursor-Kreditpool-Überschreitungsrechner

Kosten nach Agentenanfragen pro Tag

Ihr Nutzungspreis im Vergleich zu Pro vs. Pro+

Wie dies mit anderen Tools verbunden ist

So funktioniert dieser Rechner

Häufig gestellte Fragen

Wie funktioniert die Credit-Pool-Preisgestaltung von Cursor eigentlich?

Was passiert, wenn mir das Guthaben ausgeht?

Lohnt sich Cursor Pro+ gegenüber Pro?

Warum schwankte meine Cursor-Rechnung von Monat zu Monat?