Output billingSee ratesPublished units and conditions below
Specifications
Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.
Context / input limit
Not collected
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
Maximum input tokens
Not collected
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
Maximum output
Not collected
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
Parameters
Not collected
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
Architecture
Not collected
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
Languages
Not collected
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
Knowledge cutoff
Not collected
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
Tool calling
Not collected
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
The current migration guide explicitly says legacy synchronous and streaming requests keep working through gradual Agent API reformulation.
Batch processing
Not collected
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
Fine-tuning
Not collected
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
Context caching
Not collected
Not verified for this exact historical release. Model names alone are not a numeric context/parameter specification; current Sonar facts are not inherited.
Historical API service tier; exact underlying checkpoint/weight identity unverified.
Version changes
November 2025 adds Pro Search orchestration; December 2025 adds automatic image/video result selection. Agent API migration recommends preset fast.Source for Version changes (opens in a new tab)
Built-in tools do not establish support for arbitrary custom functions.
Legacy synchronous and streaming calls are being reformulated as Agent API requests, rolling out by model. Original tier behavior and billing should not be assumed to persist.
Regions
Not collected
Prices retain their published currencies and billing units below.
Published billing units · original currency · observed 14 Oct 2026
Category
Usage
Rate
Unit
Historical Sonar pricing
Input tokens1
$3.00
1M tokens
Historical Sonar pricing
Output tokens1
$15.00
1M tokens
Historical Sonar pricing
Request fee: low search context1
$6.00
1K requests
Historical Sonar pricing
Request fee: medium search context1
$10.00
1K requests
Historical Sonar pricing
Request fee: high search context1
$14.00
1K requests
Rate conditions
Historical Sonar calculator rates retained in official documentation captured October 14, 2026. Legacy support ended September 27, 2026; current synchronous/streaming requests are translated to Agent API. Effective dates and ongoing applicability of these legacy rates are unverified. These are not current Agent API prices or a complete cost-per-question quote. Pro Search rates are explicitly excluded from the calculator. No cache rate is supplied for these legacy tiers.
Retention, training use, regional processing and enterprise terms have not been summarized for this endpoint.
Caching
Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.
01 / INITIAL INPUTProcess & retain
The system processes eligible input and retains reusable state.
02 / LATER REQUESTCheck available state
Reuse depends on matching input, session state and the cache policy.
03 / CACHE HITReuse & generate
Reusing state can reduce repeated work. Any charges follow the billing rules below.
Perplexity API (historical)
sonar-pro
Not verified
Historical exact-model cache contract not verified. Current Agent API cache rates are not inherited.
How it works
Not collected
Historical exact-model cache contract not verified. Current Agent API cache rates are not inherited.
Minimum reusable input
Not collected
Historical exact-model cache contract not verified. Current Agent API cache rates are not inherited.
Lifetime & refresh
Not collected
Historical exact-model cache contract not verified. Current Agent API cache rates are not inherited.
How to enable it
Not collected
Historical exact-model cache contract not verified. Current Agent API cache rates are not inherited.
Usage fields
Not collected
Historical exact-model cache contract not verified. Current Agent API cache rates are not inherited.
Billing rules
Not collected
Historical exact-model cache contract not verified. Current Agent API cache rates are not inherited.
Limits & data boundaries
Not collected
Historical exact-model cache contract not verified. Current Agent API cache rates are not inherited.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Caching reviewed 14 Oct 2026
What the measurements say
No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.
Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.
The record behind the model
Why it is included
The provider identifies this search/reasoning API tier, but the reviewed evidence does not establish an independently released proprietary checkpoint. It is a managed component; public or third-party base models are not reclassified as closed weights.