Perplexity Review: What It Does, Pricing, and Alternatives

Draft v0.1 — 2026-05-27 KST. content_status = qa_passed. Generated from templates/tool-page-template.md and walked through Section A of qa/adsense-seo-quality-gate.md. Meta description (≤ 155 chars): Perplexity is an AI answer engine that returns cited sources for research-style questions — what it does, its caveats, and how it compares to alternatives.

Quick verdict

• Best for: research-style questions where you want a short synthesized answer plus a list of linked web sources to click through, instead of a single unsourced paragraph from a chat assistant.
• Not ideal for: anyone who needs guaranteed-correct facts without checking originals, or who treats the cited links as a substitute for reading the underlying sources. Citations show where text may have come from; they do not certify that the summary is accurate or complete.
• Pricing model: freemium (a free tier plus a paid consumer "Pro" plan are part of Perplexity's long-standing public positioning). The consumer Pro and pricing pages returned HTTP 403 in this environment's automated fetch on 2026-05-27, so no consumer plan price or feature limit is asserted on this page — verify those live on the official site. A separate, developer-facing API has its own usage-based pricing (see "Pricing and plans").
• Free plan: yes (recorded from the official homepage read on 2026-05-21, when it was reachable; re-confirm current free-tier limits directly on the official site, since the consumer pages could not be re-read on 2026-05-27).
• Last verified: 2026-05-27 (official docs pages read; consumer pages blocked — see Sources)

Source-freshness note (2026-06-24): A 2026-06-24 KST official-source gate rechecked the surfaces you would use to evaluate Perplexity yourself as a cited answer-engine / AI search workflow (you ask a question, get a synthesized answer, and follow the linked sources). Perplexity's official developer documentation remains reachable for API/docs evaluation: the docs overview (https://docs.perplexity.ai/home) returned HTTP 200, resolving to https://docs.perplexity.ai/docs/getting-started/overview (title "Overview - Perplexity"), and the developer API pricing docs (https://docs.perplexity.ai/guides/pricing) returned HTTP 200, resolving to https://docs.perplexity.ai/docs/getting-started/pricing (title "Pricing - Perplexity", H1 "Pricing"). This is developer/API surface availability and docs reachability/title/H1 evidence only — no API rate was re-read, so the existing 2026-05-27 API-pricing rows are unchanged and no new rate is asserted. In the same pass the consumer homepage (https://www.perplexity.ai/) returned HTTP 200 with title "Perplexity", but that is a small consumer shell and a reachability/title signal only, while the consumer /pro path returned HTTP 403 (bot-protection block) and /pricing returned HTTP 404 (not citable). So consumer Pro prices, free-tier quotas, model availability, and feature limits still require verification on the official site and none are asserted here. As always with an answer engine, citations and summaries still require human source-checking — a cited link shows where text may have come from, not that the summary is accurate or complete. No independent ranking, benchmark, speed, accuracy, or superiority claim is made.

Source-freshness note (2026-06-19): A 2026-06-19 KST recheck confirms Perplexity's official developer documentation is reachable and stable: the docs overview (https://docs.perplexity.ai/home) returned HTTP 200 with title "Overview" (consistent with the 2026-06-15 recheck, when it resolved to https://docs.perplexity.ai/docs/getting-started/overview), and the developer API pricing docs (https://docs.perplexity.ai/guides/pricing) returned HTTP 200 with title "Pricing" (resolving to https://docs.perplexity.ai/docs/getting-started/pricing). This is developer/API surface availability and docs reachability/title evidence only — no API rate was re-read, so the existing 2026-05-27 API-pricing rows are unchanged and no new rate is asserted. In the same pass the consumer homepage (https://www.perplexity.ai/) returned HTTP 403 (bot protection), so consumer Pro prices, free-tier quotas, model availability, and feature limits still require verification on the official site and none are asserted here. No independent ranking, benchmark, speed, accuracy, or superiority claim is made.

Source-freshness note (2026-06-15): Perplexity's official developer docs were rechecked on 2026-06-15 and were reachable (HTTP 200): the docs overview at https://docs.perplexity.ai/home now redirects to https://docs.perplexity.ai/docs/getting-started/overview (title "Overview - Perplexity") and the API pricing docs at https://docs.perplexity.ai/guides/pricing now redirect to https://docs.perplexity.ai/docs/getting-started/pricing (title "Pricing - Perplexity"). This supports developer/API surface availability and docs reachability only — it confirms the official docs exist at their new paths and does not re-read or re-verify any specific rate. In the same recheck the consumer Pro path (https://www.perplexity.ai/pro) returned HTTP 200 with title "Perplexity", but that is a small consumer shell (reachability/title signal only), and https://www.perplexity.ai/pricing returned HTTP 403, so consumer Pro prices, quotas, model availability, and feature limits still require verification on the official site and none are asserted here. No independent ranking, benchmark, speed, accuracy, or superiority claim is made.

Source-freshness note (2026-06-07): The official homepage was rechecked on 2026-06-07 and returned HTTP 200 with title "Perplexity", so this page no longer treats the homepage source as needs_verification — it confirms only that the official homepage exists at perplexity.ai. The consumer Pro and pricing pages remained HTTP 403 (blocked) in the same recheck, so all consumer prices, free-tier quotas, model availability, and feature limits still require verification on the official site and none are asserted here. No API/developer pricing was re-fetched in this recheck.

What is Perplexity?

Perplexity is an AI "answer engine" built by Perplexity AI. Instead of returning a ranked list of ten blue links the way a traditional search engine does, it takes a natural-language question, runs web search behind the scenes, and returns a written answer with inline citations pointing back to the web pages it drew from. The pitch is research and Q&A: ask a question, get a synthesized answer, and click the numbered sources to verify or read further.

Perplexity AI also ships a developer platform. Its official documentation describes an Agent API (access to third-party models from OpenAI, Anthropic, Google, and xAI together with web-search tools), a Search API (raw, ranked web-search results with filtering and real-time data), and an Embeddings API (for semantic search and retrieval-augmented-generation pipelines). These are programmatic products distinct from the consumer answer engine most people interact with on the website or apps.

• Vendor: Perplexity AI
• Official homepage: https://www.perplexity.ai/
• Official developer docs: https://docs.perplexity.ai/home
• Category: AI Search & Research (secondary: AI Assistants)

Main use cases

• Use case 1 — Cited research and fact-finding: asking a question and getting a synthesized answer with linked sources you can open, so you have a starting point and a trail to follow rather than an unsourced blob of text. This is the canonical reason people reach for Perplexity over a plain chat assistant.
• Use case 2 — Quick competitive and market lookups: "what does company X sell," "who are the main vendors in category Y," "summarize recent coverage of Z" — the kind of shallow-but-broad scan where the linked sources matter as much as the summary.
• Use case 3 — Reading-list generation: turning a vague topic into a set of open-web sources worth reading, which you then read yourself. Treat the answer as an index into sources, not as the finished research.

Pricing and plans

There are two separate pricing surfaces, and it is important not to conflate them.

Consumer Perplexity (free + Pro). Perplexity has long offered a free tier and a paid consumer "Pro" subscription. However, during this environment's automated fetch on 2026-05-27, https://www.perplexity.ai/pricing and https://www.perplexity.ai/pro both returned HTTP 403 (and the homepage itself returned 403 on the same run, after returning 200 on an earlier check — the site uses bot protection that responds inconsistently to automated requests). Because the consumer pricing pages could not be read, no consumer price, free-tier quota, or Pro feature limit is quoted on this page.

Consumer plan prices and limits should be verified on the official website at https://www.perplexity.ai/pro before you rely on them.

Developer API pricing (separate from consumer plans). Perplexity's official API pricing documentation at https://docs.perplexity.ai/guides/pricing was reachable (HTTP 200) and describes usage-based pricing. As read on 2026-05-27, the docs state:

• Agent API — token-based pricing for third-party models (OpenAI, Anthropic, Google, xAI) "at direct provider rates with no markup."
• Tool pricing (billed per invocation, separate from model token costs): web_search $0.005, fetch_url $0.0005, people_search $0.005, finance_search $0.005 per call.
• Search API — $5.00 per 1,000 requests, with no additional token-based charge.
• An Embeddings API is also documented for semantic search / RAG.

Source: live read of https://docs.perplexity.ai/guides/pricing on 2026-05-27 KST. These are API/developer rates and are unrelated to what an individual pays for the consumer Pro subscription. Re-read the docs before quoting, since API rates change.

Pros

• The core differentiator is real: an answer paired with clickable, numbered citations is genuinely more useful for research than an unsourced chat reply, because it gives you somewhere to verify.
• It spans web, iOS, and Android, plus a documented developer API and SDK, so it can be used both as an end-user product and as a building block.
• The official documentation is detailed and openly accessible, including a published API pricing page and a documentation index — useful for anyone evaluating the programmatic side before committing.

Cons and caveats

• Citations are not a correctness guarantee. A linked source shows where text may have originated; it does not prove the summary faithfully represents that source. Always open and read the originals before relying on a claim.
• Summaries can drop context. Condensing several pages into a few sentences can omit caveats, dates, scope, or contradicting evidence present in the underlying material.
• Source freshness and quality vary. The web pages cited may be outdated, low-quality, or themselves wrong; the engine's selection of which sources to cite is not editorial vetting.
• YMYL caution. Do not treat answers about medical, legal, financial, or other "your money or your life" topics as professional advice. Citations on such topics can look authoritative while still being incomplete or misapplied.
• Consumer pricing could not be auto-verified in this environment on 2026-05-27 (403 on the Pro and pricing pages). Confirm current consumer plan prices and limits directly on the official site.
• Data handling is governed by Perplexity's own policies, which differ between the consumer product and the API. Read the vendor's official privacy and security documentation before sending sensitive content.

Alternatives

• ChatGPT — better if you primarily want a general-purpose conversational assistant with a large plugin/tool ecosystem, and treat web research as a secondary mode rather than the main job.
• Gemini — better if you live inside Google's products and want research-style answers alongside Workspace integration and Google's own models.
• Phind — better if your research skews toward developer and technical questions, where a search-plus-answer tool tuned for code and documentation may fit more closely.

Buyer control and the review boundary

If you are evaluating Perplexity as a buyer rather than a casual searcher, the deciding question is less "does it answer the question?" than "who owns the cited conclusion once you reuse it, and where does the review boundary sit before a synthesized answer becomes a record, a recommendation, or a decision?" An answer engine returns a synthesized answer with linked sources — so the durable control questions are about the source trail behind that answer, not the answer's polish. <span id="perplexity-review-boundary-2026-06-28"></span>

• Treat the answer as an index into sources, not the source. Perplexity returns a written answer with inline citations; those citations show where text may have come from, not that the summary faithfully represents the underlying pages. Decide up front that the cited pages — not the synthesized paragraph — are what your team reads and relies on, and open them before a claim moves forward, as Cons and caveats describes.
• Name who owns a cited conclusion before it is reused. When an answer is going to be pasted into a brief, a customer reply, or a system-of-record decision, name the person who confirms the underlying sources, their dates, and their scope. Ownership of a cited conclusion sits with the human who reused it, not with the engine that assembled it.
• Decide when an answer needs human validation before reuse. A synthesized answer can read authoritatively while dropping caveats, dates, or contradicting evidence present in the originals. Keep a validation step a hard gate before an answer becomes shared or operational — and tighten it for YMYL topics (medical, legal, financial), where a confident citation can still be incomplete or misapplied.
• Route the comparison to the right page. When the real question is Perplexity versus another tool for a specific job, follow the workflow-fit decision paths below — for example ChatGPT vs Perplexity — or browse the AI Search & Research category to scope the field of answer engines before deciding who reviews what.

Evergreen decision framing only. No price, plan, quota, model-availability, benchmark, ranking, speed, accuracy, superiority, security-certification, or legal claim is made here; verify current plan inclusions and data-handling on Perplexity's official pages, and confirm how a cited answer fits your team's review process against your own practice.

Where to compare Perplexity next

Perplexity is an answer/search/research workflow — you ask a question, get a synthesized answer, and follow the cited sources. That shape is not a drop-in substitute for a general-purpose chat assistant in every team workflow, so the useful next question is "for which job?" Right now there is a single direct head-to-head comparison for Perplexity here, so treat this as an early compare-next path, not a broad ranking hub. These paths are organized by workflow fit, not by a winner — each one helps you match a tool's shape to the task in front of you:

• ChatGPT vs Perplexity — when you are weighing a cited answer-engine search flow against a broad conversational assistant, and want to see where each shape fits research versus open-ended chat work.
• ChatGPT — when the job is general-purpose assistance, drafting, and a wide tool ecosystem rather than source-cited web research, and you want a read on that assistant's own caveats.
• AI Search & Research category — to browse the field of answer engines and research tools alongside Perplexity rather than a single head-to-head.
• AI Assistants category — when your underlying need is a general chat assistant for your team's day-to-day rather than a search/research flow, and you want to compare in that category instead.

These links are decision paths, not rankings — no benchmark, price, quota, speed, ranking, or model-availability claim is made here; any such specifics are routed to the official sources.

Who should not use Perplexity

• Anyone who would take a cited answer at face value without opening the sources — the citation UX can create false confidence if the links are never checked.
• Teams whose data-handling rules prohibit sending queries to a third-party web service before reviewing Perplexity's official privacy and security documentation.
• Users who need a single tool that also does production image, video, or audio generation; that is not what an answer engine is for.

Author selection rubric

Choose Perplexity when at least two of these are true:

• Your work is research-shaped: you ask questions and then want to read the sources behind the answer.
• You value a linked source trail more than a longer, unsourced essay.
• You will actually click through and verify, rather than treating the summary as final.

Avoid Perplexity when any of these are true:

• You need certified-correct facts for a YMYL decision without independent verification.
• Your single most important workflow is open-ended creative generation across many media types.
• Your data policy forbids sending the queries you have in mind to an external web service.

Sources

• Official homepage: https://www.perplexity.ai/ — recorded as src-perplexity-homepage-2026-05-21 in data/sources.json, access_status = ok. Reachable (HTTP 200) during the initial 2026-05-21 seed scan; after intermittent HTTP 403 bot-protection on automated re-fetches between 2026-05-27 and 2026-06-06, the homepage was rechecked on 2026-06-07 and returned HTTP 200 with title "Perplexity", so this source again supports official homepage existence/title at perplexity.ai (and only that). Product positioning quoted on this page is still taken from the official docs (below), not from the homepage. The separate consumer Pro/pricing pages remained HTTP 403 in the same 2026-06-07 run — see below.
• Official developer docs (overview): https://docs.perplexity.ai/home — recorded as src-perplexity-docs-home-2026-05-27 in data/sources.json with access_status = ok after a 2026-05-27 page-body read; source for the answer-engine positioning and the Agent/Search/Embeddings API descriptions. Rechecked 2026-06-15 (recorded as src-perplexity-docs-home-2026-06-15, access_status = ok): reachable (HTTP 200) and now redirects to https://docs.perplexity.ai/docs/getting-started/overview (title "Overview - Perplexity") — docs reachability/redirect/title evidence only. Rechecked again 2026-06-19 (recorded as src-perplexity-docs-home-2026-06-19, access_status = ok): reachable (HTTP 200), title "Overview" — docs reachability/title evidence only.
• Official API pricing docs: https://docs.perplexity.ai/guides/pricing — recorded as src-perplexity-docs-pricing-2026-05-27 with access_status = ok after a 2026-05-27 page-body read; source for every API/developer price quoted on this page. These are API rates only, not consumer Pro prices. Rechecked 2026-06-15 (recorded as src-perplexity-docs-pricing-2026-06-15, access_status = ok): reachable (HTTP 200) and now redirects to https://docs.perplexity.ai/docs/getting-started/pricing (title "Pricing - Perplexity") — docs reachability/redirect/title evidence only; the 2026-05-27 page-body API rates above were not re-read in this recheck. Rechecked again 2026-06-19 (recorded as src-perplexity-docs-pricing-2026-06-19, access_status = ok): reachable (HTTP 200), title "Pricing" — docs reachability/title evidence only; the 2026-05-27 page-body API rates were not re-read.
• Official docs/home/pricing reachability gate (2026-06-24): recorded as src-perplexity-docs-home-pricing-2026-06-24 in data/sources.json with access_status = ok, from the 2026-06-24 KST official-source gate (data/perplexity-source-gate-2026-06-24.json / .md). The developer docs overview https://docs.perplexity.ai/home returned HTTP 200 (final https://docs.perplexity.ai/docs/getting-started/overview, title "Overview - Perplexity") and the developer API pricing docs https://docs.perplexity.ai/guides/pricing returned HTTP 200 (final https://docs.perplexity.ai/docs/getting-started/pricing, title "Pricing - Perplexity", H1 "Pricing") — developer/API docs reachability/title/H1 evidence only; no API rate was re-read. The consumer homepage https://www.perplexity.ai/ returned HTTP 200 (title "Perplexity") as a small consumer shell (reachability/title signal only). In the same pass https://www.perplexity.ai/pro returned HTTP 403 (blocked) and https://www.perplexity.ai/pricing returned HTTP 404 (not citable), so consumer Pro prices, quotas, model availability, and feature limits still require official-site verification and none are asserted.
• Consumer Pro/pricing page: https://www.perplexity.ai/pro — recorded as src-perplexity-pro-2026-05-21 with access_status = blocked (HTTP 403 on the 2026-05-27 re-fetch). No consumer price or limit is asserted from it. On the 2026-06-15 recheck (recorded as src-perplexity-pro-reachability-2026-06-15) /pro returned HTTP 200 as a small consumer shell (reachability/title "Perplexity" only — not pricing verification), while https://www.perplexity.ai/pricing returned HTTP 403; consumer prices, quotas, model availability, and feature limits still require official-site verification.

Internal links (at least 3)

• Category pages: /ai-search/, /ai-assistant/
• Alternative tools: /tools/gemini/, /tools/chatgpt/
• Comparison pages: /compare/claude-vs-gemini/, /compare/chatgpt-vs-perplexity/

Disclosure

• Affiliate links: none.
• Sponsored content: none. Perplexity AI has no relationship to this page.
• Generative AI assistance: this draft was authored by Claude Code working from a 2026-05-27 live read of Perplexity's official documentation pages; every API-pricing and positioning claim is constrained to wording visible on those official pages on that date, and consumer pricing is intentionally left unquoted because those pages were blocked.

Trademark notice

Perplexity and Perplexity AI are trademarks of Perplexity AI. Use here is referential only and does not imply endorsement, partnership, or affiliation.

Update log

• 2026-06-28 (buyer-control / review-boundary qualified-traffic increment — LIVE on aistackdb.com after Hermes Cloudflare static-assets upload, NOT a new revenue page/product): added one compact, evergreen "## Buyer control and the review boundary" section placed after "## Alternatives" and before "## Where to compare Perplexity next", carrying durable marker perplexity-review-boundary-2026-06-28 as a single <span id="perplexity-review-boundary-2026-06-28"></span> in the section's lead. It frames Perplexity buying — as a cited-answer / AI-search workflow — around treating the answer as an index into its source trail rather than the source, naming who owns a cited conclusion before it is reused, deciding when an answer needs human validation before it becomes a record/recommendation/decision (with extra YMYL caution), and routing tool-vs-tool questions to the existing /compare/chatgpt-vs-perplexity/, in-page #cons-and-caveats, and /ai-search/ routes already on this page. Existing page/source context only — no web fetch and no data/* edit; no new price/quota/plan/model-availability/ranking/benchmark/speed/accuracy/superiority/security-certification/legal claim; no Gumroad/UTM/affiliate/sponsored/coupon/checkout link; data/tools.json and last_verified_at unchanged; content_type/content_status stay tool_page/qa_passed. Hermes verified JSON/seed validator/canonical production build/ZIP, uploaded the 93-file ZIP through the visible Cloudflare Dashboard static-assets flow, and public /tools/perplexity/ now serves the marker and heading.
• 2026-05-21 (seed): candidate record created from the initial HMP scan; official homepage reachable (HTTP 200).
• 2026-05-27 (qa pass): promoted from candidate to qa_passed. Official docs overview (docs.perplexity.ai/home) and API pricing docs (docs.perplexity.ai/guides/pricing) read live (both HTTP 200) and added as new source entries; consumer Pro/pricing pages and the homepage returned HTTP 403 on this run, so no consumer price is quoted and the homepage source was downgraded to needs_verification. data/sources.json, data/tools.json (pricing_summary, confidence_score, last_verified_at, sources, policy_notes), and content/content-status.json updated. Section A of qa/adsense-seo-quality-gate.md satisfied. Pricing-sensitive (API rates quoted): re-verify by 2026-08-25.
• 2026-06-07 (source-freshness refresh — NOT a new revenue page): updated stale prose so the page no longer says the homepage source is needs_verification. Per data/sources.json src-perplexity-homepage-2026-05-21 (now access_status = ok after the 2026-06-07 13:11 KST re-fetch), the official homepage returned HTTP 200 with title "Perplexity"; this supports homepage existence/title at perplexity.ai only. Added a compact "Source-freshness note (2026-06-07)" near the top and updated the Sources homepage row accordingly. The consumer Pro/pricing pages (/pro, /pricing) remained HTTP 403 in the same run, so no consumer price/quota/model/feature claim is asserted and all consumer pricing is still routed to "verify on the official site"; the existing API/developer pricing rows (from docs.perplexity.ai/guides/pricing, 2026-05-27) were not re-fetched and are unchanged. No volatile price/quota/model/ranking/speed/accuracy/benchmark claim added; no Gumroad/UTM/affiliate/sponsored/coupon CTA or new link added. data/sources.json, data/tools.json, and data/comparisons.json are unchanged by this content edit; content_type=tool_page and content_status=qa_passed unchanged; revenue inventory unchanged.
• 2026-06-08 (internal-link/traffic refinement — NOT a new revenue page): refined the existing "Where to compare Perplexity next" section intro to state honestly that Perplexity currently has a single direct head-to-head comparison here, so the section is an early compare-next path rather than a broad ranking hub. The section remains present exactly once, after "## Alternatives" and before "## Who should not use Perplexity", and still links only the existing qa_passed/category routes /compare/chatgpt-vs-perplexity/, /tools/chatgpt/, /ai-search/, and /ai-assistant/, framed as workflow-fit decision paths. No source was fetched and no volatile claim was added: no price, quota, model-availability, benchmark, ranking, speed, accuracy, or superiority fact is asserted, and no Gumroad/UTM/affiliate/sponsored/coupon CTA or new link was added. data/sources.json, data/tools.json, and data/comparisons.json are unchanged; content_type=tool_page and content_status=qa_passed unchanged; revenue inventory unchanged.
• 2026-06-15 (source-freshness refresh — NOT a new revenue page): added a compact "Source-freshness note (2026-06-15)" near the top (above the 2026-06-07 note). Per a 2026-06-15 KST Hermes official-source recheck, Perplexity's official developer docs were reachable (HTTP 200) and now redirect: docs.perplexity.ai/home → /docs/getting-started/overview (title "Overview - Perplexity", recorded as src-perplexity-docs-home-2026-06-15, access_status = ok) and docs.perplexity.ai/guides/pricing → /docs/getting-started/pricing (title "Pricing - Perplexity", recorded as src-perplexity-docs-pricing-2026-06-15, access_status = ok). These support developer/API surface availability and docs reachability/redirect/title only; no rate was re-read and the existing 2026-05-27 API-pricing rows are unchanged. The consumer /pro path returned HTTP 200 as a small shell (reachability/title only, recorded as src-perplexity-pro-reachability-2026-06-15, access_status = ok, explicitly not pricing verification) while /pricing returned HTTP 403, so consumer Pro prices, quotas, model availability, and feature limits remain routed to official-site verification and none are asserted. The existing homepage source src-perplexity-homepage-2026-05-21 was refreshed with the 2026-06-15 HTTP 200/title "Perplexity" recheck. No volatile price/quota/model/ranking/speed/accuracy/benchmark claim added; no Gumroad/UTM/affiliate/sponsored/coupon CTA or new link added. Only content/tools/perplexity.md, data/sources.json, and content/content-status.json (and content/README.md surfaces) were edited; data/tools.json and data/comparisons.json are unchanged; content_type = tool_page and content_status = qa_passed unchanged; revenue inventory unchanged at 18 tool + 51 comparison = 69 qa_passed revenue pages + 5 site_page drafts.
• 2026-06-19 (source-freshness refresh — local-only, NOT a new revenue page): added a compact "Source-freshness note (2026-06-19)" near the top (above the 2026-06-15 note). Per a 2026-06-19 KST automated recheck, Perplexity's official developer docs were reachable (HTTP 200): the docs overview https://docs.perplexity.ai/home returned HTTP 200 with title "Overview" (recorded as src-perplexity-docs-home-2026-06-19, access_status = ok) and the developer API pricing docs https://docs.perplexity.ai/guides/pricing returned HTTP 200 with title "Pricing" (recorded as src-perplexity-docs-pricing-2026-06-19, access_status = ok). These support developer/API surface availability and docs reachability/title only; no API rate was re-read and the existing 2026-05-27 API-pricing rows are unchanged. In the same pass the consumer homepage https://www.perplexity.ai/ returned HTTP 403, so consumer Pro prices, quotas, model availability, and feature limits remain routed to official-site verification and none are asserted. No volatile price/quota/model/ranking/speed/accuracy/benchmark/superiority claim added; no Gumroad/UTM/affiliate/sponsored/coupon CTA or new link added. Only content/tools/perplexity.md, data/sources.json, and content/content-status.json (and content/README.md surfaces) were edited; data/tools.json and data/comparisons.json are unchanged; content_type = tool_page and content_status = qa_passed unchanged; revenue inventory unchanged at 18 tool + 51 comparison = 69 qa_passed revenue pages + 5 site_page drafts. Local-only: not deployed in this run.
• 2026-06-24 (source-freshness refresh — LOCAL-only, NOT a new revenue page/product and NOT a deploy): added a compact "Source-freshness note (2026-06-24)" near the top (above the 2026-06-19 note), framing Perplexity as a cited answer-engine / AI search workflow. Per a 2026-06-24 KST official-source gate (data/perplexity-source-gate-2026-06-24.json / .md), Perplexity's official developer docs were reachable (HTTP 200): the docs overview https://docs.perplexity.ai/home resolved to https://docs.perplexity.ai/docs/getting-started/overview (title "Overview - Perplexity") and the developer API pricing docs https://docs.perplexity.ai/guides/pricing resolved to https://docs.perplexity.ai/docs/getting-started/pricing (title "Pricing - Perplexity", H1 "Pricing") — recorded as src-perplexity-docs-home-pricing-2026-06-24, access_status = ok. These support developer/API surface availability and docs reachability/title/H1 only; no API rate was re-read and the existing 2026-05-27 API-pricing rows are unchanged. In the same pass the consumer homepage https://www.perplexity.ai/ returned HTTP 200 (title "Perplexity") as a small consumer shell (reachability/title signal only), while the consumer https://www.perplexity.ai/pro returned HTTP 403 (blocked) and https://www.perplexity.ai/pricing returned HTTP 404 (not citable), so consumer Pro prices, quotas, model availability, and feature limits remain routed to official-site verification and none are asserted. No volatile price/quota/model/ranking/speed/accuracy/benchmark/superiority claim added; no Gumroad/UTM/affiliate/sponsored/coupon CTA or new link added. Only content/tools/perplexity.md, data/sources.json, and content/content-status.json (and content/README.md surfaces) were edited; data/tools.json and data/comparisons.json are unchanged; content_type = tool_page and content_status = qa_passed unchanged; revenue inventory unchanged at 18 tool + 51 comparison = 69 qa_passed revenue pages + 5 site_page drafts. LOCAL production ZIP will be verified by Hermes later — not a deploy.
• 2026-06-05 (internal-link/traffic refresh — NOT a new revenue page): added a "Where to compare Perplexity next" section (placed after "## Alternatives", before "## Who should not use Perplexity") linking existing qa_passed/live routes — /compare/chatgpt-vs-perplexity/ (qa_passed comparison), /tools/chatgpt/ (qa_passed tool), and the /ai-search/ and /ai-assistant/ category routes — framed as workflow-fit decision paths rather than rankings, and noting that Perplexity is an answer/search/research workflow and not a substitute for a general chat assistant in every team workflow. Expanded the "Internal links" rows to add /ai-assistant/, /tools/chatgpt/, and /compare/chatgpt-vs-perplexity/. No source was fetched and no volatile claim was added: no Perplexity pricing, quota, model-availability, benchmark, ranking, speed, or accuracy fact is asserted, and no Gumroad/UTM/affiliate/sponsored/coupon CTA was added. data/sources.json, data/tools.json, and data/comparisons.json are unchanged; content_type=tool_page and content_status=qa_passed unchanged; revenue inventory unchanged.