Compatible now

1. Create an identity

Create a separate SafetyRouter API key for the Hermes user or agent. Descriptive names and shared project tags make manager reporting useful.

2. Use interactive setup

hermes model
# Choose: Custom endpoint
# Base URL: https://your-company.safetyrouter.io/v1
# API key: sr_live_...
# Model: provider/model-name

3. Or configure it manually

Edit ~/.hermes/config.yaml:

model:
  default: provider/model-name
  provider: custom
  base_url: https://your-company.safetyrouter.io/v1
  api_key: sr_live_...
Local-office example

When Hermes runs on another computer in the office, use http://192.168.166.105:8000/v1. Confirm the SafetyRouter host firewall allows port 8000 only from your trusted LAN.

Keep credentials out of source control

The literal key above makes the file easy to understand, but treat ~/.hermes/config.yaml as a secret. Prefer Hermes' interactive setup or its supported secret-management method for shared systems.

Custom endpoint behavior verified against the official Hermes Agent provider documentation.

Buffered-safety timeout

Allow up to 15 minutes

SafetyRouter intentionally waits for input review, model generation, and output review before releasing model content. Where your client exposes request, response-header, socket-read, or stream-idle timeouts, set them to at least 900000 ms or 900 seconds. Keep streaming enabled. A longer timeout preserves the safety boundary; it does not bypass inspection.