hermes-gateway-http-limitations

Your curl HTTP POST fails because the Hermes gateway on port 8642 is strictly WebSocket-based and does not expose a REST API. You must route messages through the WebSocket connection or the agent's send_message tool instead of HTTP endpoints.

To send WeChat alerts from a cron job, use the scheduler to deliver messages via the gateway's WebSocket path. The Hermes gateway does not support HTTP REST requests, so direct HTTP POST calls from cron will fail.

No, the Hermes gateway does not provide a REST API for WeChat message delivery. Port 8642 is WebSocket-based only, meaning all alerts and messages must traverse the gateway through the WebSocket protocol or an active agent's send_message tool.

The correct delivery path for WeChat alerts is through the gateway's WebSocket connection or by using the send_message tool within an active agent session. HTTP POST requests are unsupported and will fail, with fallback alert storage available as a contingency.

No, you cannot use standard HTTP endpoints to trigger cron job alerts on the Hermes gateway. The gateway operates exclusively on WebSocket, requiring you to configure the scheduler to deliver alerts via WebSocket rather than attempting HTTP POST requests.

The primary limitation of the Hermes gateway is that port 8642 supports WebSocket only and rejects HTTP POST requests. Alert delivery for WeChat and cron workflows must bypass REST and use the WebSocket path or the agent's integrated send_message tool.