Key error diagnosis

Perplexity | invalid API key

Perplexity returning 401 / invalid API key should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider

Perplexity

global provider route

Error type

invalid API key

high

Status code

401

invalid-api-key

Sample models

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.

What this error usually means

Perplexity returning 401 / invalid API key should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider: Perplexity
Error type: invalid API key
Status code: 401

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

Open key checker

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

Open providers

Perplexity

Open models

Sonar · Sonar Deep Research · Sonar Pro