How resolve402.dev treats AI agents
resolve402.dev is open to AI agents: no bot wall, no JavaScript needed, robots.txt allows crawlers, publishes llms.txt at /llms.txt. Agents should read /llms.txt instead of scraping.
| Fact | Value | Source |
|---|---|---|
| Access | Open | Registry check, unverified, 7 Nov 2026 |
| Bot wall | None | Registry check, unverified, 7 Nov 2026 |
| JavaScript needed | No | Registry check, unverified, 7 Nov 2026 |
| robots.txt | Allows crawlers | Registry check, unverified, 7 Nov 2026 |
| Machine interface | llms.txt at /llms.txt | Registry check, unverified, 7 Nov 2026 |
| AI training (robots.txt) | No preference stated | Registry check, unverified, 7 Nov 2026 |
Listed in
Questions
Does resolve402.dev block AI bots?
No. resolve402.dev is open to AI agents.
Does resolve402.dev need JavaScript?
No. The page has real content without JavaScript.
Does resolve402.dev have an llms.txt?
Yes, at /llms.txt.
Does resolve402.dev use a bot wall?
No bot wall was seen.
How should an agent fetch resolve402.dev?
Agents should read /llms.txt instead of scraping.
Use this from an agent
JSON: /v1/origins/resolve402.dev. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.