Developer Docs

Wire your agent to Encrypted Energy uptime monitoring. One endpoint, one bearer token, no SDK required. New to OpenClaw? Start at the project repo.

Quick Start

1. Sign up and register your first agent. We'll mint a bearer token tied to it.

2. Schedule a one-minute cron that runs the skill's ping.sh with ENCRYPTED_ENERGY_API_KEY in its env. The agent's show page generates a copy-pasteable crontab one-liner with your token pre-filled — easiest path.

3. Install the encryptedenergy-uptime skill, or POST your /health payload directly to /api/v1/ping on your own schedule.

$ openclaw skills install encryptedenergy-uptime

4. Watch your status page at /agent/:slug. Configure email alerts and the down threshold from the agent settings.

Authentication

Pings are authenticated by a per-agent bearer token:

Authorization: Bearer ee_agent_abc123...

Tokens start with ee_agent_ and are unique to a single agent. Find them on the agent's show page or rotate them at any time. The token can also be passed as a token query/body param if Authorization headers aren't available.

Ping Endpoint

The only endpoint you need to integrate. Call it as often as you like — every minute is typical.

POST /api/v1/ping

Record a heartbeat. Marks the agent up, records the payload, and closes any open incident. The body should be the JSON from your gateway's /health endpoint, but any JSON object works.

Request Body (example /health payload) 
{
  "ok": true,
  "version": "2026.4.24",
  "durationMs": 12,
  "channels": { "telegram": "connected", "discord": "disconnected" },
  "tasks": { "pending": 0, "failed": 0, "lost": 0, "timedOut": 0 },
  "tokenUsage": { "input": 412034, "output": 89221 }
}

Recognized fields: ok (boolean — defaults to true if omitted), version or runtime.version (shown on the status page). Everything else is stored verbatim and surfaced on the agent dashboard.

Response 200 
{
  "status": "ok",
  "agent_slug": "neo-prod",
  "received_at": "2026-04-26T22:13:44Z",
  "previous_status": "up"
}
Errors 
401  { "error": "Invalid agent token" }
422  { "error": "<validation messages>" }
Example: cURL 
# Pipe your gateway's /health straight into a ping
curl -s http://127.0.0.1:18789/health | \
  curl -X POST https://encryptedenergy.com/api/v1/ping \
    -H "Authorization: Bearer $ENCRYPTED_ENERGY_API_KEY" \
    -H "Content-Type: application/json" \
    --data-binary @-
How down detection works
  • A background job runs every minute and checks every agent.
  • If last_ping_at is older than the agent's down_threshold_seconds (default 600), the agent flips to down.
  • An Incident is created and an email is sent to the alert address (if email alerts are on).
  • The next successful ping flips the agent back to up, closes the incident, and sends a recovery email.
Public Status Page

Every agent gets a public URL — paste it on your docs site or your README:

https://encryptedenergy.com/agent/<slug>

Shows live status, 24h/7d/30d uptime, and incident history. Toggle public_listing off in agent settings to make it private.

Questions? Contact us

Start Monitoring →