I have been using my own API key with Cursor Pro for the entire month without any issues. This afternoon, Cursor suddenly started saying that I cannot use it anymore. I am a Cursor Pro subscriber and I have always used my own API keys so that I do not consume my Pro model quota. Now they simply no longer work.
The steps to reproduce the problem are very simple: just try to use any of my models via my own API key. The key itself works normally in another program that uses the same provider and endpoint, so the issue is not with the key or the API provider. The problem seems to be how Cursor is handling personal API keys in this workflow.”
Steps to Reproduce
I have been using my own API key with Cursor Pro for the entire month without any issues. This afternoon, Cursor suddenly started saying that I cannot use it anymore. I am a Cursor Pro subscriber and I have always used my own API keys so that I do not consume my Pro model quota. Now they simply no longer work.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Hey, thanks for the report. Custom API keys in Cursor Pro aren’t officially supported - support only covers built-in providers (OpenAI, Anthropic, Google, Bedrock, Azure).
Chutes.ai, even though it’s popular, isn’t integrated with Cursor. The error “The model does not work with your current plan or api key” means Cursor can’t validate the model through your custom key.
Quick checks:
Check DevTools (Help > Toggle Developer Tools > Console) - there might be a request error
Make sure your key hasn’t expired and has the right permissions
Verify the exact model name in Chutes (it might differ from what you added)
Try deleting the model and adding it again in Settings > Models
If the problem persists after these steps, share the exact error text from the console.
No, my dear, I believe you didn’t quite understand. I’ve been using the key since version 1.6 or Saige. I know exactly what’s being discussed — the system is indeed broken.
After the system stopped having limited calls, I figured it would be worthwhile to pay for the Chutes subscription to ease the load of my monthly usage.
So yes, in this case, it was working fine until yesterday afternoon. And I know the issue is related to Cursor, because the same API key is used in other programs and they continue to work — only Cursor stopped.
As I mentioned, the proof that it works is precisely because I just updated to a new version and it started working normally again. In other words, the issue has already been resolved. Thank you.
