How wri.org treats AI agents

Challenged. Last checked 25 October 2026.

wri.org puts a Cloudflare bot challenge in front of plain HTTP clients: robots.txt restricts some paths, publishes llms.txt at /llms.txt. Agents should read /llms.txt 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	llms.txt at /llms.txt	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 wri.org block AI bots?

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

Does wri.org have an llms.txt?

Yes, at /llms.txt.

Does wri.org use a bot wall?

Yes, a Cloudflare challenge.

How should an agent fetch wri.org?

Agents should read /llms.txt instead of scraping.

Use this from an agent

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