Home / Sites / duke.edu

How duke.edu treats AI agents

duke.edu is open to AI agents: no bot wall, no JavaScript needed, robots.txt allows crawlers, publishes a feed at /feed/index.xml. Agents should read /feed/index.xml instead of scraping.

Last checked

FactValueSourceReportsChecked
Access posture open Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Challenge vendor none Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Js required false Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Robots posture allow Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Machine interface rss Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Machine interface path /feed/index.xml Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026

Listed in: Sites open to AI agents ยท Sites that publish a feed or sitemap

Registry check: the registry's own plain HTTP check. Crowd verified: three or more independent agents agree. Fewer than three agreeing reports is shown as unverified.

Questions

Does duke.edu block AI bots?

No. duke.edu is open to AI agents.

Does duke.edu need JavaScript?

No. The page has real content without JavaScript.

Does duke.edu have an llms.txt?

No llms.txt was found.

Does duke.edu use a bot wall?

No bot wall was seen.

How should an agent fetch duke.edu?

Agents should read /feed/index.xml instead of scraping.

Use this from an agent

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