How wto.org treats AI agents

Challenged. Last checked 25 October 2026.

wto.org puts a Cloudflare 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, 25 Oct 2026
Bot wall	Cloudflare	Registry check, unverified, 25 Oct 2026
robots.txt	Restricts some paths	Registry check, unverified, 25 Oct 2026
Machine interface	Sitemap at /sitemap.xml	Registry check, unverified, 25 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 wto.org block AI bots?

Yes. wto.org puts a Cloudflare bot challenge in front of plain HTTP clients.

Does wto.org have an llms.txt?

No llms.txt was found.

Does wto.org use a bot wall?

Yes, a Cloudflare challenge.

How should an agent fetch wto.org?

Agents should read /sitemap.xml instead of scraping.

Use this from an agent

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