Skip to main content
Hermes can call the Toolken gateway as its LLM backend. However, Hermes does not attach custom headers to outbound requests today, so the X-Toolken-Key required to authenticate and attribute those requests never reaches the gateway.
Coming soon. Full Hermes support is in progress. The steps below will not work until it ships.

​
Why it does not work yet

Toolken identifies your workspace from the X-Toolken-Key header on every request. Hermes currently sends only your provider key (as Authorization: Bearer) to the configured base URL. Its config accepts a headers field, but those values are silently dropped and never forwarded. Without X-Toolken-Key, the gateway cannot authenticate the request.

​
What is coming

Toolken is adding server-side key management. Once it ships, you will point Hermes at the gateway with a single Toolken key — Toolken handles provider routing and attribution on the server side with no custom headers required. The Hermes config will shrink to just a base URL and that one key. This page will be updated with a full step-by-step guide when support is ready.

​
Get notified

Want this sooner? Reach out at [email protected] and we will let you know when Hermes support lands.

​
Next

OpenClaw

OpenClaw forwards custom headers today — the Toolken integration is fully working.

Providers & Routing

One gateway URL, 13 providers, your own keys.