Integration Guide
Hermes Agent + 9Router: One Local Gateway for Multiple Providers
9Router exposes a local OpenAI-compatible API and can route requests across connected providers, aliases, and fallback combinations. Hermes Agent can consume that endpoint like another model provider, but the network and credential boundary must be configured carefully.
How the connection works
9Router runs as a gateway between clients and upstream model providers. Its documented local API is OpenAI-compatible and commonly listens at http://127.0.0.1:20128/v1. Hermes Agent sends requests to that base URL; 9Router selects an account, model, alias, or fallback combo and translates the request when needed.
Hermes Agent -> http://127.0.0.1:20128/v1 -> 9Router -> providerDeploy a managed Hermes Agent and, on a paid plan, add 9Router as a Custom API Provider on the API Keys page. A hosted bot cannot reach localhost or a private tunnel, so expose 9Router at a public HTTPS URL with endpoint API-key enforcement first.
Install and secure 9Router
- Install 9Router from its official repository or package instructions.
- Replace the default first-login password before connecting accounts.
- Enable endpoint API-key enforcement.
- Keep it on localhost, a private Docker network, or a private tunnel whenever possible.
- Connect only providers whose terms permit your intended workflow.
Configure the Hermes provider
In Hermes Agent, add an OpenAI-compatible provider using the 9Router base URL, the API key copied from its dashboard, and the exact model or combo ID shown by 9Router. If Hermes and 9Router run in different containers, 127.0.0.1 points to the wrong container; use a private service name or network address instead.
On a paid OpenClaw Launch plan, open the API Keys page, use the Custom API Provider card, and enter 9Router's public HTTPS base URL and its endpoint key, then pick a model or combo ID it exposes. Keep API-key enforcement on: a public URL without it is an open proxy to your provider accounts.
When 9Router is useful
- Fallback: move to another approved model when a provider is unavailable.
- Aliases: give Hermes Agent a stable model name while changing the route behind it.
- Usage visibility: inspect request and cost records in one dashboard.
- Format translation: bridge compatible request formats when supported.
When to keep the setup simpler
If you only use one provider, a direct BYOK connection has fewer moving parts and a smaller credential surface. Add 9Router because you need routing, visibility, or fallback—not because an extra proxy automatically improves answer quality.
OpenClaw Launch manages the Hermes Agent service itself. A private 9Router deployment remains your responsibility, including its updates, provider accounts, security, and compliance.
Hermes Agent and 9Router FAQ
Can Hermes Agent connect to 9Router?
Yes. 9Router exposes an OpenAI-compatible endpoint, and its release notes include a Hermes preset. Use the endpoint and key generated by your own 9Router installation.
Should 9Router be exposed publicly?
Prefer a private network or same-host connection. If it must be internet-accessible, enable API-key enforcement, HTTPS, firewall rules, and a strong dashboard password.
Does 9Router make model usage free?
No guarantee. Costs and terms depend on each connected provider or subscription. Review provider policies before routing subscription credentials.