Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

OpenAI-Compatible API

4.6. OpenAI-Compatible API — Calling Hermes as a Model Backend

Role

Hermes can run a local HTTP server following the OpenAI-compatible standard, letting third-party applications and tools (which only know how to call an OpenAI-style API) connect to Hermes as if it were an ordinary model endpoint.

A practical use — the Subscription Proxy

One noteworthy use: this server can forward requests to an upstream provider already authenticated via OAuth (such as Nous Portal or xAI) — the external application only needs to point at the proxy with any bearer token, while the proxy attaches the real OAuth credentials when sending. This lets you use an existing subscription (instead of a usage-based API key) with tools that only support a direct API key.

Notes

  • This is a useful doorway when you want to use Hermes (or the model behind it) from tools that do not support MCP/ACP but do support an OpenAI-style endpoint — extending the integration surface beyond the Hermes-native ecosystem.
  • Exactly per the firewall principle in 1.4/2.3: only open this API port when a client truly needs it, and keep it inside your Tailscale network rather than exposing it on 0.0.0.0 unless public internet access is truly required.
  • For managing multiple rotating keys for the same provider (to avoid rate limits), Hermes has its own credential pool mechanism — worth a look if this API server will serve a high call volume.