Copy the badge URL from a check’s detail view. Its public badge key is different from the private ping key. Publishing a badge lets anyone see that check’s status; it cannot submit pings.
[](https://cronpulse.wouldairecommend.workers.dev/?ref=badge&src=badge)<a href="https://cronpulse.wouldairecommend.workers.dev/?ref=badge&src=badge"><img src="https://cronpulse.wouldairecommend.workers.dev/b/BADGE_KEY.svg" alt="CronPulse job status"></a>States and caching
up (green), down (red), new (grey), paused (grey). New means no success has armed the check. Badges cache for 60 seconds; image proxies may cache longer.
JSON status
GET https://cronpulse.wouldairecommend.workers.dev/b/BADGE_KEY.json
{"status":"up"}The JSON route is a simple status object, not the full shields.io endpoint schema. Use the SVG for a ready-to-embed badge. Free badges say CronPulse; paid plans use cron.
Get your badge