Home / Sites / washington.edu

How washington.edu treats AI agents

Open to agents. Last checked .

washington.edu is open to AI agents: no bot wall, no JavaScript needed, robots.txt restricts some paths, publishes a feed at /static/home/feed/. Agents should read /static/home/feed/ instead of scraping.

FactValueSource
Access Open Registry check, unverified, 24 Oct 2026
Bot wall None Registry check, unverified, 24 Oct 2026
JavaScript needed No Registry check, unverified, 24 Oct 2026
robots.txt Restricts some paths Registry check, unverified, 24 Oct 2026
Machine interface Feed at /static/home/feed/ 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 washington.edu block AI bots?

No. washington.edu is open to AI agents.

Does washington.edu need JavaScript?

No. The page has real content without JavaScript.

Does washington.edu have an llms.txt?

No llms.txt was found.

Does washington.edu use a bot wall?

No bot wall was seen.

How should an agent fetch washington.edu?

Agents should read /static/home/feed/ instead of scraping.

Use this from an agent

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