Hey everyone at WondTech! Got some important news for those of you working with Google's Gemini API. Google is changing how its API keys look and work, and you might have already noticed it. If you've recently generated a Gemini API key through Google AI Studio, you might have seen it start with AQ.Ab... instead of the familiar AIza... This isn't a mistake; it's part of a planned update from Google. They are moving from an 'AIza...' Standard key format to a new 'AQ.Ab...' Auth key. New keys you create now come out in this updated style automatically. So, what does this mean for you? Well, the new AQ.Ab... keys work perfectly fine with the native Gemini API endpoint. However, if you're using OpenAI-compatible endpoints or certain third-party tools that were built to expect the old AIza... format, your new AQ.Ab... key might get rejected. It’s important to check your integrations to see if they’re affected. And here’s a critical part for existing users: Google has a timeline for phasing out the old AIza... keys. As of June 19, 2026, unrestricted Standard keys (the ones starting with AIza... that didn't have specific usage restrictions) started to be rejected by the Gemini API. This deadline has already passed for many. If you have an AIza... key with 'explicit restrictions', it will continue to work beyond that date, but don't get too comfortable. By September 2026, 'all' Standard keys, regardless of any restrictions, will stop working completely. What should you do? If you rely on Gemini API, it's wise to generate a new key through Google AI Studio. This will give you an AQ.Ab... Auth key. Then, test it with your applications, especially if you're using non-native Gemini endpoints or third-party tools. If you’re using an old AIza… key, make sure it has explicit restrictions, or plan to replace it before September 2026. This is a staged shutdown, so staying updated is key to avoiding service interruptions. Keep your projects running smoothly by adapting to these changes now!