TestKey.ai logo
TestKey.ai
KEY CHECKER & MODEL MARKET
You are hereHome
Key error diagnosis

Google | access forbidden

Google returning 403 / access forbidden should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider
Google
global provider route
Error type
access forbidden
high
Status code
403
access-forbidden
Sample models
32
Gemini 2.0 Flash · Gemini 2.0 Flash Lite · Gemini 2.5 Flash
Error route summary
Error type
access-forbidden
high
Provider
Google
Status code
403
Read-only check. Detection data burns after 5 minutes.
Read-only check. Detection data burns after 5 minutes.

What this error usually means

Google returning 403 / access forbidden should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

  • Provider: Google
  • Error type: access forbidden
  • Status code: 403

How to prove it during checking

Read-only check. Detection data burns after 5 minutes.

  • Run read-only identity first: confirm whether the key really belongs to Google, not just a compatible protocol.
  • Then list models or run a lightweight probe: check whether models like Gemini 2.0 Flash · Gemini 2.0 Flash Lite · Gemini 2.5 Flash are visible and return stable evidence.
  • Finally record 403, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.

Next action

access forbidden should not only show failed. The console should return the next move: refill balance, change Base URL, switch model, add permission, change egress IP, hold listing, or monitor.

  • Read-only check. Detection data burns after 5 minutes.
  • global provider route
  • Gemini 2.0 Flash · Gemini 2.0 Flash Lite · Gemini 2.5 Flash