Hello Google AI Studio / Gemini API team,
We are using a paid Tier 2 Google AI Studio project in Japan. Billing is active, the project is accessible from the correct Google Workspace account, and the published Lyria 3 Pro quota is not exhausted.
Issue 1: Lyria 3 Pro returns HTTP 403 for every tested key
- Model:
lyria-3-pro-preview - Surface: Google AI Studio Music Composer
- Visible message:
Generation failed: Http response at 400 or 500 level, error: , http status code: 403 - We tested three different Gemini API-restricted keys from the same existing project, one request per key only:
- An existing key bound to a service account
- An existing standard key not bound to a service account
- A newly created key bound to a new service account
- All three keys returned the identical HTTP 403 response.
- We did not retry any key.
Issue 2: AI Studio blocks new API-key creation
- We completed interactive Google account password verification.
- The correct account can access the correct Cloud project, and no access-denied banner is visible.
- Creating a dedicated API key in Google AI Studio for the same project returns:
Failed to generate API key, The request is suspicious. Please try again. - The key is not created.
Additional checks
- Billing: active, Tier 2, postpaid
- Rate limits: well below the published limits
- Existing project and existing API keys are visible in AI Studio
- Every tested key is restricted to the Gemini API
- No raw key, key suffix, account email or project ID is included in this report
Could you please check whether this AI Studio account or project is being incorrectly blocked by an anti-abuse/security control, or whether Lyria 3 Pro Preview requires an additional entitlement? We can provide the project ID and exact timestamps privately to Google staff if required.