This is a very confusing business logic. When you upgrade from a monthly subscription to an annual one, once you’ve exceeded 500 requests, you’re no longer allowed to use the model normally. The support team keeps replying in different ways, suggesting that I use the 【0.04-per-call】 option instead.
I simply cannot understand this business model. Under the 【20】 plan, even if you exceed the 500 fast requests, you can still get a response after waiting 1–3 minutes. But under the 【192】 plan, it almost always gets stuck at “Generating…” , and after about 20 minutes, the session automatically closes.
I tried to analyze Cursor’s business logic: with the 【20】 plan, if users find the service unsatisfactory, they can simply choose not to renew the next month. There’s no obvious refund option, but at least the financial loss is small. However, with the 【192】 plan, even if users find it unusable, they can’t cancel until a year later.
So this business logic cleverly prioritizes acquiring 【new users】 , which makes user growth numbers look better. Other than that, I honestly can’t think of any reason why they would design such a 【u.s.e.r-h.o.s.t.i.l.e] system.
I used to use Max to change it. I spent a lot of money, and it was going to be successful. It was just 500 , I found a small problem. I went on (the default is to turn off usage billing) . As a result, I used some model automatically, and it was completely changed, so 500 is the watershed.
I’ve seen other posts where some people claim that using more than 500 requests is considered “abusing the API,” while others say they’ve never even reached 500 requests in months. Interestingly, these more “positive” posts seem to be ranked higher in visibility.
Here’s what I want to say:
Since Cursor offers this service to users, using 100, 200, or even 500 requests should not be considered “abuse.” From a user’s perspective, Cursor is simply a service provider. As long as the user is not breaking any laws, how they choose to use the service they paid for shouldn’t be judged or restricted as “abuse.”
The slow request behavior described on the official website worked just fine under the $20/month plan — it was slow (1–3 minutes), but it always responded. However, under the $192/year plan, I’ve experienced an almost 100% failure rate — the model doesn’t respond at all.
If there is such a hidden business logic, it should be clearly disclosed on the website. The lack of transparency is frustrating and misleading for paying users.
What they really care about is likely new user registration numbers — possibly to make their user growth metrics look better for financial reports or investors.
Since there’s no refund option anywhere on the official site, it feels like their mindset is:
“We’ve already got this person’s money — now let’s focus on getting more new users to sign up and pay. Once they pay, we shift resources to the next batch of newcomers.”
This cycle keeps repeating.
So honestly, my recommendation is:
Just register a new account, use the free 50 requests, and when that’s done — register another account.
That might actually be more reliable than paying for a plan that doesn’t deliver on what’s promised.
Indeed, you don’t know why it’s stuck on “Generating…”, and I don’t know either — even though many people are asking about this issue.
This situation is really interesting. Their way of handling it is not to solve the actual problem, but to solve the person who raised the problem. Interesting.
Yesterday I roughly sorted it out. The “Generating…” issue generally falls into the following categories:
Suddenly becomes unusable.
Becomes unusable after using up 500 requests post payment.
Becomes unusable after upgrading from monthly to annual plan and hitting 500 requests.
Hi, to be clear, you should still have access to the slow pool regardless of if you pay monthly or yearly - it sounds like you may have a bug which is stopping you from using this!
If you get stuck on Generating... again, can you open the console by running the Developer: Toggle Developer Tools command, checking the console tab and seeing if there are any errors there?
Also, starting a new chat and disabling buggy MCP server may get your requests working again!
Thanks again for getting back to me. Sadly, the “Developer: Toggle Developer Tools” suggestion didn’t resolve anything, and it’s a bit strange that the post was marked as “Solution” so quickly.
As I already detailed earlier, I’ve tested many methods, including the MCP-related suggestions. It’s starting to feel like quick recommendations are being made just to close tickets, which is understandable, but not helpful.
I fully uninstalled and reinstalled Cursor after seeing your reply, just in case.
The issue I’m facing looks like this:
1). The $0.04 per request option works flawlessly
2). After upgrading to the $192 annual plan, the model suddenly became completely unusable
3). Emails sent to [email protected] have only resulted in repeated suggestions to use the $0.04 option, in various forms
If I were able to resolve this issue on my own, I would never have come to a forum that hides users’ posts. The fact that I even had to find alternative ways just to get my issue seen makes me feel like a ridiculous fool who has wasted several days on this.
Please take a closer look — it seems to be affecting more users than just me.
