xpu liveBETA
Agents›Perplexity-User

Perplexity-User

Documented identity

Perplexity-User is listed here in the ai assistants category and is associated with Perplexity. Fetches pages in connection with Perplexity user requests. 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 Perplexity-User does

Separate user-driven retrieval from PerplexityBot indexing. Review the operator documentation for the different access and robots.txt behavior.

Perplexity-User user-agent identity

The request identifier recorded for this profile is Perplexity-User. 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.

User-directed web retrieval

A person asks an assistant to inspect a page or obtain information. The resulting fetch can be limited to a particular URL rather than a broad indexing pass. When investigating a request, preserve its time, requested path and response status. A fetch does not by itself tell you which answer the user received.

Compare user-directed retrieval with automatic collection before making a site-access decision. An assistant may need the content now, while a crawler may revisit it on its own schedule. Keep these activities separate in reporting; neither a successful fetch nor a quoted link proves that the page was used for model training.

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.

Perplexity-User 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 Perplexity-User 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 Assistants

What it can do

  • Fetches pages in connection with Perplexity user requests.
  • Request identity: Perplexity-User
  • Source-linked operator reference
  • Distinct category: AI Assistants

Where it fits

  • User-directed web 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

Separate user-driven retrieval from PerplexityBot indexing. Review the operator documentation for the different access and robots.txt behavior. User-agent matching alone does not authenticate a request. Technical behavior not confirmed in the linked sources is not asserted here.