Account Restricted to Buggy AQ. Prefix Keys Only – Need Standard AIza Key for Local Agent

Gemini API
1

Hi Google AI Team,

I am developing a local, stateless data synthesis agent for professional use. My Google Cloud project is currently generating only AQ. prefix API keys (e.g., AQ.Ab8...).

These keys are failing with authentication errors (Multiple authentication credentials received) and are incompatible with standard generativelanguage.googleapis.com endpoints in my local HTML/JS workflow. Previous documentation and community threads indicate that AIza prefix keys are required for stable free-tier usage.

Request: Could you please review my account/project restrictions? I need to generate a standard AIza... key to proceed. Creating new projects or regenerating keys has not resolved this; the system only provides AQ. keys.

Project ID: [concise-ion-484310-b..]

Thank you for your assistance.

2

There are known issues with the AQ prefixed keys. Apparently it’s “being worked on”. There’s no way to generate the old style key, so you would need to dig one up if you have one (along with the risks that come with that).

That’s all I know. I’m also affected by this. I prepaid money for the API and I’m largely unable to use it for what I need it for currently.

Apparently free tier keys work though? I don’t know man.

3

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!