File
SMF·PERPLEXITY
Received on
30.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·PERPLEXITY

Can a prompt replace Perplexity?

AI assistants — answer engine

Almost Verdict recorded on 28.09.2026 · Verified on 30.07.2026
Price
$20/moSource: www.perplexity.ai · Checked on July 30, 2026
Per year
$240
Build time
A week
Votes
0 votes
YesAlmost (checked)Not yet

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: search/data/model routing
Exhibit Q Questions

Verdict

A retrieval-plus-LLM answer engine — search the web, extract readable text from top results, ask a model to answer only from those excerpts with citations — is a real weekend build on top of existing search and model APIs. What doesn't come with it is Perplexity's search quality, source ranking, and the speed and polish of a dedicated product.

Exhibit B — What you lose

Exhibit A — The prompt

Received on30.07.2026
Build a personal answer engine that wraps real search and model APIs rather than reimplementing either. For each question: query a real search API (several offer a usable free tier), fetch the top handful of results, extract the readable text from each page, and pass the question plus numbered excerpts to a model (Claude or GPT, key from the environment) with strict instructions to answer only from the given excerpts and cite each claim as [1], [2], and so on. Render citations as clickable footnotes with the full source list under every answer — if a page fails to fetch or its text can't be extracted, drop it silently rather than ever citing something that wasn't actually read. Keep follow-up questions in the same thread, with prior questions and answers carried forward as context. Store threads in a database with a sidebar listing past threads by their first question.

Do not build your own web index or crawler, model routing across providers, or mobile apps — retrieval quality here tracks the search API directly, and that's the honest trade for not running Perplexity's own infrastructure.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 Perplexity's own search ranking and quality tuning
  • B.2 mobile and browser-extension surfaces
  • B.3 publisher partnerships and integrations
  • B.4 response speed at scale

Prior art

Exhibit C — Why people still pay: search/data/model routing

Answers arrive fast, with sources already assembled, and without having to build the query yourself — people pay for that speed and polish, not because retrieval-plus-LLM is a novel technique.

Questions

Can I import my Perplexity thread history?

Not in a structured way — Perplexity doesn't offer a bulk export of past threads. Anything worth keeping would need to be copied over by hand.

Will it work on my phone?

As a responsive web page, yes, if hosted somewhere reachable. There's no dedicated mobile app and no browser extension for quick lookups from other apps.

What does it cost to run?

Search API usage plus model API usage per question — most search APIs have a free tier covering light personal use, after which it's a small amount per query.

What's the one thing that doesn't survive the rebuild?

Search quality at Perplexity's level. Answers here are only as good as the underlying search API's results — Perplexity has invested specifically in ranking and source quality, which a general-purpose search API doesn't match out of the box.

Receipt

Already built this yourself?