Request allowlist access for Veo 3.1 person generation — project TAHA Video Labs (gen-lang-client-05529216..)

Gemini API
1

Request allowlist access for Veo 3.1 person generation — project TAHA Video Labs (gen-lang-client-0552921651)

Project ID: gen-lang-client-05529216..
Project name: TAHA Video Labs
Account email: a....@gmail.com
Billing tier: Tier 1 (Prepay)
Model: models/veo-3.1-generate-preview (also applies to veo-3.0-generate-001)
Region: Sweden (EU)

Issue:
Since the project was created on July 22, 2026, calls to predictLongRunning for Veo 3.1 with personGeneration: "allow_adult" are being rejected with:

allow_adult for personGeneration is currently not supported

Per the Veo documentation, allow_adult is the only valid and default personGeneration value for EU/UK/CH/MENA regions, so this rejection is inconsistent with documented regional behavior. The API errors dashboard confirms the failures (Usage → Total API Errors, last 28 days):

  • Jul 22, 2026 — 400 BadRequest: 2, 429 TooManyRequests: 4
  • Jul 23, 2026 — 400 BadRequest: 0, 429 TooManyRequests: 2
  • Jul 24, 2026 — 400 BadRequest: 8, 429 TooManyRequests: 1

We’ve confirmed on our end that personGeneration is hardcoded to "allow_adult" in our request payload and has never been changed — this rules out a client-side parameter bug. The 429s appear to stem from the Tier 1 daily quota (10 RPD) on the “Veo 3 Generate” bucket being exhausted, which is a separate issue from the 400 rejection.

Request:
Please allowlist project gen-lang-client-0552921651 (TAHA Video Labs) for personGeneration: allow_adult on Veo 3.1 / Veo 3.0, consistent with our region’s documented eligibility.

Use case:
Generating short-form video content (marketing/documentary segments) via the ScriptForge production pipeline, using real adult subjects in prompts, no minors involved.

Happy to provide additional project details or sample failing request/response payloads if needed.

2

Hello @AMIS_CAMEROON ,

No allowlist is required. For Text-to-Video requests, allow_adult is not a supported personGeneration parameter value. The allow_adult setting is only supported for Image-to-Video requests when providing a reference image.

You have the below options:

  • a. Text-to-Video: Omit the personGeneration parameter entirely or set personGeneration to allow_all.
  • b. Image-to-Video: Omit the personGeneration parameter entirely or set personGeneration to allow_adult when providing a reference image.
  • c. Rate Limits (HTTP 429): These errors occur when requests exceed the Tier 1 Prepay daily quota of 10 requests per day. Submit a Rate Limit Increase Request or upgrade your billing tier in AI Studio.