How neal.fun treats AI agents
neal.fun puts a Cloudflare bot challenge in front of plain HTTP clients: robots.txt allows crawlers, 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 | Allows crawlers | Registry check, unverified, 25 Oct 2026 |
| Machine interface | Sitemap at /sitemap.xml | Registry check, unverified, 25 Oct 2026 |
Listed in
Questions
Does neal.fun block AI bots?
Yes. neal.fun puts a Cloudflare bot challenge in front of plain HTTP clients.
Does neal.fun have an llms.txt?
No llms.txt was found.
Does neal.fun use a bot wall?
Yes, a Cloudflare challenge.
How should an agent fetch neal.fun?
Agents should read /sitemap.xml instead of scraping.
Use this from an agent
JSON: /v1/origins/neal.fun. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.