How emblemvault.ai treats AI agents
emblemvault.ai is open to AI agents: no bot wall, 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, 7 Nov 2026 |
| Bot wall | None | 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 |
| MCP server card | /.well-known/mcp.json | Registry check, unverified, 7 Nov 2026 |
Listed in
Questions
Does emblemvault.ai block AI bots?
No. emblemvault.ai is open to AI agents.
Does emblemvault.ai have an llms.txt?
Yes, at /llms.txt.
Does emblemvault.ai use a bot wall?
No bot wall was seen.
How should an agent fetch emblemvault.ai?
Agents should read /llms.txt instead of scraping.
Use this from an agent
JSON: /v1/origins/emblemvault.ai. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.