Account blocked from generating standard API keys (AIza...) after leaked key incident

Gemini API
1

My Google account ([r…@gmail.com]was flagged after a Gemini API key was accidentally exposed publicly. Since then, all my projects — including new ones — generate OAuth tokens starting with AQ. instead of standard API keys starting with AIza.

I have already deleted the compromised key. However, I cannot generate standard API keys in any project, even brand new ones. I also cannot create new Google Cloud projects.

This is blocking a production app (Narli - narli.pro) with beta testers scheduled for today.

Please restore standard API key generation for my account.

Account: …@gmail.com Project affected: Narli Project (gen-lang-client-05119838..)

Thank in advance

2

hi ive been dealing with the same problem its just im not sure if my api key was exposed. ive been getting AQ. api keys lately and they havent been working well, so please if you found a fix to this problem notify me if its possible, Thank you.

3

I now have the same issue… ( ~500$ in unauthorized Gemini API charges from a Vite-built client bundle — requesting billing review )

4

We are moving away from Traffic keys (Alza) and towards a more secure Authentication Key (AQ). AI Studio will now only generate Authentication Key (AQ) keys. More information on key usage can be found in the Using Gemini API keys documentation.

Please submit any compatibility issues with services / SDKs etc. in this form for our engineering team to review. Thanks!