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

Claude-Web

Anthropic · AI search crawlers · json

User-agent: Claude-Web
Disallow: /


robots.txt token	`Claude-Web`
User-agent contains	`Claude-Web`
Operator	Anthropic
Category	AI search crawlers
robots.txt	control token only — no crawler
Verify by	no published verification method

What it is

An earlier Anthropic token for user-facing web access, superseded by Claude-User and Claude-SearchBot. Kept here because it appears in most published robots.txt templates.

What blocking it costs you

None in practice. Retain the rule; expect no traffic.

Full user-agent string

Mozilla/5.0 (compatible; Claude-Web/1.0)

Allow it instead

User-agent: Claude-Web
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=claude-web&s=client-dossiers'

/tools/verification-methods?crawler=claude-web
How do I prove a request really is Claude-Web? 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://support.anthropic.com/en/articles/8896518
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-all-ai · allow-ai-search-only · maximum-ai-visibility