Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Perplexity API has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 4 scoped observations for Perplexity API. The baseline covers Agent API tier range, Search API throughput, Sonar model RPM, cumulative credit thresholds. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| Agent API tier rangeThe same tiers range from 1 to 33 queries per second. | Tier 0: 50 RPM; Tiers 4–5: 2,000 RPM | Permanent cumulative-spend tiers | PerplexityAug 22, 2026 |
| Search API throughputSearch uses a leaky bucket and is independent of the account's usage tier. | 50 requests per second with a 50-request burst | All usage tiers | PerplexityAug 22, 2026 |
| Sonar model RPMDeep Research, Sonar, and asynchronous endpoints each have separate values. | Tier 0: 5–50 RPM; upper tiers: up to 100–4,000 RPM | Model and tier specific | PerplexityAug 22, 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 | PerplexityAug 22, 2026 |
Tracked constraints and impact
Agent, Search, and Sonar API rate limits across permanent spend tiers. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
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.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Perplexity API baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Agent, Search, Sonar, tier, burst, and 429 behavior