Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Checkly Status Pages (BYOK) — connector documentation

  • MCP endpoint: https://byok-checkly-status-pages.connectorbay.com/mcp
  • REST API: POST https://byok-checkly-status-pages.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-checkly-status-pages.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Checkly Status Pages Checkly user API key, sent in the X-Upstream-Key header and the Checkly account id in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-checkly-status-pages.connectorbay.com/health · Tool schemas: https://byok-checkly-status-pages.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-checkly-status-pages · agent@connectorbay.com

What Checkly Status Pages (BYOK) is for

Checkly Status Pages (BYOK) lets an AI assistant read your own Checkly Status Pages data through the Checkly Status Pages API with a key you supply (Checkly user API key). Read-only: 6 tools (list_status_pages, get_status_page, list_components, list_incidents, list_incident_updates, list_automation_rules). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.checklyhq.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Checkly Status Pages. Checkly Status Pages and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which status pages do I have in Checkly?"
  • "Show one Checkly status page"
  • "Which components does this Checkly status page show?"
  • "What incidents happened on my Checkly status page?"
  • "What updates were posted for this Checkly incident?"
  • "Which incident automation rules does my Checkly status page have?"

What it does

  • list_status_pages: List v3 status pages with name, URL, custom domain, privacy flag and timestamps. Page with nextId.
  • get_status_page: Get one v3 status page: name, description, URL, custom domain, theme, links and privacy flag.
  • list_components: List the components (services and groups) of a status page with type, order, visibility and parent group.
  • list_incidents: List incidents of a status page with name, last update status (investigating, identified, monitoring, resolved), duration and timestamps.
  • list_incident_updates: List the updates posted for one incident: status, public text and publish time.
  • list_automation_rules: List the automation rules that open and update incidents from check results, with name, enabled flag, cool-down and timestamps.

BYOK key

You bring your own Checkly Status Pages Checkly user API key (https://app.checklyhq.com/settings/user/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.checklyhq.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Checkly Status Pages API (api.checklyhq.com) with a BYOK key; documentation: https://www.checklyhq.com/docs/api-reference/openapi.json. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Checkly Status Pages. Checkly Status Pages and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Checkly Status Pages account.

Built for: Worldwide. Languages: English.