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

archive.org_bot

Internet Archive · Archivers · json

User-agent: archive.org_bot
Disallow: /


robots.txt token	`archive.org_bot`
User-agent contains	`archive.org_bot`
Operator	Internet Archive
Category	Archivers
robots.txt	obeys robots.txt (documented)
Verify by	no published verification method

What it is

The Wayback Machine's crawler. Preservation rather than AI, but it lands in the same 'is this bot welcome' decision and its output is a public corpus.

What blocking it costs you

Your site stops being preserved. When it dies, it is gone. Consider this one separately from the AI question.

Full user-agent string

Mozilla/5.0 (compatible; archive.org_bot +http://archive.org/details/archive.org_bot)

Allow it instead

User-agent: archive.org_bot
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=archive-org-bot&s=client-dossiers'

/tools/verification-methods?crawler=archive-org-bot
How do I prove a request really is archive.org_bot? 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://archive.org/details/archive.org_bot
Machine copies: json · markdown
Policies that name this crawler: allow-all · maximum-ai-visibility