Install the Checkly CLI: npm install -g checkly; run checkly login to authenticate with your Checkly account
Initialize a new project with checkly create and choose a template; the CLI scaffolds a checkly.config.ts file and an example check definition
Define API checks using the ApiCheck class: specify a name, frequency (e.g., Frequency.EVERY_1M), request method and URL, and an assertions array using AssertionBuilder helpers
Define browser checks using the BrowserCheck class, pointing to a Playwright test file; the check runs your Playwright script on Checkly's global infrastructure
Run checkly test --record to execute checks against your Checkly account and record results; use checkly deploy to publish the configuration to production monitoring
Add checks to alert channels (Slack, PagerDuty, email) by defining alert channel resources in your config and referencing them from check alertChannels arrays
Known gotchas
Checkly CLI uses a monitoring-as-code model where the config is the source of truth; checks created manually in the UI will be overwritten by the next checkly deploy if not reflected in code
Browser check scripts must be self-contained Playwright test files; they run in Checkly's sandboxed environment, which may have slightly different browser versions than your local Playwright install
Frequency options are predefined constants (e.g., Frequency.EVERY_1M, Frequency.EVERY_10M); you cannot set arbitrary intervals outside the supported set
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp