What this error usually means
Diagnose Perplexity invalid API key (401) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
- Provider: Perplexity
- Error type: invalid API key
- Status code: 401
Key error diagnosis
Perplexity | invalid API key
Diagnose Perplexity invalid API key (401) by checking balance, Base URL, model permission, region/IP, and visible models before the next fix.
Provider
Perplexity
global provider route
Error type
invalid API key
high
Status code
401
invalid-api-key
Sample models
5
Sonar · Sonar Deep Research · Sonar Pro
Error route summary
Error type
invalid-api-key
high
Provider
Perplexity
Status code
401
Read-only check. Detection data burns after 5 minutes.
Read-only check. Detection data burns after 5 minutes.
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 Perplexity, not just a compatible protocol.
- Then list models or run a lightweight probe: check whether models like Sonar · Sonar Deep Research · Sonar Pro are visible and return stable evidence.
- Finally record 401, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.
Next action
invalid API key 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
- Sonar · Sonar Deep Research · Sonar Pro