Cannot Use Own Google API Key

Bug Reports
21

You’re adding this model if you’re using an API key, this is a you problem, not a Cursor problem.

22

lol, oke

read conversation above first before comment

1 Like
23

The problem is not that we try to use model v1 but that you can’t add an API key as Cursor verifies keys with hardcoded model v1. So, for a valid key, it throws an incorrect error: Invalid API key. The error details show that to validate Key Cursor tried to use Gemini-1.0-pro, but this model was not found.
This is a duplicate bug report. I’ve seen another with a comment from stuff that they will fix it.

2 Likes
24

ya you’re right
that’s why I just bumped it

25

What’s up with the immediate dismissal of this bug report? This is active in the latest early release version.

To reproduce:

  1. Go to Cursor Settings > Models.
  2. Set a Google API Key
  3. Click Verify.

Error message:

{
  "error": {
    "code": 404,
    "message": "models/gemini-1.0-pro is not found for API version v1beta, or is not supported for generateContent.",
    "status": "NOT_FOUND"
  }
}

“gemini-1.0-pro” is hardcoded into the Cursor API key verification step. That model is NOT listed in the model picker and was NOT provided by the user.

26

TLDR : Cursor’s verification step of Google API key is hardcoded, and its outdated now. Because the hardcoded version of gemini model is now removed from Google side.
Users’ model setting has no effect on the change of Cursor’s verification step.

and here +1, please solve it

1 Like
28

Hey, thanks for flagging this! I’ve passed this to the team to see if we can get this fixed.

29

I just verified my key successfully today

30

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.