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

ia_archiver

Internet Archive · Archivers · json

User-agent: ia_archiver
Disallow: /


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

What it is

The legacy Alexa/Internet Archive token, still present in most robots.txt files and still occasionally honoured.

What blocking it costs you

Negligible today; retain for tidiness.

Full user-agent string

ia_archiver (+http://www.alexa.com/site/help/webmasters; crawler@alexa.com)

Allow it instead

User-agent: ia_archiver
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=ia-archiver&s=client-dossiers'

/tools/verification-methods?crawler=ia-archiver
How do I prove a request really is ia_archiver? 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