Account can only generate AQ. keys — AIza key restoration request

Gemini API
1

My account can no longer generate standard AIza-format API keys.
Every key I create in Google AI Studio — including keys in newly
created projects with billing enabled and a bound service account —
is issued with an “AQ.” prefix.

When I use these AQ. keys to call the Gemini API
(generativelanguage.googleapis.com, generateContent), every request
fails with 403 Forbidden.

I have already tried:

  • Creating keys in a new project
  • Enabling billing (free trial active)
  • Binding the key to a service account with a role
  • Restricting the key to Gemini API only

The GET /models endpoint works, but generateContent returns 403.

Could you please restore AIza-key generation for my account, or
advise how to make AQ. keys work with the Generative Language API?

Project ID: clinickeeper-5014..

2

You can still generate an API key using Google Cloud with restricted permissions. However, beware that the Gemini API will reject restricted keys in the next few months, and all keys must be service accounts that are bound to a service identity and limited to Gemini API permissions only. This is to protect you from getting bill shock if your key gets stolen.

3

Hello @derya_ozbostan ,

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!