Hermes Quick Start

Purpose

This guide connects Hermes to AnyRoute through the Anthropic-compatible Messages API and verifies a minimal working setup.

1. Before you begin

Confirm that:

You created an API key on the AnyRoute API Keys page.

You know the exact model ID Hermes should call.

You can edit Hermes's config.yaml.

You intend to use the Anthropic-compatible endpoint, not the OpenAI-compatible endpoint.

2. Supported models

Common Anthropic-compatible model IDs include:

claude-fable-5

claude-opus-4-8

claude-opus-4-7

claude-opus-4-6

claude-sonnet-5

claude-sonnet-4-6

claude-haiku-4-5-20251001

Use the Supported Models page and your AnyRoute console as the current source of truth.

3. Configure `custom_providers`

The setup has three parts:

Define an AnyRoute provider under custom_providers.

Point the default model to that provider.

Disable smart model routing so Hermes does not silently select another model.

Define the provider

Required values:

base_url: https://cc.anyroute.io

api_mode: anthropic_messages

Select the provider as the default

model.provider must match the custom_providers[].name value.

Disable smart model routing

Otherwise, Hermes may route short prompts to a lower-cost model instead of the model selected above.

4. Minimal combined configuration

Replace <your-key> locally. Do not commit the configured file or share it while it contains a real key. Restrict its filesystem permissions on shared systems.

To switch models, update both model.default and the matching entry under custom_providers[].models.

5. Success checklist

base_url is https://cc.anyroute.io.

api_mode is anthropic_messages.

model.provider matches the custom provider name.

Smart model routing is disabled.

Hermes receives a normal model response.

Troubleshooting

Why use the Anthropic-compatible mode?

This setup uses the Anthropic Messages endpoint:

POST /v1/messages

Set api_mode: anthropic_messages; do not mix this guide with an OpenAI Chat Completions configuration.

Hermes selected a different model

Check that smart_model_routing.enabled is false.

Can I use `api_key_env`?

The source configuration records inconsistent api_key_env behavior in Hermes v0.10.0. If your installed version fails to expand the environment variable and returns HTTP 401, verify the current Hermes documentation or use the direct api_key field temporarily. Protect the resulting configuration file as a secret.

HTTP 401

Check the key, both key fields in the configuration, and whether Hermes loaded the file you edited.

HTTP 503

Confirm that Hermes is using anthropic_messages. If it is, check the AnyRoute service status and try another currently available model.

6. Test the AnyRoute endpoint directly

This request helps distinguish an AnyRoute endpoint issue from a Hermes configuration issue:

Run this only in a private terminal. Avoid saving a real API key in shell history.

Next steps

OpenClaw Quick Start

Cherry Studio Quick Start

AnyRoute API Keys

Purpose#

1. Before you begin#

2. Supported models#

3. Configure custom_providers#

Define the provider#

Select the provider as the default#

Disable smart model routing#

4. Minimal combined configuration#

5. Success checklist#

Troubleshooting#

Why use the Anthropic-compatible mode?#

Hermes selected a different model#

Can I use api_key_env?#

HTTP 401#

HTTP 503#

6. Test the AnyRoute endpoint directly#

Next steps#