How yruz.one treats AI agents
yruz.one puts a Cloudflare bot challenge in front of plain HTTP clients: robots.txt restricts some paths, publishes llms.txt at /llms.txt. Agents should read /llms.txt instead of scraping.
| Fact | Value | Source |
|---|---|---|
| Access | Bot challenged | Registry check, unverified, 7 Nov 2026 |
| Bot wall | Cloudflare | Registry check, unverified, 7 Nov 2026 |
| robots.txt | Restricts some paths | 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 |
| API catalog | /.well-known/api-catalog | Registry check, unverified, 7 Nov 2026 |
Listed in
Questions
Does yruz.one block AI bots?
Yes. yruz.one puts a Cloudflare bot challenge in front of plain HTTP clients.
Does yruz.one have an llms.txt?
Yes, at /llms.txt.
Does yruz.one use a bot wall?
Yes, a Cloudflare challenge.
How should an agent fetch yruz.one?
Agents should read /llms.txt instead of scraping.
Use this from an agent
JSON: /v1/origins/yruz.one. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.