API key error
Identify a missing or invalid Gemini API key before changing model code.
{"error":{"code":401,"message":"API key not valid. Please pass a valid API key.","status":"UNAUTHENTICATED"}}Developer Utilities
Decode Gemini API and Antigravity Agent error responses locally with likely causes, fix steps, and retry templates.
This tool runs locally in your browser. Your input is not sent to a backend or paid API.
Paste a sanitized Gemini API or Antigravity Agent error and get local troubleshooting notes.
Detected category: Authentication
Remove API keys, user data, repository names, and private prompts before sharing error output.
How to use
Follow this workflow to complete the task locally without leaving the page.
Paste a Gemini API error JSON response, SDK error message, or sanitized terminal output.
Run the decoder to identify the likely failure category.
Review the probable cause, fix steps, and retry template.
Copy the troubleshooting notes into your issue, docs, or local debugging checklist.
Examples
Use these examples to understand common workflows and expected input formats.
Identify a missing or invalid Gemini API key before changing model code.
{"error":{"code":401,"message":"API key not valid. Please pass a valid API key.","status":"UNAUTHENTICATED"}}Check whether an Antigravity Agent request failed because of a stale preview ID or wrong API surface.
{"error":{"code":404,"message":"Agent antigravity-preview-05-2026 was not found or is not available for this project.","status":"NOT_FOUND"}}FAQ
Answers to common questions about behavior, privacy, and practical usage.
No. The decoder runs locally in your browser and does not send pasted API errors to a backend or paid API.
No. It explains likely causes and practical next steps so you can fix keys, model names, agent IDs, state IDs, request shape, or retry behavior yourself.
Yes. It includes checks for common Antigravity Agent preview problems such as unknown agent IDs, missing environment IDs, previous_interaction_id issues, and broad task timeouts.
No. Even though the tool runs locally, paste sanitized error output and never include real API keys, secrets, user data, or private repository content.