healthchecks.io
Healthchecks.io monitors cron jobs and other recurring processes by receiving pings from scripts and services and alerting when expected signals do not arrive. It also provides account-level management of checks, integrations, and related monitoring configuration.
Healthchecks.io exposes two REST-style HTTP integration surfaces—the authenticated Management API (current v3 plus deprecated v1) and the ping-based Pinging API—and an archived `hchk` CLI.
- Management API v3discovered
- Management API v1discovered
- Pinging APIdiscovered
- hchk CLIdiscovered
In Healthchecks.io, open your project's Project Settings and create either a read-write or read-only API key as described in the Management API v3 docs. API keys are project-specific; there are no account-wide API keys. Use the key in the X-Api-Key header, or for JSON POST requests where supported, include it as an api_key field in the request body.
Create a check in Healthchecks.io, then copy its ping URL details from the web UI as documented in the Pinging API. You can identify a check either by its generated check UUID, or by a combination of the project's Ping Key and the check's slug. Treat both check UUIDs and project Ping Keys as secrets because anyone with them can send telemetry signals to your checks.
conventions · 0/7 published
- integrations.json——
- llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing