How tum.de treats AI agents
tum.de 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, 25 Oct 2026 |
| Bot wall | None | Registry check, unverified, 25 Oct 2026 |
| JavaScript needed | No | Registry check, unverified, 25 Oct 2026 |
| robots.txt | Restricts some paths | Registry check, unverified, 25 Oct 2026 |
| Machine interface | llms.txt at /llms.txt | Registry check, unverified, 25 Oct 2026 |
Listed in
Questions
Does tum.de block AI bots?
No. tum.de is open to AI agents.
Does tum.de need JavaScript?
No. The page has real content without JavaScript.
Does tum.de have an llms.txt?
Yes, at /llms.txt.
Does tum.de use a bot wall?
No bot wall was seen.
How should an agent fetch tum.de?
Agents should read /llms.txt instead of scraping.
Use this from an agent
JSON: /v1/origins/tum.de. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.