I am encountering an "Error in Saving Credentials" when attempting to add my Google Gemini API key to my Vapi dashboard. The Error Message: "Couldn't Validate Google Credential. Error: {"error": {"code":404,"message":"This model models/gemini-2.0-flash is no longer available to new users. Please update your code to use a newer model...","status":"NOT_FOUND"}}" Context: Even though I am not selecting Gemini 2.0 Flash for my assistant, it appears that Vapi’s internal validation process (the initial "handshake" to verify the key) is hardcoded to ping that specific model ID. Since Google has restricted or deprecated gemini-2.0-flash for new API keys, the validation fails, and I am unable to save my credentials. Request: Could you please update the validation model used during the "Save Credentials" step to a current stable version, such as gemini-1.5-flash or gemini-2.5-flash? Alternatively, is there a way to bypass this validation so I can save the key and manually select a supported model for my agent? I have attached a screenshot of the error message for your reference. https://cdn.discordapp.com/attachments/1478584552262729991/1478584552669708478/image.png?ex=69a8eeac&is=69a79d2c&hm=a573c3a85f7a8807f5054e91e5de823e551a2d9392bae9e6f0ddc842bbbef93b&

Hi 👋 I can help with this. The issue isn’t your API key it’s happening because Vapi’s credential validation step is trying to ping the deprecated gemini-2.0-flash model. Since Google no longer allows new keys to access that model, the validation call returns a 404, which blocks you from saving the credentials. So basically, the handshake model Vapi is using is outdated that’s what’s causing the error. Quick question: Are you using a newly created Google AI Studio API key, or an older one that previously had access to gemini-2.0-flash? That will help confirm the exact cause 👍

Yes it is a new key, and the only key. And the only option

Perfect, that confirms it. Since it’s a new key, it doesn’t have access to the deprecated Google Gemini model that Vapi is using internally for validation. That’s why you’re getting the 404, and it’s not something you can fix from your side. If you’d like, we can take this privately and I’ll handle it properly for you either by guiding the exact fix or helping get it resolved quickly.

Hi, thanks for reaching out. We're working on a fix for this. Thanks!