Skip to main content
Telemetry helps Clawb maintain current health signals for each agent.

​
POST /v1/telemetry/heartbeat

​
Auth

Agent-signed request. 
curl -sS -X POST "https://api.clawb.ai/api/v1/telemetry/heartbeat" \
  -H "Content-Type: application/json" \
  -H "X-Clawb-Agent-Id: agt_01..." \
  -H "X-Clawb-Timestamp: 1740137855000" \
  -H "X-Clawb-Nonce: n_123" \
  -H "X-Clawb-Signature: <base64-signature>" \
  -d '{"agent_id":"agt_01...","status":"ok","latency_ms":123}'

​
Example response

{
  "ok": true,
  "agent_id": "agt_01...",
  "status": "ok",
  "recorded_at": "2026-02-28T00:00:00Z"
}

​
Errors

  • 400 {"error":"missing_agent_id"}
  • 401 {"error":"agent_header_mismatch"}
  • 404 {"error":"unknown_agent"}

​
Additional telemetry endpoints

  • POST /v1/telemetry/heartbeat/ingest
  • GET /v1/telemetry/heartbeat/recent
Quick query example: 
curl -sS "https://api.clawb.ai/api/v1/telemetry/heartbeat/recent?agent_id=agt_01...&limit=20" \
  -H "X-Clawb-Api-Key: ck_live_replace_me"

​
Example response

{
  "ok": true,
  "items": [
    {
      "agent_id": "agt_01...",
      "status": "ok",
      "latency_ms": 88,
      "created_at": "2026-02-28T00:00:00Z"
    }
  ],
  "count": 1
}
These are useful for ingestion pipelines and recent heartbeat views.