Routeless Radar calls Perplexity's Sonar API for search-backed brand discovery checks. The integration can include the target market as user-location context, then records the answer, returned search results or citations, usage, timing, and failure state. Perplexity belongs to Radar's base provider coverage and is measured as its own source, not blended with another provider.
Evidence verified 2026-09-28 · Vendor facts reviewed 2026-09-28
Radar contains a direct Perplexity Sonar provider with user-location context, search-result and citation parsing, usage records, timing, estimated cost, and explicit failure handling. Perplexity belongs to the base provider set.
The evidence supports Radar's API-based Perplexity measurement. It does not claim consumer-app equivalence, exact device simulation, Perplexity partnership, or fixed provider behavior.
Radar sends a buyer-style question to Perplexity's Sonar API, includes market context when eligible location data is available, and stores the answer with returned search sources.
Evidence: Radar contains a direct Perplexity provider and public methodology for grounded AI visibility checks.
Radar resolves the market attached to the check and maps available country, region, city, and coordinate data into Perplexity's user-location options.
Evidence: Verified in Radar's Perplexity request builder and provider tests.
The provider parser normalizes returned search results and citations. Usage and timing remain attached to the same provider attempt.
Evidence: Verified in Radar's Perplexity response parser and orchestration path.
The Perplexity API key remains in the server-side provider environment. It is not sent to the browser or included in public observation records.
Perplexity credentials stay in the server-side provider environment. Public observations can include the answer, sources, timing, and usage totals, but not the API key, private prompt controls, internal request identifiers, or exact cost rates.
Radar distinguishes successful observations from authentication, quota, timeout, malformed-response, and provider failures. A failed Perplexity call is recorded for operations and does not become a successful visibility result.
Product context for Perplexity and other grounded AI visibility checks.
How Routeless treats answers, citations, locations, and repeated observations.
Yes. Radar contains a direct Sonar API provider with search-backed answers, citation parsing, location context, usage accounting, timing, and explicit error handling.
Yes. Radar maps eligible country, region, city, and coordinate data into the provider's user-location options for local checks.
Perplexity is part of Radar's base provider coverage, together with OpenAI and Gemini.
Not necessarily. Radar identifies its API method and does not claim to reproduce every consumer interface, account, device, or personalization condition.
Yes. The provider parser normalizes available search results and citations so the answer can be reviewed with its returned sources.
Perplexity official site. The Perplexity name and logo belong to their owner. Inclusion documents Routeless implementation experience and does not imply partnership, certification, or endorsement.
Share the account access, records, expected events, and the workflow that must recover when delivery fails.