Hermes Bridge API provides a straightforward interface for interacting with Hermes agents via REST and Server-Sent Events. Designed for the Agentfy app, this bridge offers versatile features like session persistence, skill management, and device pairing, making it an essential tool for developers integrating AI capabilities into mobile applications.
The Hermes Bridge API serves as a lightweight REST + SSE bridge that connects Hermes Agent to mobile applications and HTTP clients. Designed with compatibility in mind, it operates efficiently alongside Agentfy, an iOS application, and is provider-agnostic, eliminating the need for complex WebSocket or custom handshake processes.
~/.hermes/skills/, and attach or detach skills to agents with ease.~/.hermes/.env, keeping sensitive information hidden from mobile clients.To utilize the Hermes Bridge API, ensure the following:
~/.hermes/hermes-agent, which will be imported at runtime.Establishing the bridge is straightforward. The repository provides an installation script that checks for your Hermes setup and installs the necessary components:
git clone https://github.com/jcnh74/hermes-bridge.git
cd hermes-bridge
./install.sh
To verify the setup, use the command:
hermes-bridge doctor
To start the Hermes Bridge API, perform:
hermes-bridge start
The API responds on the route http://localhost:8765/api/v1, providing health checks and status updates on the agents.
Some key API endpoints include:
GET /health - Returns the health status of the API and feature flags.GET /agents - List all available Hermes agents, while POST /agents creates new agents.POST /sessions establishes a session with an agent, enabling real-time message exchanges.In Agentfy, establish a connection to the bridge API by either using the API URL directly or leveraging a QR code for quick pairing. Ensure proper tunneling or proxy setup if accessing it over the internet to maintain security and integrity.
The architecture of the Hermes Bridge integrates seamlessly with existing Hermes installations, maintaining shared configurations and data. By adhering to this design, the API inherits the robust pipeline of the Hermes Agent, ensuring consistent functionality and performance without including Hermes resources directly.
Given the sensitive nature of API interactions, it is recommended to keep API keys stored securely within the ~/.hermes/.env directory. When deploying the Hermes Bridge, avoid direct exposure to the public internet and instead leverage authenticated tunnels or reverse proxies for secure access.
No comments yet.
Sign in to be the first to comment.