phaseo hermes to set Phaseo as Hermes Agent’s custom endpoint with its own key, or set the same four Hermes settings and one .env line yourself.
Set up with the Phaseo CLI
sh, bash and curl. Setup then:
- Saves your current values of
model.provider,model.base_url,model.defaultandmodel.key_env, so removal can restore them. - Creates a
Phaseo CLI: Hermes Agent API Keythat expires after 90 days and has a $100 monthly spend limit. - Writes the key to Hermes’
.envfile asOPENAI_API_KEY, inside a block that starts with# >>> phaseo managed (do not edit)and ends with# <<< phaseo managed. Your other lines are left alone, and the key never appears on a command line. - Runs
hermes config setto point Hermes at Phaseo:
model.key_env tells Hermes to send OPENAI_API_KEY to the custom endpoint. Without it, Hermes sends that key only to OpenAI’s own hosts, and requests reach Phaseo without a key.
Phaseo asks Hermes where its .env file is (hermes config env-path), which covers profiles and other overrides. If Hermes can’t say, the CLI uses the .env in HERMES_HOME, or ~/.hermes/.env (%LOCALAPPDATA%\hermes\.env on native Windows). Hermes keeps provider keys in this plaintext file, so protect it like any other key file.
Run phaseo hermes again to replace an expired key or change the model. It keeps the settings saved on the first run.
Configure Hermes manually
Add your Phaseo API key to Hermes’.env file:
.env
hermes config env-path to find the .env file Hermes reads.
Check it works
Restart active Hermes sessions so they use the Phaseo endpoint and key. Runhermes config get model.base_url --json to confirm it returns https://api.phaseo.app/v1, then send a short prompt and confirm the request appears in Settings → Usage → Logs.
Remove Phaseo
.env, deletes the CLI’s saved state in ~/.config/phaseo/integrations/hermes.json, and revokes the key. Restart active Hermes sessions so they reload the restored configuration.
Fix common problems
For other agents and the provider values every agent needs, see Coding Agents.