Current documented limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| Agent API tier rangeQPS and RPM are independent limits and a request must fit both: Tier 1 is 3 QPS / 150 RPM, Tier 2 8 QPS / 500 RPM, Tier 3 17 QPS / 1,000 RPM. | Tier 0: 1 QPS / 50 RPM; Tier 4: 33 QPS / 4,000 RPM; Tier 5: 33 QPS / 8,000 RPM | Permanent cumulative-spend tiers | PerplexitySep 17, 2026 |
| Search API throughputEach query in a multi-query request consumes one unit while billing stays per request; the limit is a leaky bucket independent of usage tier. | 50 query units per second with a 50-unit burst | All usage tiers | PerplexitySep 17, 2026 |
| Sonar model RPMTier 0 allows 50 RPM for sonar, sonar-pro and sonar-reasoning-pro and 5 RPM for sonar-deep-research; Tier 5 allows 4,000 and 100 RPM; tiers unlock at $50, $250, $500, $1,000 and $5,000 cumulative spend. | Tier 0: 5–50 RPM; upper tiers: up to 100–4,000 RPM | Model and tier specific | PerplexitySep 17, 2026 |
| cumulative credit thresholdsOnce reached, tiers are retained and do not downgrade. | Tier 1 at $50; Tier 5 at $5,000 cumulative credits | API accounts | PerplexitySep 17, 2026 |
How to apply Perplexity API limits safely
The monitored baseline covers Agent API tier range, Search API throughput, Sonar model RPM, cumulative credit thresholds. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.
- Match the production workload to the exact scope printed beside each value and confirm it in the active Perplexity API console, configuration, or response headers.
- Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
- Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.
Specific limit pages
These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.
Perplexity Agent API Rate Limits
Perplexity Agent API Rate Limits, verified against Perplexity API's official documentation with scope, implementation impact, caveats, and a direct check.
Perplexity Search API Rate Limit
Perplexity Search API Rate Limit, verified against Perplexity API's official documentation with scope, implementation impact, caveats, and a direct check.
Perplexity Sonar API Rate Limits
Perplexity Sonar API Rate Limits, verified against Perplexity API's official documentation with scope, implementation impact, caveats, and a direct check.
Perplexity API Usage Tier Thresholds
Perplexity API Usage Tier Thresholds, verified against Perplexity API's official documentation with scope, implementation impact, caveats, and a direct check.