How dev.to treats AI agents

Open to agents. Last checked 25 October 2026.

dev.to is open to AI agents: no bot wall, no JavaScript needed, robots.txt restricts some paths, publishes llms.txt at /llms.txt. Agents should read /llms.txt instead of scraping.

Fact	Value	Source
Access	Open	Registry check, unverified, 25 Oct 2026
Bot wall	None	Registry check, unverified, 25 Oct 2026
JavaScript needed	No	Registry check, unverified, 25 Oct 2026
robots.txt	Restricts some paths	Registry check, unverified, 25 Oct 2026
Machine interface	llms.txt at /llms.txt	Registry check, unverified, 25 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 dev.to block AI bots?

No. dev.to is open to AI agents.

Does dev.to need JavaScript?

No. The page has real content without JavaScript.

Does dev.to have an llms.txt?

Yes, at /llms.txt.

Does dev.to use a bot wall?

No bot wall was seen.

How should an agent fetch dev.to?

Agents should read /llms.txt instead of scraping.

Use this from an agent

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