Tool support requires the appropriate API integration; a supported tool is not automatically active in every chat.
Supported API features and tools
Multi-query research across many web sources
Synthesis into structured, cited reports
A documented 128K-token context
Search-result and usage metadata for reviewing evidence and costs
Before you choose
Broad research generally requires more time and billable work than a focused lookup.
Input/output tokens alone are not a complete cost estimate; citations, reasoning, and searches add charges.
Asynchronous Sonar requests are no longer supported; use Agent API background mode for that integration pattern.
Choose the reasoning effort
lowmedium · defaulthigh
The Sonar model card documents reasoning_effort low, medium (default), and high. Higher effort increases research depth, reasoning tokens, latency, and cost. The current migration guide maps this model to the Agent API high preset; that replacement configuration is not the same control or a promise of an unchanged underlying model.
Perplexity’s migration guide maps Sonar Deep Research to the Agent API high preset. Presets and underlying model selections can change; test results after migrating.
The reviewed model card does not publish a maximum output-token limit or training cutoff. Web access does not make an unknown training cutoff a current date.
This guide’s examples use text. Check the selected endpoint’s current input and output support rather than assuming full parity with another Sonar or Agent API configuration.
Put it to work
Start with a more useful prompt.
Original examples from EZ Ai Assist. Adapt these to your task and the features available in your workspace.
Workflow 01
Map an emerging software category
Define scope before asking for an extensive report.
Prepare a research report on the software category below for a small product team. Limit the review to the stated geography and date range. Cover established products, emerging approaches, buyer requirements, and unresolved technical barriers. Cite primary sources, label vendor claims, and finish with an evidence table and research gaps.
Workflow 02
Review a technical literature base
Make search coverage and exclusions inspectable.
Review publicly accessible research on this technical question. Explain your search scope and inclusion criteria, group the main approaches, and compare methods and reported limitations. Cite each study, distinguish peer-reviewed work from preprints, and identify contradictory findings. Do not invent papers or treat missing evidence as a negative result.
Workflow 03
Prepare a technology due-diligence brief
Turn a broad review into concrete follow-up questions.
Research this technology stack for a potential adoption decision. Cover project maintenance, release history, licensing sources, operational requirements, and documented migration risks. Cite evidence with dates, separate facts from judgments, and end with questions for maintainers and a small proof-of-concept checklist. Do not make a final legal or security determination.
Developer reference
Perplexity API pricing
These are Perplexity Sonar API reference prices, not EZ Ai Assist subscription prices.
Published Sonar reference · USD per 1,000,000 tokens
Token type
Price
Input
$2.00
Output
$8.00
Citation tokens
$2.00
Reasoning tokens
$3.00
Additional API fees · USD
Usage
Rate and unit
Search queries
$5.00per 1,000 searches
These are the published Sonar reference rates, not an estimate of migrated Agent API costs or OpenRouter resale prices. Check the current endpoint, preset, and response usage before budgeting.
The documented cost includes input, output, citation and reasoning tokens plus search queries. Do not count this as an ordinary input/output-only chat request.
Perplexity recommends Agent API for new projects. Migration can change both execution and billing; retain these rates as a clearly scoped Sonar reference.
Common questions
A few things worth knowing.
When should I consider Sonar Deep Research?
Use deep-research-style workflows when a question warrants a broad source review and a structured report rather than an instant answer. Define the research boundary, date range, and evidence standard first, and budget for multiple searches and reasoning tokens.
What changed with the Sonar API?
Perplexity says Sonar Chat Completions support ended September 27, 2026. Synchronous and streaming calls continue through a gradual translation to Agent API requests; async Sonar calls are no longer supported. This does not establish whether EZ Ai Assist or a reseller exposes a particular model.
Which Agent API preset is the documented replacement?
Perplexity maps Sonar Deep Research to high. Treat this as migration guidance, not an identical model or a guaranteed equivalent response. Recheck citations, quality, latency, and usage on representative tasks.
Why can a research request cost more than expected?
Searches, citation tokens, and reasoning tokens are separate metered items in addition to ordinary input and output. Research breadth affects work performed; inspect the response usage rather than guessing from prompt length.
Can I trust every citation?
No. Open the cited pages and confirm they support the exact claim, concern the correct version, and are recent enough. A citation is a starting point for verification, not a guarantee of accuracy.
What do the limits on this page mean?
The model card lists a 128K-token context. It does not establish a maximum output limit or training cutoff in the reviewed documentation. Integration limits may be lower, and search-backed answers still need checking.
Are these fees part of my EZ Ai Assist subscription?
No. The reference table describes Perplexity’s documented API billing. EZ Ai Assist plans are separate, and app availability must be checked in the workspace. These prompts are original starting points, not verified benchmark outputs.
Check the source
Official documentation
Specifications and API prices checked on . Example prompts and workflow advice are editorial guidance from EZ Ai Assist.