Subject: Request for AIza API Key Restoration — Account Restricted to AQ. Tokens

Gemini API
,
1

Hello Google AI Developer Support Team,

I am writing to respectfully request a review of my account and the restoration of my ability to generate standard AIza format API keys in Google AI Studio.

Account Details:

  • Account Email: s.....@gmail.com
  • Linked Project ID 1: gen-lang-client-09164406..
  • Current Restricted Token Sample: AQ.Ab8RN6LHiLEhKc5CcKppxhoQGN_zEKw3pBikCefxH7sD_STG..

The Issue:
Every time I generate a new API key in Google AI Studio, my account exclusively issues keys starting with the ‘AQ.’ prefix. When I attempt to use these keys to authenticate my local development environment (connecting via an IDE and specialized local tools), the application fails immediately, throwing a 401 UNAUTHENTICATED error with the specific status message: “ACCESS_TOKEN_TYPE_UNSUPPORTED”. Because of this, my local development pipeline is completely blocked.

Suspected Cause:
I believe my account inadvertently triggered an automated anti-abuse or scraping flag during intensive local testing. I have been building a complex multi-agent system utilizing Python and LangGraph. While testing concurrent script executions to automate system workflows and stage development payloads, the rapid, successive background loops originating from my local IP machine likely tripped the platform’s automated concurrent request security limits.

Resolution & Assurance:
I want to explicitly clarify that these request bursts were entirely confined to local execution, testing, and debugging of my multi-agent architecture. This traffic was not a malicious scraping operation or an attempt to exploit platform quotas.

To ensure this does not happen again, I am modifying my local orchestration code to implement strict rate-limiting, exponential backoff, and pacing delays between sequential model requests. This will guarantee that all ongoing development calls remain safely within normal platform behavior thresholds.

Could a member of the Trust & Safety or Support team please review my project logs and lift this automated restriction so that my account can generate functional AIza keys again?

Thank you for your guidance, time, and support.

Best regards,
Sarvath Taj.

2

Hello @Sarvath_Taj,

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!