What is Retool?
Retool is the platform user agent attached to outbound HTTP requests from Retool. The known pattern is Retool/, and Cloudflare's bot directory records the full example as Retool/2.0 (+https://docs.tryretool.com/docs/apis). Retool has also described this value as a hardcoded header added before a request is sent.
The header does not identify one fixed job. A Retool app or workflow can call an external HTTP endpoint for a task configured by the team that built it. The URL, method, frequency, credentials, and expected response all depend on that configuration, so two Retool requests can have unrelated purposes.
A server log entry therefore means that Retool's platform claims to have made an HTTP call. It does not mean Retool is crawling the surrounding website or discovering links. Start with the requested endpoint and the owning integration when investigating why the traffic exists.
This user agent has no direct effect on AI search visibility. It does not index pages for an answer engine, and the available operator description gives it no model-training role. Blocking it can break a Retool integration that calls your service, but it does not opt a site out of search results or training data.
The robots status is not confirmed in the bot metadata. Cloudflare's entry marks Retool as not following robots.txt, even though the Retool token is stable enough to write a group for it. Use that group only to express a preference; secure an API with authentication and enforce denials in the application or at the edge.
Cloudflare categorizes this identity as a bot and links to Retool's API documentation. It provides no signature directory, and there is no verified IP identity in the record. The cataloged agent is verified, but the header on an individual request is not proof that Retool sent it because any HTTP client can reproduce the string.
