# Keep support for Sonar-pro on the Agents API

**URL:** https://community.perplexity.ai/t/keep-support-for-sonar-pro-on-the-agents-api/6172
**Category:** Bug Reports
**Tags:** agent-api, api, sonar
**Created:** [September 21, 2026, 11:43pm UTC](https://community.perplexity.ai/t/keep-support-for-sonar-pro-on-the-agents-api/6172 "2026-09-21T23:43:00Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![dev](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/dev/32/2490_2.png) [@dev](https://community.perplexity.ai/u/dev)
#### Post date: [September 21, 2026, 11:43pm UTC](https://community.perplexity.ai/t/keep-support-for-sonar-pro-on-the-agents-api/6172/1 "2026-09-21T23:43:00Z")

</div>

## **Pre-flight checklist**

- This is about the Perplexity API, not the Perplexity app, Computer, Comet, or web UI.
- I have removed API keys, secrets, and private data.
- I have included enough information for someone else to reproduce the issue.

## **Bug type**

- Other API bug
  - API docs issue
  - Backwards Compatibility

## **Affected API area**

- Agent API

## **Summary**

The [Sonar Pro - Perplexity](https://docs.perplexity.ai/docs/sonar/models/sonar-pro) page says:

> Sonar Chat Completions is now [Agent API.](https://docs.perplexity.ai/docs/agent-api/quickstart) Sonar will be supported until September 27, 2026.

I’m aware that the [Migrate from Sonar to the Agent API - Perplexity](https://docs.perplexity.ai/docs/agent-api/migrate-from-sonar/overview#how-sonar-chat-completions-maps-to-agent-api-presets) suggests moving from `sonar` to `preset="fast"` and from `sonar-pro` to `preset="low"`:

 ![image](https://us1.discourse-cdn.com/flex001/uploads/sonar1/original/2X/c/c9d4c040b55378665f9b3d065c95be6570872b3a.png)

But these aren’t 1-1 transitions; we have done **benchmarks** and have precisely chosen `sonar` and `sonar-pro` for their great performances on our **specific use cases**.

We could do benchmarking for presets, but that’s a time consuming task and even a bit **risky** as there’s no guarantee that the same “backend” model will be consistently used on your server, so this also adds risks for our production app.

The [Agent API Models - Perplexity](https://docs.perplexity.ai/docs/agent-api/models#perplexity) only shows the `perplexity/sonar` on the table — no mention to `perplexity/sonar-pro` (same for other models in the `sonar` family):

 ![image](https://us1.discourse-cdn.com/flex001/uploads/sonar1/original/2X/7/7755a361f0f025a92a71a40928d1ca113d703c12.png)

So we’re able to keep force using `sonar` with `model="perplexity/sonar"`, but don’t have an alternative to `sonar-pro` on our Tier 4 production app.

## **Expected behavior**

Allow forcefully using `model="perplexity/sonar-pro"` on the Agents API for a low-risk migration w/ backwards compatibility .

## **Actual behavior**

Docs only mention about migrating from `model="sonar-pro"` to `preset="low"`, adding risks to migration.

---

<div class="post-metadata">

### Author: ![CandidOrca79](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/candidorca79/32/3595_2.png) [@CandidOrca79](https://community.perplexity.ai/u/CandidOrca79)
#### Post date: [September 25, 2026, 1:39pm UTC](https://community.perplexity.ai/t/keep-support-for-sonar-pro-on-the-agents-api/6172/2 "2026-09-25T13:39:38Z")

</div>

This is a clear backwards-compatibility concern. Allowing `sonar-pro` through the Agent API would make migration safer and avoid unexpected changes in production performance.