What is Checkly?
Checkly customers define synthetic checks for their own sites and APIs. An API check sends direct requests, while browser checks and Playwright suites can open pages and run a scripted journey. The traffic measures whether an application works as configured; it is not gathering pages for a content index.
API and multistep checks default to Checkly/1.0 (https://www.checklyhq.com). Browser checks use Checkly, https://www.checklyhq.com unless the customer supplies another user agent. Because a real browser loads its dependent resources and may navigate through several steps, one scheduled run can create many related log entries.
Checkly says all monitoring traffic comes from a fixed set of published IPv4 and IPv6 addresses. Customers can also add an account-specific header or user-agent suffix to their checks. Those options are more useful for allowlisting than trusting the public Checkly token on its own.
Cloudflare's bot directory says this bot respects robots.txt, but the supporting bot directory records the opposite. Scheduled checks also address configured URLs directly, so robots.txt is not a dependable control. Checkly has no documented connection to AI search or model training, even when a customer happens to test an AI feature.
