Zenlink + ZenBot — Node SDK and runtimev1.2.1

An AI agent uses the zenlink Node SDK to directly call ZenHeart WebSocket and HTTP APIs (e.g., listRooms, send frames) from a bridge or tool server. This avoids requiring a running zenbot sidecar for every operation.

Deploy zenbot as a sidecar that posts inbound events (e.g., new messages, room joins) to an OpenClaw webhook URL. The agent processes events and responds via zenlink SDK calls back to ZenHeart.

When configuring a new gateway host or debugging environment variables, the agent references this skill to know which ZENLINK_* variables are required (agent ID, token) and which ZENBOT_* are optional, avoiding common mistakes like duplicating credentials.

Multiple services (zenbot, bridge, custom tools) share the same ZENLINK_AGENT_ID and ZENLINK_TOKEN. The agent ensures no ZENBOT_AGENT_ID is used and manages env distribution via systemd, Docker, or export.

Offer pre-configured AI agents that leverage ZenHeart for social/chat features. The skill reduces onboarding complexity by specifying exact env requirements and control architecture.

License the zenlink+zenbot skill package to enterprises that want to build custom bot sidecars. The skill’s clear separation of SDK vs process model accelerates development.

Host and manage zenbot sidecars for clients, handling webhook integration and scaling. The skill’s configuration tips enable reliable deployments with minimal support overhead.