AI summarized from verified sources
Gemini API key management is moving to safer auth keys
You can improve key security while planning the migration early.
SOURCE CHECK
1 sources
Sources
Key Points
- 1New keys are auth keys by default
- 2Unrestricted keys rejected from June 19
- 3Standard keys end in September
Google is moving the Gemini API from standard keys to auth keys. New keys are already created as auth keys, unrestricted standard keys are rejected from June 19, 2026, and standard keys are scheduled to stop working in September 2026.
What changed
Google is moving Gemini API authentication from standard API keys to auth keys tied to service accounts. New keys are already created as auth keys, and the old path is being phased out.
Why it matters
Standard keys are harder to control at a fine-grained level, especially if they are exposed. Auth keys make tighter permissions and leak response easier to enforce.
Impact for users
Developers using Gemini API need to check existing key restrictions and migrate to auth keys. The June 19 and September deadlines matter if you want to avoid interruptions.
Briefs that include this news
Use daily, weekly, and monthly briefs to understand the surrounding context.
Daily / 2026-06-21
A Day of Progress in AI Safety and Migration: Latest Moves from Gemini API, Claude, and OpenAI
Weekly / 2026-06-15 to 2026-06-21
AI News Summary for the Third Week of June 2026: Safety Operations, Migrations, and Enterprise Adoption Advance
Monthly / 2026-06-01 to 2026-06-30
June 2026 AI News Roundup: Anthropic Resumes Access and Expands Work Features, While Google and OpenAI Strengthen Practical Tools