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