Skip to main content

Perplexity

Use this when your team already runs on Perplexity and you want that vendor family to stay explicit in Loong config instead of disappearing behind a generic compatibility route.

At A Glance

FieldValue
Built-in kindperplexity
Provider groupDirect Hosted Providers
Protocol familyopenai_chat_completions
Feature familyopenai_compatible
Auth schemebearer
Credential envsPERPLEXITY_API_KEY
Aliasesperplexity_compatible
Default base URLhttps://api.perplexity.ai
Request endpointhttps://api.perplexity.ai/chat/completions
Models endpointhttps://api.perplexity.ai/models

Minimal Config

active_provider = "perplexity"

[providers.perplexity]
kind = "perplexity"
api_key = { env = "PERPLEXITY_API_KEY" }
model = "auto"

Verify It

loong doctor
loong list-models
loong ask --message "Say hello and name the active provider."
If list-models is unreliable for this account or region, pin an explicit provider.model or add preferred_models instead of leaving recovery implicit.

Auth And Routing Contract

ContractValue
Auth optionalno
Model probe auth optionalno
Default API key envPERPLEXITY_API_KEY
OAuth envnone
Primary request routehttps://api.perplexity.ai/chat/completions
Primary model-catalog routehttps://api.perplexity.ai/models