# Atlas with Perplexity Sonar in 2026: The Live-Web Research Model, Not the Build Model > Perplexity Sonar costs $1.00/$1.00 per Mtok and is the only model family in the Atlas registry that returns live web results with citations natively. Perplexity Sonar models are the only entries in the Atlas registry that return live web results with citations as a native part of the completion. Inside Atlas, the terminal-native coding agent, Perplexity Sonar is worth wiring not as your build model but as the model you switch to when the answer depends on a library version or an API that changed last month. Pricing runs Sonar $1.00/$1.00 per Mtok, Sonar Pro $3.00/$15.00, Sonar Reasoning Pro $2.00/$8.00, and Sonar Deep Research $2.00/$8.00. ## Key takeaways - Perplexity Sonar models are the only entries in the Atlas registry that return live web results with citations natively. - Sonar costs $1.00/$1.00 per Mtok with symmetric pricing, Sonar Pro is $3.00/$15.00, and Sonar Reasoning Pro and Sonar Deep Research are $2.00/$8.00. - Sonar Pro has a 200,000 token context, while Sonar, Sonar Reasoning Pro, and Sonar Deep Research run 128,000 tokens. - Sonar Deep Research allows 32,768 output tokens, 8x the 4,096 output cap on plain Sonar. - Perplexity Sonar is not a build model: a 4,096 token output cap cannot emit a large unified diff. - @ai-sdk/perplexity is a dedicated AI SDK package, so citation metadata survives the round trip instead of being flattened into prose. ## What is Perplexity Sonar best at inside Atlas? Perplexity Sonar is best inside Atlas for research turns where the answer depends on something that changed recently. Sonar models are the only entries in the 2026 registry that return live web results with citations as a native part of the completion, rather than as a bolted-on search tool. Perplexity Sonar loads through @ai-sdk/perplexity, a dedicated AI SDK package, so citation metadata survives the round trip instead of being flattened into prose. That is the technical reason to prefer Sonar over pasting search results into a general model: the sources come back as structured data, not as a paragraph the model wrote about sources. The workflow that fits Atlas is a research turn, not a build turn. Atlas drafts a plan in a read-only plan agent and asks before switching to a build agent, and the plan agent is exactly where a Perplexity Sonar answer about a breaking API change belongs. ## Why is Perplexity Sonar not a good build model for Atlas? Perplexity Sonar and Sonar Reasoning Pro cap output at 4,096 tokens, which is far too small to emit a large unified diff. Atlas computes a unified diff for every file edit and surfaces it for approval before writing, so a 4,096 token output ceiling makes Sonar unusable as an Atlas build model. The output cap is the whole story here. A multi-file refactor can easily exceed 4,096 tokens of diff, and a model that truncates mid-patch is worse than useless in an agentic edit loop. Sonar Pro is not the escape hatch either: at $15.00 output per Mtok it is more expensive per output token than most frontier coding models, and it is not tuned for agentic tool loops. Perplexity Sonar earns a slot in Atlas as a research model that hands findings to a build model, and the Atlas architecture supports exactly that: subagents can run in the foreground or in parallel background sessions, so a Sonar research subagent can run while the build agent waits. ## How much does Perplexity Sonar cost per million tokens? Perplexity Sonar costs $1.00/$1.00 per Mtok, Sonar Pro is $3.00/$15.00, Sonar Reasoning Pro is $2.00/$8.00, and Sonar Deep Research is $2.00/$8.00. Sonar at a flat $1.00/$1.00 per Mtok is the only symmetric price in the family, which matters for long research answers. Symmetric pricing means a research-heavy turn with a long answer costs the same per token in both directions on plain Sonar. Compare that with Sonar Pro, where output is $15.00 per Mtok, 5x the $3.00 input rate. If your Atlas research turn is short-question, long-answer (which is the normal shape for a research turn), the asymmetry on Sonar Pro is what actually drives your bill, not the input price. Sonar Deep Research at $2.00/$8.00 sits in between and buys you the largest output budget in the family. ## What context window and output limits does Perplexity Sonar have? Perplexity Sonar Pro runs a 200,000 token context. Sonar, Sonar Reasoning Pro, and Sonar Deep Research run 128,000 tokens. The output limits matter more: Sonar Deep Research allows 32,768 output tokens, which is 8x the 4,096 output cap on plain Sonar. For Atlas, the output number is the one to check before pinning a Perplexity Sonar model. Sonar Deep Research allowing 32,768 output tokens against a 128,000 context is enough for a real writeup, the kind of research artifact a plan agent can actually use. Plain Sonar at a 4,096 output cap will give you an answer, not a document. Sonar Pro's 200,000 token context is the largest window in the Perplexity family, but a big input window on a model you are only asking research questions of is less useful than a big output budget on a model you want a report from. ## How do I use Perplexity Sonar alongside a build model in Atlas? In Atlas, leave your build model alone and add Perplexity as a favorite in the `/models` dialog. Then `model.cycle_recent` flips to Perplexity Sonar for a research turn and back to your build model afterward, which is the intended 2026 pattern for a model that caps output at 4,096 tokens. Atlas lets you switch the active model and provider on the fly with favorites and recents, which is precisely the mechanism Perplexity Sonar is designed for here. The heavier pattern is a research subagent: pin `"perplexity/sonar-deep-research"` for that subagent and let the plan agent hand the findings to the build agent. Atlas drafts a plan in a read-only plan agent and asks before switching to a build agent, so the handoff is a first-class step rather than a hack. Your build model stays on a provider tuned for agentic tool loops, and Perplexity Sonar does the one thing nothing else in the registry does. ## When should I pick a different model than Perplexity Sonar? Pick a different model than Perplexity Sonar for any Atlas task that writes code. Sonar and Sonar Reasoning Pro cap output at 4,096 tokens, and Sonar Pro at $15.00 output per Mtok is more expensive per output token than most frontier coding models while not being tuned for agentic tool loops. Perplexity Sonar is a specialist, and the failure mode is treating it as a generalist. If the question is about your own repository, a coding model with a real output budget is better and cheaper. Atlas already searches code with hybrid semantic and keyword retrieval fused by reciprocal rank fusion and indexes code by AST declarations using tree-sitter, so it does not need a web-search model to answer questions about code it has indexed. Reach for Perplexity Sonar only when the answer lives outside your repository and outside the model's training data: a library that changed last month, an API that shipped a breaking version, a deprecation you have not read yet. ## Setup 1. Export PERPLEXITY_API_KEY from your Perplexity API dashboard. 2. Run `atlas models perplexity` to confirm the four Sonar models resolve. 3. Leave your build model alone. Perplexity Sonar caps output at 4,096 tokens and cannot emit a large unified diff. 4. Add Perplexity as a favorite in the `/models` dialog so `model.cycle_recent` flips to it for a research turn and back. 5. For a research subagent, pin `"perplexity/sonar-deep-research"` and let the plan agent hand the findings to the build agent. ## FAQ ### how to add perplexity sonar to atlas Export PERPLEXITY_API_KEY from your Perplexity API dashboard, run `atlas models perplexity` to confirm the four Sonar models resolve, then add Perplexity as a favorite in the `/models` dialog so `model.cycle_recent` flips to it for a research turn. ### how much does perplexity sonar cost per million tokens Sonar is $1.00/$1.00 per Mtok, Sonar Pro is $3.00/$15.00, Sonar Reasoning Pro is $2.00/$8.00, and Sonar Deep Research is $2.00/$8.00. Sonar is the only one with symmetric input and output pricing. ### can perplexity sonar write code in an ai coding agent Not well. Sonar and Sonar Reasoning Pro cap output at 4,096 tokens, which is far too small to emit a large unified diff. Use Perplexity Sonar for research turns and hand the findings to a build model tuned for agentic tool loops. ### what is the context window of perplexity sonar pro Perplexity Sonar Pro runs a 200,000 token context. Sonar, Sonar Reasoning Pro, and Sonar Deep Research each run 128,000 tokens. Sonar Deep Research allows 32,768 output tokens against that 128,000 context. ### which perplexity model is best for deep research in an agent Sonar Deep Research at $2.00/$8.00 per Mtok. It allows 32,768 output tokens against a 128,000 context, which is 8x the 4,096 output cap on plain Sonar and enough for a real writeup a plan agent can use. ### does perplexity sonar return citations to an agent Yes. Perplexity Sonar loads through @ai-sdk/perplexity, a dedicated AI SDK package, so citation metadata survives the round trip instead of being flattened into prose. Sonar models are the only registry entries that return live web results with citations natively. ### why is perplexity sonar pro expensive for coding Sonar Pro costs $15.00 output per Mtok, which is more expensive per output token than most frontier coding models, and it is not tuned for agentic tool loops. For writing code, a dedicated coding model is both cheaper and better. --- Canonical HTML: https://runatlas.sh/resources/models/perplexity Source of truth: aeo_pages row `/resources/models/perplexity` (segment: Models) (this file is generated from it, never hand-edited). Licence: Atlas is proprietary with a free core. It is not open source and there is no public source repository.