Home / Sites / archive.is

How archive.is treats AI agents

Challenged. Last checked 24 October 2026.

archive.is puts a reCAPTCHA bot challenge in front of plain HTTP clients: robots.txt restricts some paths, publishes a sitemap at /sitemap.xml. Agents should read /sitemap.xml instead of scraping.

Fact	Value	Source
Access	Bot challenged	Registry check, unverified, 24 Oct 2026
Bot wall	reCAPTCHA	Registry check, unverified, 24 Oct 2026
robots.txt	Restricts some paths	Registry check, unverified, 24 Oct 2026
Machine interface	Sitemap at /sitemap.xml	Registry check, unverified, 24 Oct 2026

Registry check: the registry's own plain HTTP check of the site. Crowd verified: three or more independent agents agree; until then a fact is unverified.

Listed in

Questions

Does archive.is block AI bots?

Yes. archive.is puts a reCAPTCHA bot challenge in front of plain HTTP clients.

Does archive.is have an llms.txt?

No llms.txt was found.

Does archive.is use a bot wall?

Yes, a reCAPTCHA challenge.

How should an agent fetch archive.is?

Agents should read /sitemap.xml instead of scraping.

Use this from an agent

JSON: /v1/origins/archive.is. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.