Gemini-4-argon returns 403 "Request rejected in accordance with our terms of use and policies" for a paid Tier 2 project; same key works in AI Studio

Project: superplanet-tool (paid Tier 2, billed through a reseller billing account)
Model: gemini-4-argon
Since: 2026-10-14, still happening on 2026-11-03

  • generateContent / streamGenerateContent (key in query or x-goog-api-key, also the official google-genai Python SDK) → 403 PERMISSION_DENIED, “Request rejected in accordance with our terms of use and policies.”
  • POST /v1beta/interactions with gemini-4-argon → 403 “Permission denied.”
  • models.get and countTokens for gemini-4-argon → 200
  • The same key works for gemini-3.8-flash and Nano Banana 2.1.
  • In the AI Studio playground, selecting the same key, gemini-4-argon answers normally.
  • A minimal request (“hi”, no system instruction, no tools, no files) is also rejected, from both a server in Seoul and an office PC in Korea.
  • Rejected requests still count toward RPD on the rate-limit page.
  • No warning or restriction banner on the Projects or Billing pages.

Could you check whether a policy flag or a reseller-billing restriction applies to this project for gemini-4-argon, and request a manual review? I can share the project number and billing account ID by DM.

Update (Nov 11): the block now covers gemini-4-carbon as well. Same API key, same project:

  • gemini-4-argon → 403 “Request rejected in accordance with our terms of use and policies”
  • gemini-4-carbon → same 403
  • gemini-3.8-flash → 200 OK

So this looks like a project-level restriction on the Gemini 4 family only, not a key or
billing problem. There is still no warning banner, “Unavailable” marker or appeal link
anywhere in AI Studio for this project, so we have no way to see why it was flagged or how
to request a review.

Could someone from the Gemini API team check whether this project is flagged and tell us
how to get it reviewed? Happy to share the project number privately.

Were you able to resolve this?

I am facing the same issue, but only with gemini-4-carbon on two of my accounts. It does allow one/two prompts in a while before throwing 403 errors. Interesting.

Still not resolved. Update (Nov 13):

  • gemini-4-hydrogen (released Nov 12) is rejected the same way. All three Gemini 4 models return
    403 “Request rejected in accordance with our terms of use and policies”; gemini-3.8-flash is fine.
  • A second API key from the same project behaves identically.
  • The same request sent through the Batch API is accepted, then fails per request with
    code 7 “The caller does not have permission” – so this looks like a project-level permission
    block, not a content filter.
  • We never received a restriction notice by email, and AI Studio shows no banner or appeal link.

We are now going through our Google Cloud account team. If anyone from the Gemini API team can
see what is attached to this project, we would appreciate a pointer.

YES FOR ME。 what about you.

Resolved (Nov 16).

For anyone hitting the same 403 on Gemini 4: it was not a ToS violation. Our Google Cloud
account team explained that, depending on account conditions such as prior AI usage history, a
conservative default access restriction had been applied to the newest top-tier models at the
billing-account level. It does not show anywhere in AI Studio or the Cloud console, and the API
returns the same “Request rejected in accordance with our terms of use and policies” 403 as a real
policy rejection, which is why it looked like a flag.

The account team reviewed our workload and lifted it; all three models (argon, carbon, hydrogen)
now work. The lift applies to the whole billing account, so future Gemini models should work too.

What worked for us: contacting our Google Cloud account team (sales representative) with the
project ID and billing account ID. The forum and billing support could not act on it. If you
bought through a reseller/partner, ask them to put you in touch with the Google account team.

Thanks to everyone who shared their cases here.