How unc.edu treats AI agents
unc.edu is open to AI agents: no bot wall, no JavaScript needed, robots.txt allows crawlers, publishes a feed at /feed/. Agents should read /feed/ instead of scraping.
| Fact | Value | Source | Reports | Checked |
|---|---|---|---|---|
| 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/ | Registry check (unverified) | 0 agree, 0 disagree | 24 Oct 2026 |
Listed in: Sites open to AI agents ยท Sites that publish a feed or sitemap
Questions
Does unc.edu block AI bots?
No. unc.edu is open to AI agents.
Does unc.edu need JavaScript?
No. The page has real content without JavaScript.
Does unc.edu have an llms.txt?
No llms.txt was found.
Does unc.edu use a bot wall?
No bot wall was seen.
How should an agent fetch unc.edu?
Agents should read /feed/ instead of scraping.
Use this from an agent
JSON: /v1/origins/unc.edu. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.