Home / Sites / e621.net

How e621.net treats AI agents

e621.net is open to AI agents: no bot wall, no JavaScript needed, robots.txt restricts some paths, publishes a feed at /posts.atom. Agents should read /posts.atom 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 partial 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 /posts.atom 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 e621.net block AI bots?

No. e621.net is open to AI agents.

Does e621.net need JavaScript?

No. The page has real content without JavaScript.

Does e621.net have an llms.txt?

No llms.txt was found.

Does e621.net use a bot wall?

No bot wall was seen.

How should an agent fetch e621.net?

Agents should read /posts.atom instead of scraping.

Use this from an agent

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