Perplexity Search API Citations and Brand Mentions Monitoring for AI Search

Perplexity Search API citations and brand mentions monitoring are different products. Engineering teams ask for an API key. SEO teams ask whether Perplexity named them. We will not let those tickets share a title in the weekly deck, because they are not the same work and they are not owned by the same person. Conflating them is how a procurement team buys an API seat and an SEO team ends the quarter with no mention log. The two requests sound adjacent in a meeting, and that adjacency is exactly what causes the wrong purchase, because the budget gets spent against the wrong question.

The official Search API returns real-time ranked web results as structured data (title, url, snippet, optional dates), with domain filters, languages, and regions. Perplexity's own docs say: use Search when you need raw results for your own processing. For an LLM-generated answer with citations inside an application you ship, use the Agent API. That is a clean split, and it is the vendor's split, not ours. Reading it as the vendor wrote it saves a lot of meetings, because the two APIs are aimed at two different buyers, and the docs are explicit about which buyer is which.

Neither API is a brand-mention monitor against what a buyer sees in Perplexity. Building a nightly Search-API scrape of your category is engineering. It is not a GEO dashboard. We will not report API hits as "we were mentioned," because a row in a ranked result list is not a mention in an answer a buyer read. The two objects look similar in a spreadsheet and mean different things in a review. A ranked URL is a retrieval result. A mention is a string inside a generated answer. Counting the first as the second inflates the number and hides the question the SEO team actually needs answered.

When we tell a client to buy the API

They are shipping a product that needs ranked links, or they are piping results into their own retrieval stack. Domain allowlists and denylists are documented. That is developer infrastructure. We will introduce their eng lead to the docs and step back. We will not run it as the SEO mention program, because it is not one, and pretending it is one is how the SEO team inherits a bill and a job they did not sign up for. The test for whether to buy the API is whether the buyer is building something. If nothing is being built, the API is the wrong line item.

When the question is "did Perplexity name us on this sales prompt, and whose URL did it footnote," we buy monitoring. That question is about a stored answer, not about a ranked result, and the answer to it does not come out of the Search API. The distinction is storage. The Search API returns what it retrieved now. Monitoring returns what the model generated and footnoted, kept over time, so you can see whether the footnote changed and when.

The monitoring layer we run

Promptwatch paid plans replay your prompts against the Perplexity UI, daily, with mention versus citation and citation analytics. ChatGPT, Gemini, Claude, and Overviews sit on the same project. Essential is $95/mo with visitor analytics and country-level targeting, but no listed crawler-log allowance. Professional is $245/mo with 25 million crawler logs plus state and city targeting. Kick-off is $199/mo with those features, unlimited projects, and 10 seats. Business is $579/mo with 100 million logs. Explore is ChatGPT only and limited to 10 prompts.

Agent Analytics logs whether Perplexity's crawler fetched you on Professional and the agency plans. Visitor analytics through a script or GTM attach a click if one arrived. Query fan-outs, topics, tags, personas, and country targeting start on Essential. State and city targeting require Professional or an agency plan. The reason the tier split matters is that a national brand and a city brand ask different questions, and a tool that only does country cannot answer the city question no matter how many prompts you load. The tier is not an upsell lever. It is the line between "can we see the country" and "can we see the city", and the city is where most of the actual commercial intent lives.

Otterly at $29 can include Perplexity in the base set, with up to seven days of lag. Peec at $95 can include it in three models (extra $35 to $165; Claude is Enterprise). Profound Starter is $99 annual and ChatGPT only. Growth is $399 annual. Enterprise is about $2,000 to $5,000+/mo. These are monitors at different price points and different depths. None of them is the Search API, and the Search API is not one of them.

Ahrefs and Semrush stay. They are not the Perplexity UI. They are still the systems of record for links and for Google rank, and we do not cancel them when we add a Perplexity column.

How to get cited by ChatGPT is still the passage habit for pages you control. Google Overviews stay on Search Central: our reading.

What we will not do

We will not count Search API rows as citation share in a QBR. We will not tell SEO to provision an API key instead of a prompt list. We will not claim Promptwatch wraps the Search API, because it does not. The claim we brief is real UI monitoring against the consumer Perplexity answer, daily, with the URL the model actually footnoted.

FAQ

You can count whether your domain appeared in raw results. That is not the consumer answer. Do not report it as brand visibility.

Does the Agent API monitor Perplexity.com?

No. It is for cited answers in an app you build.

Should SEO own the API key?

Only if SEO is also shipping product. On our retainers, SEO owns the prompt list. Eng owns the API.

What to do this week

If you are shipping a product, read Search versus Agent API on Perplexity's docs.
If you are doing SEO, skip the API key.
Load 15 Perplexity prompts into Promptwatch Essential ($95), or Professional if crawler logs or city targeting are required. Save cited URLs, not just names.
Allow Perplexity's crawler. Check Agent Analytics on Professional or an agency plan.
Email hello@1001seomedia.com if you want the API-versus-monitor split written into the SOW so procurement stops buying the wrong thing.