AgentPulse - API status & breaking-change alerts built for AI agents
by•
Humans read status pages. AI agents can't — so when an API they depend on goes down or ships a breaking change, they retry blindly, burn tokens, and guess at causes.
AgentPulse is the ground-truth layer for agents: one compact API call returns whether a service is up, degraded, or broken, and whether a breaking change affects your stack. Free tier: 100 requests/day.

p/slotify-2
p/runevr
p/producthunt
p/google-cloud-platform
p/airuncode
p/ai-context-flow
p/aperture-7
p/kodlo
p/raycast
p/lasso-11
p/kuc-kuc
p/offiai
p/dino-kids
p/supabase
p/jev
p/many-displays
p/murror
p/reso
p/dex-by-exmergo
p/htmldrag
Replies
Hey Product Hunt — I'm Akshat, a senior frontend engineer from New Jersey, and I built AgentPulse solo, on the side, because I kept seeing the same absurd loop: an autonomous agent's API dependency goes down, and the agent — having no machine-readable way to check — retries it hundreds of times, burning tokens, then confidently invents a wrong explanation.
Status pages, changelogs, and incident posts are all written for humans. AgentPulse is the same information rebuilt for the callers that actually dominate API traffic now: agents. One small JSON verdict instead of an HTML page, per-agent impact ("does this breaking change affect MY stack?"), and a playbook for the fix.
It's live today, tracking 37 services with real data only, and it's published in the official MCP Registry. The free tier (100 calls/day, 304 responses always free) is meant for agents to try with zero friction — registration is a single POST, because onboarding is the product when your users are bots.
No users yet, no hype — just a working system I'd love your feedback on. What should it track next?
🔗 Live: https://agentpulse-43di.onrender.com
💻 GitHub: https://github.com/Akshat-Srivastava-PS/AgentPulse