I am writing to request a review of my Google account. I am currently unable to generate standard Gemini API keys (AIza...) in Google AI Studio.
Issue Description: All new API keys generated in my account—even in brand-new projects—start with the AQ. prefix instead of the standard AIza format. I believe my account has been flagged or restricted.
Development Context: I am a non-technical builder currently developing an AI-native talent intelligence platform, QuickTrain. Because I do not have a coding background, I rely entirely on AI orchestration tools like Claude Code to build out the architecture. Unfortunately, Claude Code does not recognize the AQ. key format and throws a free_tier_requests limit: 0 error, completely halting my progress.
I have not intentionally exposed or misused any of my previous API keys. Could you please review my account and restore my ability to generate standard AIza API keys so I can resume my work?
You account has not been flagged for any security issue, but we are moving away from Traffic keys (Alza) and towards a more secure Authentication Key (AQ).
Are you facing any issues when using the new Authentication Keys when using gemini API ?
Thanks for responding.
Yes I a facing issues - Claude is not accepting API keys starting with AQ… as Gemini key because it is returning zero free tier. Sharing the error below,
"Why the dry-run couldn’t complete
The GEMINI_API_KEY in .env (AQ.Ab8R...) is not a Google AI Studio key. Google reports free_tier_requests limit: 0 — the project this key belongs to has no free-tier quota allocated for any Gemini model.
I am non-technical developer, so I dont know how to resolve this and I was to use the free tier first because its a prototype / agent that I am building for myself
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!