Overview
Perplexity-User 1.0 is a historical version-specific request pattern associated with Perplexity’s user-initiated retrieval service.
The record tracks Perplexity-User/1.0 as a legacy detection variant. It should not be treated as a separate current service from the canonical Perplexity-User identity.
User-agent strings can be copied. Corroborate the request with current operator documentation, source ownership, and user-directed retrieval behavior.
Identity
- User-Agent
Perplexity-User/1.0- Aliases
- perplexity-user-1-0; Perplexity-User 1.0
- HTTP Agent Examples
Perplexity-User/1.0- Robots.txt Token
Perplexity-User/1.0- Identity Type
- Documented
- Evidence Method
- Treat `Perplexity-User/1.0` as a historical version-specific pattern of the canonical `Perplexity-User` identity and corroborate it with current operator documentation and source behavior.
Classification
- Type
- AI User Agent
- Kind
- AI User Agent
- Family
- Perplexity
- Purpose
- user-initiated-ai-fetching
Behavior and handling
- Common Use
- Historical detection of user-initiated Perplexity retrieval traffic using the version-specific `Perplexity-User/1.0` pattern.
- Detection Notes
- Do not model this legacy version string as a separate current service. Prefer the canonical `Perplexity-User` record for current policy decisions.
- Respects robots.txt
- No
- Spoofing Risk
- Perplexity-User 1.0 can be spoofed if identification relies only on a user-agent string; corroborate the request with stronger operator-controlled evidence when available.
- Risk
- Neutral
- Recommended Handling
- Monitor
Rules and controls
- Robots.txt Snippet
# Legacy or noncanonical identity. Confirm the current canonical token before relying on robots.txt.