I am using Google AI Studio with a paid Gemini API project and prepaid billing.
Veo 3.1 Fast was previously working correctly for me and I successfully generated several videos.
Now every new video generation request returns:
“Failed to generate video: permission denied. Please try again.”
I have tried Veo 3.1 Fast and Veo 3.1. The error persists.
My project is paid and AI Studio confirms that I am using a paid API key.
This is a legitimate low-volume creative project for testing short marketing/lifestyle videos.
Could you please check whether there is an access restriction, entitlement issue, or automated security flag on my project and restore Veo access if this is a false positive?
I can provide my project ID, screenshots, timestamps and other diagnostic information privately if needed.
The Rate Limit page explicitly lists Veo 3 Generate, Veo 3 Fast Generate, and Veo 3 Lite Generate, each with available limits of 2 RPM and 10 RPD. Usage is 0, so this is not quota exhaustion.
The Projects and Billing pages show the correct project and billing account, with no actionable warning or appeal banner.
Following the troubleshooting advice given in a similar thread, I attempted to create a fresh API key in AI Studio for the same project. That request was rejected immediately with: “Failed to generate API key. The request is suspicious. Please try again.”
This new result strongly suggests an automated security/trust flag affecting AI Studio or the account/project control plane. The Veo request is also rejected before it is recorded in usage.
Could a Google AI Studio / Gemini API team member please initiate a manual Trust & Safety review and remove the restriction if this is a false positive? I can provide the project ID, billing account reference, timestamps, and screenshots privately to a Googler. I will not publish API keys.
Could you also confirm that the below verifications are done. If not done, please do so and retry creating a new api key linked to your billing-linked project and retry API requests. Just want to rule out any edge cases, Thanks!
The request still fails immediately with the exact error:
“Failed to generate API key. The request is suspicious. Please try again.”
Therefore, the issue persists after completing all requested account-security checks. Could you please escalate this for a manual review of the account/project restriction or automated Trust & Safety flag?
The error could have been triggered by browser-side anti-automation checks instead of an account restriction (as your account is already on paid tier 1). Please try using a different browser or incognito window, closing browser developer tools (DevTools), disable suspicious browser extensions or custom user-agent overrides, and try generating a new key in a clean browser window.
I have the same problem. I’m also using a paid Tier 1 account and get the same error message. I’ve completed age verification, two-factor authentication, and phone verification. Even using the Chrome browser in incognito mode with all extensions disabled didn’t help.
Following the suggestions in this thread, I opened a clean Chrome Incognito session with extensions and DevTools disabled. In that session I was able to create a new Gemini API key for the same billing-enabled Paid Tier 1 project without receiving the previous “suspicious request” error.
I then linked and saved the new key in my normal Google AI Studio session. Veo 3.1 successfully generated a video, and AI Studio now confirms that the new key is active.
One detail: during testing, video generation also succeeded once while AI Studio still appeared to reference the previous key. Therefore, I cannot confirm whether creating the new key itself fixed the problem or whether a temporary browser-side/security restriction cleared at the same time. What I can confirm is that PERMISSION_DENIED is no longer reproducible and Veo video generation is working normally.