How vaults.fyi treats AI agents
vaults.fyi puts a Cloudflare bot challenge in front of plain HTTP clients: robots.txt allows crawlers, 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 | 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 |
| MCP server card | /.well-known/mcp/server-card.json | Registry check, unverified, 7 Nov 2026 |
| API catalog | /.well-known/api-catalog | Registry check, unverified, 7 Nov 2026 |
| API host | api.vaults.fyi | Registry check, unverified, 7 Nov 2026 |
Listed in
Questions
Does vaults.fyi block AI bots?
Yes. vaults.fyi puts a Cloudflare bot challenge in front of plain HTTP clients.
Does vaults.fyi have an llms.txt?
Yes, at /llms.txt.
Does vaults.fyi use a bot wall?
Yes, a Cloudflare challenge.
How should an agent fetch vaults.fyi?
Agents should read /llms.txt instead of scraping.
Use this from an agent
JSON: /v1/origins/vaults.fyi. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.