# Atlas with Perplexity Sonar in 2026 > Perplexity Sonar models, including Sonar Pro with its 200,000 token context window, are designed for live web results and up-to-date information. Perplexity Sonar models are invaluable in Atlas for developers needing live web results and up-to-date API information, especially when library versions or recent changes are critical. With models like Sonar at $1.00/$1.00 per Mtok, they offer targeted research capabilities, allowing Atlas to fetch current data directly from the web. ## Key takeaways - Perplexity Sonar models provide live web results with citations, crucial for 2026 API and library version research. - Sonar Pro offers a substantial 200,000 token context window for extensive information gathering. - Sonar's symmetric $1.00/$1.00 per Mtok pricing is cost-effective for long, research-heavy answers. - Sonar Deep Research allows 32,768 output tokens, which is 8x the output cap of plain Sonar, suitable for detailed writeups. - Sonar and Sonar Reasoning Pro are capped at 4,096 output tokens, making them unsuitable for generating large unified diffs. - Sonar Pro's output is $15.00 per Mtok, making it more expensive than most frontier coding models for agentic tool loops. ## When should I use Perplexity Sonar with Atlas? Perplexity Sonar models are best utilized in Atlas for research-intensive tasks in 2026, particularly when the answer depends on live web results or recent API changes. These models are the only entries in the registry that return live web results with citations as a native part of the completion. Atlas developers should wire Perplexity Sonar models not as their primary build model, but as the model to switch to when the answer depends on a library version or an API that changed last month. This capability is crucial for staying current in a rapidly evolving development landscape. The models load through `@ai-sdk/perplexity`, a dedicated AI SDK package, ensuring that citation metadata survives the round trip instead of being flattened into prose. This preserves the integrity and verifiability of the information Atlas retrieves, making it a powerful tool for accurate, up-to-date research. ## What are the context window and pricing for Perplexity Sonar models? Perplexity Sonar models offer diverse context windows and pricing structures for Atlas users in 2026. Sonar Pro leads with a 200,000 token context window, while Sonar, Sonar Reasoning Pro, and Sonar Deep Research all provide a 128,000 token context. The Perplexity Sonar family provides several options for Atlas users. Sonar Pro offers a substantial 200,000 token context window. The other models,Sonar, Sonar Reasoning Pro, and Sonar Deep Research,each provide a 128,000 token context window. Pricing varies across the models: Sonar is priced symmetrically at $1.00/$1.00 per Mtok for both input and output. Sonar Pro is $3.00 per Mtok for input and $15.00 per Mtok for output. Sonar Reasoning Pro and Sonar Deep Research are both priced at $2.00 per Mtok for input and $8.00 per Mtok for output. Sonar's flat $1.00/$1.00 per Mtok symmetric pricing means a research-heavy turn with a long answer costs the same per token in both directions, which can be cost-effective for extensive information retrieval. ## What are the output limitations and tradeoffs of Perplexity Sonar models in Atlas? Perplexity Sonar and Sonar Reasoning Pro cap output at 4,096 tokens, which is far too small to emit a large unified diff, making them unsuitable as primary build models in Atlas for 2026. Sonar Pro also has a high output cost of $15.00 per Mtok. While excellent for research, Sonar and Sonar Reasoning Pro have a significant tradeoff: they cap output at 4,096 tokens. This limitation means they are not suitable for tasks requiring the generation of large unified diffs, which are common in Atlas's build agent operations. Therefore, these models should not be considered primary build models. Sonar Pro, while offering a larger context window, comes with a higher output cost of $15.00 per Mtok, which is more expensive per output token than most frontier coding models. Furthermore, Sonar Pro is not specifically tuned for agentic tool loops, which might impact its efficiency in certain automated workflows. However, Sonar Deep Research stands out by allowing 32,768 output tokens against its 128,000 context, providing 8x the 4,096 output cap on plain Sonar, making it capable enough for a real writeup or more substantial research summaries. ## How does Atlas integrate with Perplexity Sonar for research tasks? Atlas connects to Model Context Protocol servers and exposes their tools to the agent, allowing direct integration with Perplexity Sonar models for research turns in 2026. Atlas lets you switch the active model and provider on the fly. Atlas is designed for flexibility, allowing developers to switch the active model and provider on the fly using favorites and recents. This capability is perfectly suited for integrating Perplexity Sonar models as dedicated research tools. Instead of replacing your primary build model, you can add Perplexity as a favorite in the `/models` dialog. This setup allows `model.cycle_recent` to quickly flip to a Sonar model for a research turn and then back to your build model. For more complex research, Atlas can fan out work to subagents. You can pin `"perplexity/sonar-deep-research"` for a research subagent, letting the plan agent hand the findings to the build agent, leveraging Sonar's unique web-fetching and citation capabilities without disrupting the core development workflow. ## 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 and add Perplexity as a favorite in the `/models` dialog, so `model.cycle_recent` flips to it for a research turn and back. 4. For a research subagent, pin `"perplexity/sonar-deep-research"` and let the plan agent hand the findings to the build agent. ## FAQ ### Can Perplexity Sonar models be used as a primary build model in Atlas? No, Sonar and Sonar Reasoning Pro cap output at 4,096 tokens, which is far too small for emitting large unified diffs required by build agents in Atlas. They are best used for research turns. ### What is the context window for Perplexity Sonar Pro? Perplexity Sonar Pro offers a substantial 200,000 token context window, making it suitable for deep research tasks within Atlas. ### How much does Perplexity Sonar cost per million tokens? Perplexity Sonar has symmetric pricing at $1.00/$1.00 per Mtok for both input and output, making research-heavy turns cost-effective. ### Which Perplexity Sonar model is best for detailed writeups in Atlas? Sonar Deep Research is ideal for detailed writeups, allowing 32,768 output tokens against its 128,000 token context, which is 8x the output cap of plain Sonar. ### Why should I use Perplexity Sonar with Atlas? Perplexity Sonar models are uniquely designed to return live web results with citations, making them invaluable in Atlas for research turns where answers depend on current library versions or recently changed APIs. ### Is Perplexity Sonar Pro cost-effective for agentic tool loops? Perplexity Sonar Pro is not tuned for agentic tool loops, and its $15.00 per Mtok output pricing is more expensive than most frontier coding models for such tasks. ### How does Atlas handle citation metadata from Perplexity Sonar? Atlas loads Perplexity Sonar models through `@ai-sdk/perplexity`, a dedicated AI SDK package, ensuring that citation metadata survives the round trip instead of being flattened into prose, preserving data integrity. ### Can Atlas use Perplexity Sonar for subagent tasks? Yes, Atlas can fan out work to subagents. You can pin `"perplexity/sonar-deep-research"` for a research subagent, allowing the plan agent to hand its findings to the build agent. --- Canonical HTML: https://seashell.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: SeaShell is proprietary with a free core. It is not open source and there is no public source repository.