Hermes

This is NousResearch/hermes-agent, the Hermes Agent, not the Nous Hermes model family. The built-in anthropic provider honors ANTHROPIC_BASE_URL, so two env vars are enough.

Environment

In ~/.hermes/.env:

~/.hermes/.env

ANTHROPIC_API_KEY=<inert key>
ANTHROPIC_BASE_URL=https://api.inert.lol

Then pick provider anthropic and model fable-5.

Custom provider

Alternative path: edit ~/.hermes/config.yaml:

~/.hermes/config.yaml

custom_providers:
  - name: inert
    base_url: https://api.inert.lol
    key_env: INERT_API_KEY        # set in ~/.hermes/.env
    api_mode: anthropic_messages

Set INERT_API_KEY in ~/.hermes/.env.

Warning

api_mode: anthropic_messages is required unless base_url ends in /v1. Without it hermes defaults to chat_completions and calls /chat/completions unprefixed, which 404s. In anthropic_messages mode hermes strips a trailing /v1, so either base form works.

Runtime selection

Select the provider and model at runtime:

text

/model custom:inert:fable-5

Troubleshooting

A 401 missing or malformed API key means the key env var never loaded. Hermes silently sends the placeholder no-key-required when key_env resolves empty. Check ~/.hermes/.env.

Next steps

PiAnother agent harness with a provider override.