Gemini Own Key Error

[furki]

Hello,

I’m using my own Gemini token. I’m only getting the following error in the Cursor app. Even though I’m using my own personal token.

Request ID: 4632b869-d94a-4b23-9797-a2950334a735
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We encountered an issue when using your API key: Streaming error\n\nAPI Error:\n\n\n{\"error\":{\"type\":\"provider\",\"reason\":\"provider_error\",\"message\":\"Provider returned 429\",\"retryable\":true,\"provider\":{\"status\":429,\"body\":\"[{\\n \\\"error\\\": {\\n \\\"code\\\": 429,\\n \\\"message\\\": \\\"Resource has been exhausted (e.g. check quota).\\\",\\n \\\"status\\\": \\\"RESOURCE_EXHAUSTED\\\"\\n }\\n}\\n]\"}}}\n”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}

[deanrie]

Hey, thanks for the report.

This is a known issue, and it’s a duplicate of this thread: Gemini API key doesn't work with the latest Cursor version

The team is already working on a fix. The issue started in version 2.2.36 and is related to how Cursor routes requests to the Gemini API. It’s using a regional endpoint instead of the global one.

Please follow the main thread for updates. There’s no workaround yet, but for now you can try using a different model.