xpu liveBETA
Agents›PerplexityBot

PerplexityBot

Documented identity

PerplexityBot is listed here in the ai search category and is associated with Perplexity. Collects web information for Perplexity search discovery. This profile explains the identity and its documented scope so readers can distinguish it from a downloadable coding agent or a language model. It is an independent reference, not an operator endorsement.

What PerplexityBot does

This crawler is separate from the user-initiated Perplexity-User fetcher. A successful visit does not guarantee that an answer will cite the page.

PerplexityBot user-agent identity

The request identifier recorded for this profile is PerplexityBot. A display name, an HTTP user-agent string and a robots.txt product token can differ. Confirm the control spelling in the linked operator guidance before writing a rule. A name in a request header alone is not authentication: another client can copy it.

Search discovery and answer retrieval

Search-oriented systems discover or refresh content that may later help answer a query. A fetch, an index entry and a citation are different events. Successful HTTP delivery only confirms that a resource was served. It does not establish whether the system retained the page or selected it for a particular answer.

Evaluate search access against the content you want discoverable. Keep public reference pages readable and verify that canonical URLs and sitemaps are consistent. These practices help diagnosis, but no crawler profile can promise inclusion or ranking. Use the operator guidance to distinguish search indexing from training and user-initiated visits.

How to investigate a visit

Keep a representative log entry with the requested URL, timestamp, response code and source address. Compare it with current operator documentation and any published identity evidence. Use published IP ranges, DNS checks or request-signature verification only when the operator actually supports that method. This profile does not publish guessed address ranges or a universal allow rule.

Scope, costs and source limits

A recorded visit does not establish a model version, an API token price or a software license. These properties belong to separate products and agreements. The details below state the scope that was established for this identity; unconfirmed implementation information is identified as such. Any subscription, API or browser-service charge must be checked on the operator's current pricing pages.

PerplexityBot questions

Can I install this crawler as an agent?

This is a web-identity reference. An operator-managed crawler or fetcher is not automatically available as self-hosted software. If the operator offers a separate SDK, API or browser product, use that product's documented installation and access process rather than assuming the crawler name is an installable package.

Where should I verify the details?

Review the source documentation for PerplexityBot and the Perplexity website. For related entries, browse the XPU Live agent and crawler directory. To compare inference services separately, visit the AI provider directory.

AI Search

What it can do

  • Collects web information for Perplexity search discovery.
  • Request identity: PerplexityBot
  • Source-linked operator reference
  • Distinct category: AI Search

Where it fits

  • Search discovery and answer retrieval
  • Web traffic identification and log investigation
  • Comparing crawler and assistant roles

Models & deployment

Model compatibility

Not a standalone model endpoint. A supported model list and model-specific prices do not follow from this web identity.

Where it runs

Operated through Perplexity infrastructure or its managed services. This profile is not a self-hosted deployment recipe.

Cost model

No per-token tariff is assigned to this crawler identity. Operator services, if offered separately, have their own current access terms and pricing.

Limitations & scope

This crawler is separate from the user-initiated Perplexity-User fetcher. A successful visit does not guarantee that an answer will cite the page. User-agent matching alone does not authenticate a request. Technical behavior not confirmed in the linked sources is not asserted here.