Pulse catches a dead agent before your customers do.
A web service crashes loudly. An agent just stops firing, or returns the wrong answer with the same confidence as the right one. Pulse watches the agent itself: heartbeats, full run traces, and an alert path your on-call actually respects.
heartbeats
Tell AgentPing the schedule each agent should keep. Miss a window and you get paged in seconds, with the last good run and what was meant to happen already attached. Heartbeats are for agents on a schedule; request-driven agents get the same watch through traces and alerts.
alerting
Set rules for what matters: an agent goes quiet, runs start failing, health drops, quality drops, or spending runs hot. AgentPing opens one issue and tells you once. While it stays open it does not page you again; when it clears, you get a single all-clear. Reminders only if you haven't acknowledged. We page you, we don't spam you.
traces
Every run records its tool calls, timings, the model used, and the output it produced. When one agent hands off to another, the trace follows, so a multi-step failure is one story, not five disconnected logs.
alerting
When a run fails or a scheduled agent goes silent, the alert lands in the channel your team already lives in, with the error and the last good run attached. No new dashboard to babysit.
status pages
A public, link-shareable status page for the agents you run: operational, degraded, or down, with 90 days of history per agent. The states come from real runs, the same signal that pages your on-call, so you never declare an incident by hand. Your client sees their agents are healthy without a seat in your dashboard.
Everything you need to trust that the agents you shipped are still running, and to find out first when they are not.
traces
Follow the thread when one agent kicks off another, so a five-step failure is one trace to read, not five logs to correlate by hand.
sharing
A public page showing each agent operational, degraded, or down with 90 days of history. States, never data, so nothing sensitive can leak.
detail
Every tool call, timing, and output captured, so a slow run is a known quantity.
status
Every run lands as success, failed, timeout, or cancelled, so a bad deploy shows up immediately.
coverage
One curl monitors cron, n8n, GitHub Actions, or Claude Routines. If it can curl, it counts.
safety
Hard 2-second timeout, bounded queue. If we go down, your agent runs as if we were not there.
Schedules and heartbeats turn "I think it is fine" into a green tick or a page.
Step through the run, read the tool calls, find the exact step that went wrong.
Failures route to the channel your on-call already trusts.
Pulse catches a dead agent before your customers do. Two lines of code, or one curl. Live in minutes, free to start, 14-day trial on paid plans.
Free to start. No card. The SDK never blocks your agents.