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

Perplexity | Base URL mismatch

Perplexity returning 404/405 / Base URL mismatch 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
Base URL mismatch
medium
Status code
404/405
base-url-mismatch
Sample models
5
Sonar · Sonar Deep Research · Sonar Pro
Error route summary
Error type
base-url-mismatch
medium
Provider
Perplexity
Status code
404/405
Read-only check. Detection data burns after 5 minutes.
Read-only check. Detection data burns after 5 minutes.

What this error usually means

Perplexity returning 404/405 / Base URL mismatch 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: Base URL mismatch
  • Status code: 404/405

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 404/405, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.

Next action

Base URL mismatch 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