# Gemini APi Key verfication not working on models page in Cursor settings

**URL:** <https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052>\
**Category:** Bug Reports\
**Created:** [March 6, 2025, 7:17am UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052 "2025-03-06T07:17:30Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raviikumar001](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/raviikumar001/32/33456_2.png) [@Raviikumar001](https://forum.cursor.com/u/Raviikumar001)\
**Post date:** [March 6, 2025, 7:17am UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/1 "2025-03-06T07:17:30Z")

</div>

![image](https://us1.discourse-cdn.com/cursor1/original/3X/f/8/f8876d58ffa18c0e9b0cc3f9dac3108d2fc97a27.png)

{  
“error”: {  
“code”: 404,  
“message”: “models/gemini-1.0-pro is not found for API version v1beta, or is not supported for generateContent. Call ListModels to see the list of available models and their supported methods.”,  
“status”: “NOT\_FOUND”  
}  
}

I guess Cursor is using ‘models/gemini-1.0-pro’ for verifying the api key. I think they have discontinued the use of this model. Even when my api key is valid, it’s not connecting, hope they look into the issue.

---

<div class="post-metadata">

**Author:** ![bitzuist12](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bitzuist12/32/19777_2.png) [@bitzuist12](https://forum.cursor.com/u/bitzuist12)\
**Post date:** [March 8, 2025, 4:53pm UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/2 "2025-03-08T16:53:55Z")

</div>

I am having the same issue actually. when I change the test to 1.5 pro it works but obviously that’s only for curl, can’t change what model cursor automatically uses

---

<div class="post-metadata">

**Author:** ![reid](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/reid/32/36153_2.png) [@reid](https://forum.cursor.com/u/reid)\
**Post date:** [March 13, 2025, 8:33pm UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/3 "2025-03-13T20:33:32Z")

</div>

I’m having the same problem here. Are you still able to use the Gemini models via API key even though the “verification” fails?

---

<div class="post-metadata">

**Author:** ![hanniehoney](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/hanniehoney/32/36312_2.png) [@hanniehoney](https://forum.cursor.com/u/hanniehoney)\
**Post date:** [March 14, 2025, 9:34am UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/4 "2025-03-14T09:34:20Z")

</div>

![Screen Shot 2025-03-14 at 17.24.31](https://us1.discourse-cdn.com/cursor1/original/3X/4/2/42437e9f57e73225f9fdd3fc7d474c0f6ce48a71.png)  
I think the reason bc the outdated model that cursor request. I switch the model to 2.0 in crul, it success.

---

<div class="post-metadata">

**Author:** ![xMath7](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/xmath7/32/33318_2.png) [@xMath7](https://forum.cursor.com/u/xMath7)\
**Post date:** [March 16, 2025, 2:04pm UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/5 "2025-03-16T14:04:03Z")

</div>

How do you change it in crul?

---

<div class="post-metadata">

**Author:** ![heyJonBray](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/heyjonbray/32/32918_2.png) [@heyJonBray](https://forum.cursor.com/u/heyJonBray)\
**Post date:** [March 19, 2025, 5:14pm UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/6 "2025-03-19T17:14:12Z")

</div>

Just manually do the curl request that it provides you but switch it to the model that Google AI Studio recommends for verification.

However, under the hood Cursor is using a depricated model. I don’t understand why it needs to do this verification step at all. If I put in an API key that doesn’t work with a model I choose, return an error then.

---

<div class="post-metadata">

**Author:** ![AirVetra](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/airvetra/32/36158_2.png) [@AirVetra](https://forum.cursor.com/u/AirVetra)\
**Post date:** [March 25, 2025, 6:16pm UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/7 "2025-03-25T18:16:09Z")

</div>

Got the same problem - no gemini models now working through Google API:(

---

<div class="post-metadata">

**Author:** ![condor](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/condor/32/73148_2.png) [@condor](https://forum.cursor.com/u/condor)\
**Post date:** [March 25, 2025, 6:18pm UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/8 "2025-03-25T18:18:13Z")

</div>

Does following help?

> [@Support DeepSeek V3 0324](https://forum.cursor.com/t/support-deepseek-v3-0324/69236/25):
>
> If your key fails verification, try disabling all models and try again. Also, don’t forget to change the base URL.

---

<div class="post-metadata">

**Author:** ![heyJonBray](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/heyjonbray/32/32918_2.png) [@heyJonBray](https://forum.cursor.com/u/heyJonBray)\
**Post date:** [March 27, 2025, 12:06am UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/9 "2025-03-27T00:06:49Z")

</div>

This works for OpenAI as it lets you input an override URL for accessing the endpoint, but not for Gemini.

The verification process for Gemini is just confirming that a request can be sent, but Cursor doesn’t let you override the endpoint.

They should add a way to change the URL for verification, as models can be depricated with short notice leaving a hardcoded verification URL useless.

---

<div class="post-metadata">

**Author:** ![condor](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/condor/32/73148_2.png) [@condor](https://forum.cursor.com/u/condor)\
**Post date:** [March 27, 2025, 7:53am UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/10 "2025-03-27T07:53:54Z")

</div>

Several users posted here how to resolve Gemini issues

> [@Add Gemini-2.5-pro-exp to cursor](https://forum.cursor.com/t/add-gemini-2-5-pro-exp-to-cursor/69781/2):
>
> Yes, this model is impressive.

---

<div class="post-metadata">

**Author:** ![heyJonBray](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/heyjonbray/32/32918_2.png) [@heyJonBray](https://forum.cursor.com/u/heyJonBray)\
**Post date:** [March 29, 2025, 4:09pm UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/11 "2025-03-29T16:09:19Z")

</div>

That’s not resolving anything, it’s a workaround.

I need Gemini API key to work natively in Cursor, not via. openrouter as it’s through an enterprise account.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [April 28, 2025, 4:10pm UTC](https://forum.cursor.com/t/gemini-api-key-verfication-not-working-on-models-page-in-cursor-settings/60052/12 "2025-04-28T16:10:03Z")

</div>

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