curl -s https://www.pathwren.workers.dev/crawler/phindbot.json   # this page, as JSON

No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a

PhindBot

Phind · AI search crawlers · json

User-agent: PhindBot
Disallow: /


robots.txt token	`PhindBot`
User-agent contains	`PhindBot`
Operator	Phind
Category	AI search crawlers
robots.txt	operator publishes no robots.txt statement
Verify by	no published verification method

What it is

Phind is an answer engine for developers that combines live web search with its own models. This is the crawler behind those answers.

What blocking it costs you

You stop being cited in answers to technical questions — which, for documentation and reference sites, is the exact audience most worth keeping.

Full user-agent string

PhindBot

Allow it instead

User-agent: PhindBot
Allow: /

Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=phindbot&s=client-dossiers'

/tools/verification-methods?crawler=phindbot
How do I prove a request really is PhindBot? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.

Operator documentation: https://www.phind.com/
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-all-ai · allow-ai-search-only · maximum-ai-visibility