TestKey.ai logo
TestKey.ai
KEY CHECKER & MODEL MARKET
You are hereHome
Core routes

Keep clicks and crawl depth focused on the few pages that resolve intent fastest.

Already holding a key? Check it first, then keep reading.
Confirm ownership, visible models, and resale signals before deciding whether models, pricing, protocols, or providers matter next.
Key error diagnosis

AI21 | project scope missing

Diagnose AI21 project scope missing (403) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.

Provider
AI21
global provider route
Error type
project scope missing
medium
Status code
403
project-scope-missing
Sample models
1
Jamba Large 1.7
Error route summary
Error type
project-scope-missing
medium
Provider
AI21
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

Diagnose AI21 project scope missing (403) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.

  • Provider: AI21
  • Error type: project scope missing
  • 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 AI21, not just a compatible protocol.
  • Then list models or run a lightweight probe: check whether models like Jamba Large 1.7 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

project scope missing 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
  • Jamba Large 1.7