Other automated crawlers
Poseidon Research Crawler is a bot operated by Poseidon Research that crawls the web automatically. Lab focused on scaling the interpretability research necessary to make better AI systems possible. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Request says
"Poseidon Research Crawler"
Checked against
Nothing published
Live check
No operator check exists for Poseidon Research Crawler. This still shows what the address really is.
Reference
| User agent | Poseidon Research CrawlerToken only: match on the substring. |
|---|---|
| Operator | Poseidon Research |
| Purpose | AI research crawler |
| Respects robots.txt | No policy |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | No explicit frequency provided. |
| Robots.txt tokens | Poseidon Research Crawler |
| Operator documentation | None published |
Lab focused on scaling the interpretability research necessary to make better AI systems possible.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: Poseidon Research Crawler
Disallow: /User-agent: Poseidon Research Crawler
Allow: /User-agent: Poseidon Research Crawler
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking Poseidon Research Crawler stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.
Build a file for every crawlerFAQ
Poseidon Research Crawler is a bot operated by Poseidon Research that crawls the web automatically. Lab focused on scaling the interpretability research necessary to make better AI systems possible. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Not documented. No operator statement says whether Poseidon Research Crawler reads robots.txt, so add the rule but verify in your logs that the requests actually stop.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the Poseidon Research Crawler token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking Poseidon Research Crawler stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.