hermes-gateway-http-limitations

Name: hermes-gateway-http-limitations
Availability: InStock
Author: huidge

Identify Hermes gateway port 8642 as WebSocket-only, not REST API.

2|2|Updated Apr 16, 2026

Search Tags:#alerting #wechat #websocket #cron #rest-api #gateway #weixin

Ready to run

npx skills add https://github.com/huidge/hermes-skills --skill hermes-gateway-http-limitations

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hermes-gateway-http-limitations
Source: https://github.com/huidge/hermes-skills/tree/main/hermes-gateway-http-limitations
Command: npx skills add https://github.com/huidge/hermes-skills --skill hermes-gateway-http-limitations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes gateway port 8642 is WebSocket-based only — NOT a REST API. Do NOT try to send WeChat/Weixin alerts via curl HTTP POST to the gateway. Understanding this prevents wasted time debugging "404 on all endpoints" when trying to send alerts from cron jobs.

Core Features & Use Cases

Clarifies that the Hermes gateway on port 8642 is WebSocket-based and not accessible via HTTP REST.
Describes the correct delivery paths for alerts (WebSocket in the gateway or using the send_message tool in an active agent session).
Provides practical use cases such as cron-triggered WeChat alerts and agent-assisted message delivery, plus fallback alert storage.

Quick Start

Use the scheduler to deliver WeChat alerts through the gateway WebSocket path instead of HTTP POST.

Frequently Asked Questions about hermes-gateway-http-limitations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why does my curl HTTP POST to the Hermes gateway return a 404 error?▼

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.

How do I send WeChat alerts from a cron job through the Hermes gateway?▼

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.

Does the Hermes gateway provide a REST API for delivering WeChat messages?▼

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.

What is the correct delivery path for WeChat alerts when HTTP POST fails?▼

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.

Can I use standard HTTP endpoints to trigger cron job alerts on the Hermes gateway?▼

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.

What are the limitations of the Hermes gateway when sending alerts?▼

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.