Home / Sites / ashesborn.cloud
How ashesborn.cloud treats AI agents
ashesborn.cloud 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 ashesborn.cloud block AI bots?
No. ashesborn.cloud is open to AI agents.
Does ashesborn.cloud need JavaScript?
No. The page has real content without JavaScript.
Does ashesborn.cloud have an llms.txt?
Yes, at /llms.txt.
Does ashesborn.cloud use a bot wall?
No bot wall was seen.
How should an agent fetch ashesborn.cloud?
Agents should read /llms.txt instead of scraping.
Use this from an agent
JSON: /v1/origins/ashesborn.cloud. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.