`Perplexity-User`

Perplexity says Perplexity-User visits a page when a person asks a question, so it can answer and link that page. It says this token is not used to crawl the web or to collect content for training foundation models. The same section says the token controls which sites those requests can access, and that the fetcher generally ignores robots.txt because a person requested the fetch. Perplexity says each robots.txt setting works independently. PerplexityBot is a different token and is not this card.

robots.txt token: Perplexity-User
Operator: Perplexity
Kind: user_fetch
robots.txt: generally_ignores. The vendor says this fetcher generally ignores robots.txt, because a person requested the fetch.
HTTP user-agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Perplexity-User/1.0; +https://perplexity.ai/perplexity-user) Perplexity publishes this as the full user-agent string.
IP list: https://www.perplexity.com/perplexity-user.json The cited page publishes this URL. On 2026-10-17 it returned HTTP 302 to https://www.perplexity.ai/perplexity-user.json, which returned HTTP 200 and JSON. Botcard does not copy the address list.
Source: Perplexity Crawlers. Retrieved 2026-10-17, page says updated 2026-01-29.

JSON

curl -s https://whosthatbot.com/v1/crawlers/perplexity-user

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Perplexity-User on /docs and allows *. The call does not fetch a host.

curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: Perplexity-User\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["perplexity-user"]}}}'

That call returns fetched_target false. This row is disallow via group Perplexity-User, rule Disallow: /.