Account only generating AQ. tokens, cannot create standard AIza API keys

Gemini API
1

Hello Google AI Developer Support,

My account is unable to generate standard Gemini API keys (AIza… prefix).
Every key I create in Google AI Studio — including keys in brand-new projects —
is issued as an “AQ.” prefixed token instead.

When I use these AQ. keys to call the Gemini API (e.g. the
generativelanguage.googleapis.com/v1beta/models endpoint with ?key=…),
the request fails with:

“Request had invalid authentication credentials. Expected OAuth 2 access
token, login cookie or other valid authentication credential.”

I believe my account may have been flagged or restricted from generating
standard API keys. I have billing enabled (paid tier) on the project.

Could you please:

  1. Confirm whether my account has been restricted from generating standard
    AIza API keys, and
  2. Help restore the ability to generate standard Gemini API keys so I can
    use the API for my project?

Account email: ..
Project number: 4980462250..

Thank you very much for your help.

2

Hi,

I too am having the same problem and was wondering what are the reasons people are becoming restricted to access the tokens of AIza… instead of the AQ?

Could you please:

  1. Confirm whether my account has been restricted from generating standard
    AIza API keys, and

  2. Help restore the ability to generate standard Gemini API keys so I can
    use the API for my project?

    Also what would be the ETA to get this fixed since I’ve got a Project needing done and this is holding me back to approve the API access.

3

They’ve announced in other threads that they have stopped issuing these and are going full AQ.

See this other thread

The person responding is sort of just responding without explaining.

The problem is, they did this before the AQ keys started working. It’s a fundamental failure of the Gemini API team. I don’t know who on Earth is approving this and how these things get pushed to production when clearly they aren’t ready. My trust with Google is almost totally eroded.

My only workaround right now is using one of the older keys I happen to have, but apprently those might stop working June 19; and we already know these keys are fundamentally not secure and you risk running up a large bill if you keep using the unrestricted ones.
It’s really a mess here in AI Studio.

4

Someone replied to a topic you are Watching.

| Henry-Khanh
June 4 |

  • | - |

Hello Google AI Developer Support,

My account is unable to generate standard Gemini API keys (AIza… prefix).
Every key I create in Google AI Studio — including keys in brand-new projects —
is issued as an “AQ.” prefixed token instead.

When I use these AQ. keys to call the Gemini API (e.g. the
generativelanguage.googleapis.com/v1beta/models endpoint with ?key=…),
the request fails with:

“Request had invalid authentication credentials. Expected OAuth 2 access
token, login cookie or other valid authentication credential.”

I believe my account may have been flagged or restricted from generating
standard API keys. I have billing enabled (paid tier) on the project.

Could you please:

  1. Confirm whether my account has been restricted from generating standard
    AIza API keys, and
  2. Help restore the ability to generate standard Gemini API keys so I can
    use the API for my project?

Account email: ..
Project number: 4980462250..

Thank you very much for your help.

5

Subject: Account restricted to AQ. keys — requesting AIza key restoration

My Google AI Studio account can only generate AQ. prefix API keys. These return 404 errors when used server-side with the Gemini API. I have never been able to generate a standard AIza key. I believe my account may have been flagged or restricted from generating
standard API keys. I have billing enabled (paid tier) on the project.

Could you please restore my account’s ability to generate standard AIza API keys?

Account email: [k…@googlemail.com]