What is this? A joke?
Why by using my own API Key am I hitting Cursor’s limits?
Is this a bug? Because if not, this is mercenary.
It’s like if a company tells a worker:
Hey, we can give you a computer or bring you your own
(proceeds to bring his puter 
)
(Company) Ohh, you can’t use your computer if the rest are busy!
What kind of criminality is this?
Pure bandalism
In the Cursor Docs it explicitly says:
Cursor allows you to enter your own API keys for several LLM providers to send as many AI messages as you want at your own cost. When using a client API key, we will use it when calling LLM providers.
This is more false than BBC news.
Hey, sorry about that. It should be working now, I checked it on my end.
Hello,
I have the same issue:
We’re experiencing high demand for Claude 3.5 Sonnet right now. Please upgrade to Pro, switch to the ‘auto-select’ model, another model, or try again in a few moments.
What is the background of this issue? How Can I solve it?
I already have a configured API key from Claude
Hey, please check, that bug is happening again now
yes
Hey, looks like we were hitting our capacity limits, but we’re scaling things up to support more traffic, so should be resolving soon!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
