WorldEye in Perplexity: Cited, Not Connected — and Why That's Fine

Perplexity is an answer engine: it searches the web, reads what it finds, and writes an answer with numbered citations. There is no app directory, no connector gallery and no submission path for a data provider to plug live tools into a Perplexity answer. Perplexity's own API, Sonar, runs the other direction — it lets developers put Perplexity inside their products. Its Publisher Program is a revenue arrangement for news publishers, not an integration channel. Anyone selling a “Perplexity integration” for a site like ours is selling something that does not exist, and this post is not going to pretend we bought it.

What does exist is the citation. Perplexity's crawler, PerplexityBot, can read worldeye.app freely, and the pages are built to survive being quoted: every statistic carries its measure and its date, the headline camera count is stated exactly — 74,229 cameras served — and larger catalogue totals elsewhere are labelled as the different measures they are rather than blended into a bigger number. Each topic lives on its own page with a single clear claim, which is the shape an answer engine can lift without mangling it.

That discipline is the whole strategy, and it is measurable in the answers themselves: when Perplexity answers a question about live volcano webcams, a place's cameras, or today's earthquakes with a worldeye.app source in its numbered list, the citation is doing the work a connector would do elsewhere. Our WorldEye in Perplexity page keeps the details and the example questions current.

There is nothing to install and nothing to pay for. Ask Perplexity a question WorldEye is genuinely the best source for — a live camera for a specific place, the current state of an erupting volcano, the strongest earthquakes today — and check the numbered sources under the answer. A worldeye.app link opens the live globe, where browsing is free and unlimited camera opens need an upgrade. And if you build software and want the data programmatically, that path is real too: it is our developer API and MCP server, called from your own code — just not a Perplexity feature.