What Perplexity's API Retirement Means for Your AI Visibility Score

Perplexity shut down the Sonar Chat Completions API today. If you use an AEO monitoring tool or had someone run an AI visibility audit recently, there is a real chance that the Perplexity component of that score is now either erroring or reporting zero -- silently, without flagging anything wrong.

This is not a theoretical risk. It is active as of September 27, 2026.

What Changed Today

The Sonar Chat Completions API was the endpoint most AEO monitoring tools used to programmatically query Perplexity and check whether your business gets cited. After today, any tool hitting the old endpoint receives HTTP 403 with the error code `agent_api_migration_required`.

That is not a timeout. It is not a connection error. It is a deliberate, permanent gate.

We tracked this migration across multiple research sessions in our vault, starting with a filing on 2026-09-19 and updated through today. The timeline matters: the September 27 retirement date appeared in Perplexity's blog post and documentation warning banner. But it did not appear in their migration guide (which still reads "Sonar remains supported" as of today) and it did not appear in their official changelog. Engineering teams that track API deprecations by watching changelogs missed this entirely.

The LLM Gateway -- one of the major API routing services -- confirmed migration on September 25. But that only covers tools routed through their service. Everything else is unconfirmed until the tool explicitly says so.

Two Failure Modes, Not One

When we first filed this finding on 2026-09-19, we flagged a silent failure risk: tools that hadn't migrated might return zero citations without throwing an error. The retirement day data resolves this more clearly than we expected.

Any tool hitting the old Sonar endpoint today gets the hard 403. But the silent failure has shifted location -- it now applies to tools that technically migrated the API endpoint but did not update their citation-parsing code.

Here is why that matters. Perplexity's old Sonar API returned citations inside `choices[0].message.content`. The new Agent API returns citations inside `output[]`. A tool that swapped the URL but not the parsing logic will execute without error and return zero citations. The tool shows green; the data is wrong.

This failure mode is harder to detect than a 403. A 403 surfaces. A tool that silently reads an empty field reports "0 citations" in a way that looks like legitimate data -- not a bug, just a business with no Perplexity presence.

Why This is the Worst Platform to Lose Right Now

There is a timing problem here that makes the API retirement more than a routine infrastructure issue.

In August 2026, ChatGPT underwent a structural change in how it handles web retrieval -- documented in our research sessions from August 8 to 23, 2026. ChatGPT shifted toward direct domain routing, and Reddit citations collapsed 86.4% in a single week. Open-web social content stopped flowing into ChatGPT's retrieval pipeline.

What happened to those Reddit citations? Our methodology rec filed 2026-08-30, drawing on Pierview data covering 44,488 Reddit citations from July 1 through August 19, 2026, documents the answer: Perplexity absorbed them. Perplexity now holds 71% of cross-platform Reddit citations -- a figure that roughly doubled from July into early August as ChatGPT vacated the space.

For SaaS businesses, consumer brands, and any business with organic Reddit community presence, Perplexity has become the primary platform where Reddit-based social proof converts into AI citations. ChatGPT stopped counting Reddit. Perplexity started counting it more.

The result: Perplexity is now the platform that matters most for a specific and growing class of AI citation activity, at precisely the moment most API-based tracking tools broke.

The HubSpot Problem

HubSpot's AEO Grader is one of the largest AI visibility scoring products in the market. Our competitive monitoring documented that HubSpot's AEO platform had passed 205,000 customers as of this summer.

HubSpot AEO Grader uses Perplexity Sonar as one of its three scoring models -- alongside GPT-5.2 and Gemini 2.0 Flash, based on September 2026 review-site documentation. We searched for any HubSpot migration announcement -- blog post, changelog, product update -- as recently as today. Nothing found.

Any business owner who ran a HubSpot AEO Grader score today may be looking at either a 403 error on the Perplexity component, or a zero Perplexity score, depending on how HubSpot handles the failure internally. Their Perplexity data, as of today, is actively suspect.

This is not an indictment of HubSpot's engineering. The migration window opened August 13 -- 45 days. The retirement date was published, just not where most teams would look for it. The problem is that 200,000+ users have no way of knowing their score carries a data integrity issue until HubSpot says something.

How to Tell if Your Monitoring Data Is Affected

If you use a monitoring tool and want to verify whether your Perplexity data is still valid, ask one direct question: does the tool use the Perplexity API internally, or does it check Perplexity via browser automation?

If API-based, ask specifically: have they confirmed migration to Perplexity's Agent API endpoint, and on what date?

The right answer from a vendor is specific: "Yes, we migrated to the Agent API on [date], and we confirmed citation parsing against `output[]`." A vague reassurance or no response means the data is unconfirmed.

**The manual check is unaffected.** The Sonar API retirement only affects developer integrations. Perplexity.ai itself runs exactly as it did. Typing your business name or a relevant query into perplexity.ai and reading the response gives you accurate data regardless of any platform's migration status.

What to Do Right Now

If you want an accurate read on your Perplexity visibility after today's retirement, the most reliable approach is a tool that performs browser-level checks or one that has explicitly confirmed Agent API migration with citation-parsing verification.

Sourcepull's Signal Check queries the live Perplexity interface directly -- not the Sonar API. Today's retirement does not affect what we report. If you want to see where your business actually stands across Perplexity, ChatGPT, Claude, and Gemini, with data sourced from the platforms rather than from an API layer that may have just broken, that is what Signal Check measures.

The broader point is worth keeping: API-based and browser-based AI citation data are not equivalent. They report different things, and today's retirement is a clear demonstration of why. When an API layer changes, tools that depend on it report whatever the API returns -- including zero, silently. When the platform itself changes, browser-based checks see it immediately.

Know which one you are looking at.