Manual review request: Gemini API 403 "Your project has been denied access"

Gemini API
1

Hello Gemini API Team,

I am requesting a manual review of a Gemini API access restriction affecting my Google Cloud project.

Project name: Default Gemini Project
Project ID: gen-lang-client-025438… (full ID available privately)
Billing tier: Free Tier
API: generativelanguage.googleapis.com
Tested model: gemini-3.8-flash

Every generateContent request returns:

HTTP 403 PERMISSION_DENIED
“Your project has been denied access. Please contact support.”

A read-only audit confirmed the following:

  • The Gemini API is enabled.
  • The API key is active and belongs to the same project.
  • The key is restricted to the Gemini API.
  • The associated service account is enabled.
  • The account has the Owner role.
  • No IAM Deny policy is attached to the project.
  • Gemini API quotas are available and have not been exhausted.
  • Google Cloud and AI Studio show no suspension or abuse warning.
  • GET /models succeeds with HTTP 200 and lists the tested model.
  • generateContent fails with the same HTTP 403 when tested directly, outside the Hermes integration.
  • The issue has also persisted across additional keys and projects tested with this account.

This rules out an application routing problem, SDK fallback, disabled API, invalid key, project mismatch, IAM denial and quota exhaustion. No API key or credential is included in this post.

The available evidence suggests a Gemini-side account or project eligibility, automated security, Trust and Safety, or access flag that is not visible in Google Cloud Console.

Could a member of the Gemini API team please review the access state and advise whether the restriction can be removed? I can provide the full Project ID, project number, exact timestamps, screenshots and redacted diagnostic output through a private channel.

Thank you.

2

Hello @Sergey_Stupin ,

Getting a 403 API error response and / or seeing “Unavailable” next to your project in AI audio indicates a flag has been placed on your account. To proceed:

  1. If you’re on the free tier with no billing attached, please try the below steps:

  2. Check Model Availability & Rate Limits:

    • Ensure that the model you are requesting is available on your current plan. For example, not all models are available on the free tier. You can verify model availability, quotas, and limits on the AI Studio Rate Limit dashboard.

  3. Ensure you have completed age verification by navigating to Google Account Age Verification and verifying date of birth in Google Account Personal Info.

  4. Complete Phone Verification and turn on 2-Step Verification (2SV) on the Google Account associated with your project.

  5. Once age, phone and 2sv are configured, retry your request or create a new API key in Google AI Studio.

  6. If completing these steps still does not restore access (or if using a model requiring a paid tier), you might want to consider adding prepayment credits directly in Google AI Studio and/ or attaching a Google Cloud Billing account in the Google Cloud Console. Please note this will mean you lose your free tier quota.

  7. If you are on a paid tier:

    1. Check for banners / error callouts in the AI Studio Projects page & the Billing page. Mostly these flags cause visible banners or other errors on these pages with concrete next steps / appeal links. You can also check the email address associated with your project for information on next steps.

    2. If your GCP project/ billing account is suspended, you must submit an appeal directly through the Google Cloud Console following the Project Suspension Guidelines (Help Center)

3

UPDATE / CORRECTION

The project information originally included in this topic was incorrect. A complete identity audit confirmed that the Hermes integration affected by the Gemini API restriction actually uses:

  • Project name: My Project 949..
  • Project ID: possible-sun-502018-p3
  • Project Number: 7091661502..

The previously listed project, gen-lang-client-0254386563, is unrelated to the failing Hermes Gemini API configuration.

Current verified findings:

  • Google AI Studio marks the actual project as Restricted.
  • The project quota tier is unavailable.
  • GET /v1beta/models returns HTTP 200.
  • A direct generateContent request returns HTTP 403 PERMISSION_DENIED: “Your project has been denied access. Please contact support.”
  • The same failure occurs outside Hermes, so Hermes routing and local configuration have been ruled out.
  • Age eligibility is confirmed, the phone is verified, 2-Step Verification is enabled, and the required terms have been accepted.
  • No visible Google Account security or Trust and Safety warning was found.
  • Both Gemini projects visible under the same Google account are marked Restricted.

Could a Gemini API team member please manually review project possible-sun-502018-p3 and clarify:

  1. What eligibility or security restriction is currently applied?
  2. Is the restriction account-level or project-level?
  3. Is Billing required to restore access?
  4. Is any regional or account verification still required?
  5. What exact action is required to remove the Restricted status?

No email address, API key, key fingerprint, phone number, birth date, recovery email, token, or other secret is included in this message.

Thank you.