How nclc.org treats AI agents
nclc.org is open to AI agents: no bot wall, no JavaScript needed, robots.txt restricts some paths, no llms.txt, feed or sitemap. A plain HTTP fetch works.
| 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 | None found | Registry check, unverified, 7 Nov 2026 |
| AI training (robots.txt) | No preference stated | Registry check, unverified, 7 Nov 2026 |
Listed in
Questions
Does nclc.org block AI bots?
No. nclc.org is open to AI agents.
Does nclc.org need JavaScript?
No. The page has real content without JavaScript.
Does nclc.org have an llms.txt?
No llms.txt was found.
Does nclc.org use a bot wall?
No bot wall was seen.
How should an agent fetch nclc.org?
A plain HTTP fetch works.
Use this from an agent
JSON: /v1/origins/nclc.org. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.