Model limit probe

Perplexity: Sonar Deep Research | concurrency limit

Perplexity: Sonar Deep Research concurrency limit decides whether a key can enter a production route. TestKey reads model ID perplexity/sonar-deep-research, provider Perplexity, catalog context, real-key headers, 429 errors, and region signals together.

Model

perplexity/sonar-deep-research

Perplexity: Sonar Deep Research

Provider

Perplexity

5 models in catalog

Limit dimension

concurrency limit

concurrency

Visible signal

real key probe required

Context window: 128,000

Limit matrix summary

Model

perplexity/sonar-deep-research

Limit dimension

concurrency

Visible signal

real key probe required

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

Why this limit matters

Perplexity: Sonar Deep Research concurrency limit decides whether a key can enter a production route. TestKey reads model ID perplexity/sonar-deep-research, provider Perplexity, catalog context, real-key headers, 429 errors, and region signals together.

Model: perplexity/sonar-deep-research
Provider: Perplexity
Limit dimension: concurrency limit

How to prove it

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

Start with the visible signal: real key probe required, then read headers and error bodies with read-only requests.
concurrency limit must bind model ID perplexity/sonar-deep-research; limits from another model at the same provider cannot be reused.
concurrency limit · real key probe required · 128,000

Operator action

Perplexity: Sonar Deep Research concurrency limit is not just a number. It should become route throttling, sale tags, headroom alerts, fallback model suggestions, and price protection.

Read-only check. Detection data burns after 5 minutes.
Visible signal: real key probe required
Context window: 128,000

Open key checker

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

Open models

Perplexity: Sonar Deep Research

Open providers

Perplexity