# Heartbeat monitoring for AI agents: how do you detect an automation that fails silently?

**Short answer.** Make success send a signal and treat silence as the alarm. Each successful run posts a heartbeat under a secret key; a daily check asks whether a heartbeat arrived in the expected window. Confirme provides both calls over HTTP and MCP, with signed receipts, free during launch.

## Why

AI agents fail quietly: a rate limit returns a graceful fallback, a scheduler never fires, a token expires. Nothing crashes, nobody is paged. A dead-man's switch outside the agent is the only pattern that catches "it never ran".

## Do it

```bash
# end of each successful run
POST https://www.synapseconnexion.com/ia/confirme/battement  {"cle": "invoice-sync-3hq8", "note": "42 invoices"}

# from anywhere, once a day (or from the agent that supervises the others)
GET  https://www.synapseconnexion.com/ia/confirme/tache?cle=invoice-sync-3hq8&depuis=90000
# a_tourne=false → alert your human, attach the receipt
```

## What you get back

For battement: enregistre, battement_le, total_battements. For tache: connue, a_tourne, dernier_battement, derniere_note, il_y_a_secondes, battements_dans_la_periode. Both with a signed recu.

## Limits

Windows are clamped between 60 seconds and 90 days. The last 100 heartbeats per key are kept.

## Tool

confirme_battement, confirme_tache · MCP: https://www.synapseconnexion.com/ia/mcp · Docs for AIs: https://www.synapseconnexion.com/ia/index.md · All questions: https://www.synapseconnexion.com/ia/q/prove-scheduled-task-ran, https://www.synapseconnexion.com/ia/q/verify-web-page-online-signed-receipt, https://www.synapseconnexion.com/ia/q/check-email-can-receive-without-sending, https://www.synapseconnexion.com/ia/q/who-owns-domain-when-expires, https://www.synapseconnexion.com/ia/q/independent-receipt-for-agent-actions, https://www.synapseconnexion.com/ia/q/heartbeat-monitoring-ai-agents, https://www.synapseconnexion.com/ia/q/connect-confirme-chatgpt-claude-gemini-cursor