curl -s https://www.pathwren.workers.dev/crawler/shapbot.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

ShapBot

Parallel · AI search crawlers · json

User-agent: ShapBot
Disallow: /


robots.txt token	`ShapBot`
User-agent contains	`ShapBot`
Operator	Parallel
Category	AI search crawlers
robots.txt	obeys robots.txt (documented)
Verify by	no published verification method

What it is

Parallel's crawler. It collects and structures web content to power the search, extraction and deep-research APIs that Parallel sells to agent builders.

What blocking it costs you

Agents using Parallel's research API lose you as a source. Parallel documents robots.txt compliance, so a rule works.

Full user-agent string

ShapBot

Allow it instead

User-agent: ShapBot
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=shapbot&s=client-dossiers'

/tools/verification-methods?crawler=shapbot
How do I prove a request really is ShapBot? 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://docs.parallel.ai/features/crawler
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-all-ai · allow-ai-search-only · maximum-ai-visibility