Autonomous agents
TwinAgent is a bot that browses the web on its own to finish multi-step tasks, and its operator has not been publicly identified. TwinAgent is operated by Twin, a platform that creates automated workers to perform tasks by integrating with APIs and controlling web applications through browser automa…. 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
"TwinAgent"
Checked against
Nothing published
Live check
No operator check exists for TwinAgent. This still shows what the address really is.
Reference
| User agent | TwinAgentToken only: match on the substring. |
|---|---|
| Operator | Not publicly identified |
| Purpose | Autonomous agents |
| 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 | Not published |
| Robots.txt tokens | TwinAgent |
| Operator documentation | None published |
TwinAgent is operated by Twin, a platform that creates automated workers to perform tasks by integrating with APIs and controlling web applications through browser automa…
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: TwinAgent
Disallow: /User-agent: TwinAgent
Allow: /User-agent: TwinAgent
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking TwinAgent stops automated sessions that fill forms, click through flows and read pages the way a logged-in user would. Rate limits and challenges usually work better here than a robots.txt line.
Build a file for every crawlerFAQ
TwinAgent is a bot that browses the web on its own to finish multi-step tasks, and its operator has not been publicly identified. TwinAgent is operated by Twin, a platform that creates automated workers to perform tasks by integrating with APIs and controlling web applications through browser automa…. 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 TwinAgent 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 TwinAgent 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 TwinAgent stops automated sessions that fill forms, click through flows and read pages the way a logged-in user would. Rate limits and challenges usually work better here than a robots.txt line.