Perplexity

PASS consensus from 2 PASS, 1 PARTIAL.

The Sonar quickstart links key generation, sets PERPLEXITY_API_KEY, and provides working SDK and cURL calls on one page. The key-generation card and a working curl call are both present, but the entry-point Overview and Quickstart list only Router, Agent, Search, and Embeddings, so reaching the Sonar path requires leaving the quickstart for a section the docs mark as retiring in five days. The Sonar quickstart page walks from API key creation through a working Python/cURL/TypeScript example, but Sonar is deprecated in favour of the Agent API (sunset 2026-09-27).

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The page omits numeric Router limits, and the FAQ contradicts its API-specific tier and limiter rules. One page states the six tier thresholds, per-tier Agent QPS, per-tier per-model Sonar RPM, embeddings QPS, and the separate 50 query units per second Search API limit, and the tier thresholds match the FAQ table exactly. The rate-limits page is thorough and self-consistent, but the FAQ describes rate limiting as a universal leaky-bucket algorithm while the rate-limits page states 'Rate limiter behavior differs by API; one algorithm does not apply across the platform' and documents a rolling-one-second window for the Agent API.

PARTIAL consensus from 3 PARTIAL.

The Router page says to honor Retry-After, but the SDK examples calculate delays without reading that header. Retry-After is documented only for the Router API, so a 429 from the Agent, Sonar, or Search endpoints leaves the retry interval undocumented, and the FAQ contradicts the rate-limits page by describing a single leaky-bucket algorithm where the rate-limits page states the algorithm differs by API and that the Agent API uses a rolling one-second window rather than continuous token refill. The Retry-After header is documented only for the Router API, and the SDK error-handling guide does not use it in its exponential-backoff example, so a developer must cross-reference two pages to assemble the full correction.

PASS consensus from 3 PASS.

The guide covers project setup, key creation, Bearer authentication, replacement-key validation, deployment, and old-key revocation. One page carries the project prerequisite, the console creation step, the generate_auth_token and revoke_auth_token endpoints with request and response shapes, a four-step zero-downtime rotation sequence, a runnable rotation class, and a troubleshooting table. The API Key Management page documents the full lifecycle, manual and programmatic key generation, authentication, rotation with a zero-downtime strategy, and revocation, with complete code examples for both endpoints.

PASS consensus from 3 PASS.

The Sonar quickstart's official Python client and cURL examples use the same sonar-pro model and messages payload. The official Python SDK is installed with pip install perplexityai and imported as perplexity, the minimal example is shown side by side with the equivalent curl against https://api.perplexity.ai/v1/sonar, and the docs explicitly reconcile the apparent path difference instead of leaving the reader to guess. The SDK overview gives installation and authentication, and the GitHub README along with each API quickstart page shows working Python examples that match the REST / Sonar / Search / Agent cURL calls in model, endpoint, and parameter structure.