Provider: Perplexity
Respan supports both Perplexity Sonar models and the Perplexity Agent API while keeping unified observability for logs, cost, latency, and reliability.
The Agent API can call Perplexity’s own Sonar model or third-party models offered by Perplexity. Through Respan, use an explicit model or a nonempty fallback chain; preset-only requests do not pass the current model validation.
Perplexity Sonar models require bring your own key (BYOK). Sonar usage cannot be paid with Respan credits. The Agent API has separate credential handling.
Quick setup
Add your Perplexity credentials
Configure your Perplexity credentials on the Providers page before using the Sonar examples below. See Use your own Perplexity key.
Send your first request
After configuring your Perplexity credentials in Respan, pick the integration that matches your stack. The base URL is https://api.respan.ai/api and your application authenticates with RESPAN_API_KEY.
OpenAI SDK
Vercel AI SDK
Respan API
Perplexity is OpenAI-compatible. Point the OpenAI SDK at the Respan gateway and call any Perplexity model.
Use Perplexity Agent API
Perplexity’s Agent API uses the OpenAI Responses shape. The route is activated only by the X-Respan-Route-Provider: perplexity header. These examples call Perplexity’s own Sonar model, perplexity/sonar.
This request uses RESPAN_API_KEY for Respan authentication and PERPLEXITY_API_KEY as a request-scoped provider credential. You can omit respan_params.credential_override if Perplexity is already configured under Gateway → API keys → Bring your own key, or when managed Perplexity credentials are available through Respan credits for the Agent API route.
The response reports the model returned by Perplexity and its authoritative USD cost. Set stream: true for Responses API server-sent events, or use models for an ordered fallback chain. Respan requires an explicit model or a nonempty fallback chain; preset-only requests do not pass its model validation.
For third-party model choices, see Perplexity’s Agent API model list. Requests to those models still use the Perplexity route header and Perplexity credentials.
See the Responses API guide for all request shapes, Agent API parameters, header rules, logging, and billing behavior.
More integrations
Perplexity models work with every Respan gateway integration:
Switch models
Change the model parameter to call any supported model through the same client. Use the perplexity/ prefix to disambiguate when routing across providers. Browse the full list on the Models page.
Use your own Perplexity key (BYOK)
Perplexity Sonar models require your own Perplexity credentials. Configure them in Respan or pass them with each request using one of the options below.
Global (UI)
Per-request (Code)
Agent API credentials are provider-scoped. Legacy Sonar values in available_models do not restrict Agent API model, preset, or fallback requests.
Add Perplexity
Select Perplexity and paste your perplexity.api_key. Grab one from the Perplexity API settings page.
Override credentials per model (Optional)
Use credential_override when one model on a request should use a different Perplexity key than the default.
Log without proxying (Optional)
Already calling Perplexity directly? Send logs to Respan asynchronously to track cost, latency, and performance for those external calls.
See the logging guide for the full setup.