Hello Google Gemini API Team,
I am requesting a manual review of Gemini API access for my account and new project.
Current project: M2PLAN-GEMINI-API
Project ID: gen-lang-client-08995011..
Account type: Personal Google Account
Tier: Free Tier
Model: gemini-3.8-flash
All generateContent requests return:
HTTP 403 PERMISSION_DENIED — "The caller does not have permission."
I have already verified:
- Gemini API is enabled.
- A completely new API key was created in a new project.
- The service account bound to the new key is active.
- Gemini 3.8 Flash is available in the project with Free Tier quota (5 RPM / 250K TPM).
- 2-Step Verification is enabled.
- Phone verification is configured.
- Recovery email is verified.
- Date of birth is valid.
An older Gemini project on the same Google account was suspended after Google detected that API credentials may have been accidentally exposed. The old credentials have been rotated and are no longer being used, and I have submitted a remediation/appeal for that project.
However, the brand-new project and brand-new key still immediately receive HTTP 403 on generateContent.
My use case is legitimate, low-volume development of an internal project-management application. I would like to continue using the Gemini API Free Tier.
Could you please check whether an automated account-level restriction is still affecting access to the Gemini API and manually review the account/project if necessary?
I have intentionally not included any API keys, tokens, service-account credentials, or other private secrets.
Thank you.