My account was flagged after a leaked key incident. I have successfully deleted the compromised credentials, but my workspace remains stuck generating AQ. prefixes instead of standard AIza… keys across all new projects. Could an engineer please review and restore standard key generation for my account?
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!
Hi Jon,
Thank you for the clarification regarding the transition from Traffic keys (AIza) to Authentication Keys (AQ).
I completely understand the security shift, but I am running into a critical compatibility issue using Google’s own official SDK. When attempting to use the newly generated AQ. key with the official google-genai Python library for local development, the system immediately returns a 429 RESOURCE_EXHAUSTED error.
It appears that the backend initialization for the new key format has defaulted my profile’s free_tier_requests quota limit to 0, completely blocking standard SDK execution testing.
Per your recommendation, I have submitted the tracking form with the error logs and SDK environment details. Could the engineering team please review my account profile to reset the default quota limits so I can resume development with the new Auth keys?
Best regards,
Rithvik