# Google API Key Integration Issue

**URL:** <https://forum.cursor.com/t/google-api-key-integration-issue/72329>\
**Category:** Bug Reports\
**Created:** [March 29, 2025, 7:56pm UTC](https://forum.cursor.com/t/google-api-key-integration-issue/72329 "2025-03-29T19:56:58Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![fitchmultz](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/fitchmultz/32/36048_2.png) [@fitchmultz](https://forum.cursor.com/u/fitchmultz)\
**Post date:** [March 29, 2025, 7:56pm UTC](https://forum.cursor.com/t/google-api-key-integration-issue/72329/1 "2025-03-29T19:56:58Z")

</div>

# Cursor Bug Report: Google API Key Integration Issue

## Issue Summary

Cannot use personal Google API key for Gemini-2.5-pro model.

## Environment

- Cursor v0.48.4
- VSCode v1.96.2
- macOS Darwin arm64 24.3.0
- Date: 2025-03-29

## Errors

1. **When using gemini-2.5-pro-exp-03-25** :

2. **When verifying Google API Key in settings** :

Cursor is hardcoding an invalid Google model name in the key verification step. This model is not able to be changed.

1. **With provided curl test command** :  
Incorrect headers (Anthropic headers included in Google API request)

## Steps to Reproduce

1. Added Google API key to Cursor settings
2. Verified key is valid (confirmed with separate curl test)
3. Attempted to use gemini-2.5-pro-exp-03-25
4. Received error messages

## User Verification

Key is valid and works with gemini-2.0-flash in independent testing.

## Additional Feedback

- Pricing model of $0.05 per request for “fast” requests is excessive
- Request option to use personal Google Cloud paid account keys
- Would pay $40-50 monthly for unlimited “pro”/“fast” requests with personal key

---

<div class="post-metadata">

**Author:** ![matejhorava](https://avatars.discourse-cdn.com/v4/letter/m/ce73a5/32.png) [@matejhorava](https://forum.cursor.com/u/matejhorava)\
**Post date:** [March 30, 2025, 1:08am UTC](https://forum.cursor.com/t/google-api-key-integration-issue/72329/2 "2025-03-30T01:08:17Z")

</div>

I just ran into the same issue, I can also confirm this worked ~two days ago when I first tried gemini-2.5-pro-exp-03-25

---

<div class="post-metadata">

**Author:** ![lifodetails](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/lifodetails/32/42354_2.png) [@lifodetails](https://forum.cursor.com/u/lifodetails)\
**Post date:** [March 30, 2025, 6:41am UTC](https://forum.cursor.com/t/google-api-key-integration-issue/72329/3 "2025-03-30T06:41:00Z")

</div>

Same here

---

<div class="post-metadata">

**Author:** ![cursoruser2342](https://avatars.discourse-cdn.com/v4/letter/c/bbe5ce/32.png) [@cursoruser2342](https://forum.cursor.com/u/cursoruser2342)\
**Post date:** [March 30, 2025, 7:21am UTC](https://forum.cursor.com/t/google-api-key-integration-issue/72329/4 "2025-03-30T07:21:56Z")

</div>

Same here. Does anyone know a solution? I see a lot of folks already using it, but no one explains how they managed to set it up correctly.

---

<div class="post-metadata">

**Author:** ![0x0131](https://avatars.discourse-cdn.com/v4/letter/0/7bcc69/32.png) [@0x0131](https://forum.cursor.com/u/0x0131)\
**Post date:** [March 30, 2025, 8:08am UTC](https://forum.cursor.com/t/google-api-key-integration-issue/72329/5 "2025-03-30T08:08:17Z")

</div>

hi.

> [@Gemini-2.5-pro-exp-03-25 settings](https://forum.cursor.com/t/gemini-2-5-pro-exp-03-25-settings/72369):
>
> I really wanted to know about the new power (full context window) of gemini-2.5-pro-exp. So I added a model called gemini-2.5-pro-exp-03-25 and ran it. This requires a Google AI Studio API key. Here’s an important thing. Please ignore any errors that occur when registering with the Google API key and continue. You can add custom mode to gemini-2.5-pro-exp-03-25 and use it without any problems. (and just ask) [https://aistudio.google.com/apikey](https://aistudio.google.com/apikey) If anyone has found that running in agent mode …

---

<div class="post-metadata">

**Author:** ![xiaofeidev](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/xiaofeidev/32/33386_2.png) [@xiaofeidev](https://forum.cursor.com/u/xiaofeidev)\
**Post date:** [March 30, 2025, 9:05am UTC](https://forum.cursor.com/t/google-api-key-integration-issue/72329/6 "2025-03-30T09:05:21Z")

</div>

Same promble, hope Cursor fix this ASAP.

---

<div class="post-metadata">

**Author:** ![Tocktock](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tocktock/32/35850_2.png) [@Tocktock](https://forum.cursor.com/u/Tocktock)\
**Post date:** [March 30, 2025, 9:17am UTC](https://forum.cursor.com/t/google-api-key-integration-issue/72329/7 "2025-03-30T09:17:37Z")

</div>

same problem, please fix ASAP

---

<div class="post-metadata">

**Author:** ![marko999](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/marko999/32/42439_2.png) [@marko999](https://forum.cursor.com/u/marko999)\
**Post date:** [March 30, 2025, 12:46pm UTC](https://forum.cursor.com/t/google-api-key-integration-issue/72329/8 "2025-03-30T12:46:30Z")

</div>

same problem

---

<div class="post-metadata">

**Author:** ![decsters01](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/decsters01/32/10082_2.png) [@decsters01](https://forum.cursor.com/u/decsters01)\
**Post date:** [March 30, 2025, 7:16pm UTC](https://forum.cursor.com/t/google-api-key-integration-issue/72329/9 "2025-03-30T19:16:16Z")

</div>

I agree with you I would pay 50$ to use my own API key. I can’t stand anymore cursor nerfing the models.. Sometimes I’m more productive using ge mini’s own chat than using the same model in the cursor chat and the nerf context is an absurd problem

---

<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 29, 2025, 7:16pm UTC](https://forum.cursor.com/t/google-api-key-integration-issue/72329/10 "2025-04-29T19:16:34Z")

</div>

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