HTTP API · operational

Checkly API

Run and manage browser tests and synthetic API monitors from an agent, with results, locations and runtimes exposed over REST.

Checkly runs Playwright-based browser checks and API checks from 20+ locations and exposes everything over a REST API: create checks, trigger runs, read results, list runtimes and locations. The runtimes and locations endpoints answer without a key, the rest needs a personal API key plus account id headers. Useful for agents that need a second, independent browser-testing interface next to Playwright MCP and Browserless.

endpoint: https://api.checklyhq.com/v1/runtimes
auth: api_key
try it: tested example call
curl -s https://api.checklyhq.com/v1/runtimes
capabilities: run a browser test · run an api check · read test results · list check runtimes · synthetic monitoring
tags: test · testing · browser · monitoring · automation · playwright
pricing: Free tier with 10k check runs per month, paid plans above.
i/o: HTTP GET/POST with JSON body; Authorization: Bearer <api key> and X-Checkly-Account headers for account scoped routes → JSON
docs: https://developers.checklyhq.com/reference/getv1runtimes
machine-readable: /api/public/registry/checkly-api

Get a key in one call

No account, no email, no dashboard

100 calls/day anonymous · 1,000/day with this free key · 50,000/day on Agent Pro. The key is returned instantly in the response — send it as the x-api-key header on any /api/public/* request.

tested example call

curl -s -X POST https://agentnexus.app/api/public/keys \
  -H 'content-type: application/json' \
  -d '{"agent":"my-agent","purpose":"tool discovery"}'

Use it from your agent

Point any MCP-capable agent (Claude, Cursor, your own) at the no-auth endpoint — it can then find Checkly API and every other listed interface on its own:

tested example call

claude mcp add --transport http agent-nexus https://agentnexus.app/api/public/mcp

Agents can discover Checkly API through the Agent Nexus MCP server, /llms.txt or the discovery API.