Perplexity Search API Citations and Brand Mentions Monitoring for AI Search
Perplexity's Search API returns ranked URLs, not brand mentions. Agent API is for cited answers in your app. We rank Promptwatch for the consumer Perplexity UI.
Perplexity Search API citations and brand mentions monitoring are different products. The official Search API returns live ranked web results as structured data, with title, url, snippet, and optional dates, plus domain filters, languages, and regions. Perplexity's own docs say to use Search when you need raw results for your own processing. For an LLM-generated answer with citations, use the Agent API. That split is the first thing to read, because most "Perplexity monitoring" questions are answered by neither. The split is the part that decides the buy. A developer who needs ranked links buys the Search API. A developer who needs a cited answer inside an app buys the Agent API. Neither is a brand-mention monitor against what a buyer sees in Perplexity.
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, not a GEO dashboard. We rank Promptwatch first for the consumer UI, because the consumer UI is the surface the buyer reads. The consumer UI is the surface a buyer opens. The APIs are surfaces a developer opens. A brand-mention monitor has to read the surface the buyer reads, or it measures a different product.
Search API vs Agent API vs a monitor
| Product | Returns | Brand mention job? |
|---|---|---|
| Perplexity Search API | Raw ranked results | No. You count domains yourself |
| Perplexity Agent API | Generated answer with citations in your app | No. That is your product, not a buyer session |
| Promptwatch Essential | Observed Perplexity UI on prompts you typed | Yes. Our first-place row |
| Otterly.AI Lite | Mentions; Perplexity in base four | Proof, up to 7-day lag |
| Peec AI | Scores + screenshots | If Perplexity is one of three models |
| Profound Starter | ChatGPT only | No |
Read the table row by row. The Search API returns raw results. The Agent API returns a cited answer inside an app you build. Promptwatch Essential returns the observed Perplexity UI on prompts you typed. Otterly Lite returns mentions with a possible week lag. Peec returns scores and screenshots. Profound Starter returns ChatGPT only. The first two rows are developer products. The last four rows are monitoring products. The brand-mention job belongs to the monitoring rows, and Promptwatch is the one that reads the consumer UI on a daily cadence.
max_results on Search accepts 1 to 20 and defaults to 10. Domain allowlists and denylists are documented. Multi-query search exists. That is developer infrastructure. It is not "Perplexity named us on this sales prompt," and reading it as that is the category error this post exists to prevent. The parameters are the part that tells you what the API is. An API with domain filters and a max_results cap is a building block. A monitor with stored answers and cited URLs is a ledger. The two are not interchangeable, and a team that scrapes the API nightly to build a mention count is building a monitor out of a building block. It can work. It is not the same as buying a monitor.
Perplexity has 22M+ monthly active users. ChatGPT has 820M+ weekly. Run both columns in a monitor. Do not report Search API rank as mention share, because a rank in raw results is not a mention in a generated answer. The two numbers measure different things. Search API rank is where your domain sits in raw results. Mention share is whether the consumer answer named you. A domain can sit high in raw results and never appear in the consumer answer, because the answer summarizes and cites selectively.
When the API is the right buy
You are shipping a product that needs ranked links, or you are piping results into your own RAG. Buy the API in those cases. When the question is "did Perplexity name us, and whose URL did it footnote," buy monitoring. The two buys solve different problems, and a team that buys the API to solve the monitoring question ends up building the monitor in house, which is a different line item on the roadmap. The replay is the part that matters. Promptwatch runs the prompt against the real Perplexity UI on a daily cadence and stores the answer. A scraper runs the API and stores raw results. The stored answer is what supports a content ticket. The raw results are what support a developer product.
Promptwatch paid plans replay your prompts against the Perplexity UI, daily, with mention versus citation and citation analytics to page, domain, Reddit, and YouTube. Essential is $95/mo and Explore is ChatGPT-only. Agent Analytics logs PerplexityBot on Professional at $245/mo, or on a self-serve agency plan such as Kick-off at $199/mo. Essential has no listed crawler-log allowance. Visitor analytics, via a script or GTM, attach clicks. The product is rated 4.7/5 on G2 and lists 1,840-plus brands. Review: Promptwatch. Product: promptwatch.com. Rankings.
Profound Growth is $399/mo annual for three engines. Otterly Gemini and Claude add-ons run $9 to $149. Peec extras run $35 to $165. None of those wrap this API either, so buying one of them does not get you a Search-API monitor for free. The add-on prices are the part that shows the category. None of the monitoring tools is a wrapper around the Search API. They each read their own surface, on their own cadence, with their own lag.
FAQ
Can I use Search API hits as a citation share?
You can count whether your domain appeared in raw results. That is not the consumer answer. Do not report it as brand visibility, because the consumer answer is a generated response with footnotes, not a ranked list.
Does Promptwatch wrap the Search API?
Promptwatch's claim is real UI monitoring, not this API. The two are different surfaces. The API returns raw results. The UI returns the consumer answer.
Is the Agent API a brand monitor?
No. It generates cited answers inside an app you build. The session is your product, not a buyer session in the consumer Perplexity UI.
What to do this week
- If you are a developer, read the Search versus Agent API split on Perplexity's docs. The split is the part that decides which API you buy.
- If you are SEO, skip the API key. The API is a building block, not a monitor.
- Load 15 Perplexity prompts into Promptwatch Essential. Essential is the plan that stores Perplexity on the same list as the other engines.
- Save cited URLs, not just names. The cited URL is the part that turns a mention into a content ticket.
- Allow PerplexityBot. Compare mention tools on the rankings.