Hermes Agent

Hermes Agent can route model requests through TokenHub's OpenAI compatible API gateway. Keep the official installation flow, then replace only the API key, Base URL, and model ID.

The TokenHub endpoint used by this guide is https://us-api.tokenhub.com/v1/chat/completions.

When to use it

Start in a small repository or test project. First ask the tool to read files, explain code, or produce a plan; only then enable edits, terminal commands, or agent automation.

Install or open the tool

Follow the official Hermes Agent documentation to install or open the tool. If menus or command names differ, prefer the current official documentation.

For CLI tools, confirm the executable works before adding TokenHub credentials:

hermes --version

Prepare TokenHub credentials

Create a TokenHub API key and choose a model from the TokenHub model list that fits this tool.

export TOKENHUB_API_KEY="sk-..."

Keep the key in your local shell, IDE secret storage, or the secure API key field of the tool. Do not commit it to the repository.

Configure TokenHub persistently

Use the tool configuration file or settings page first. This avoids the common problem where a terminal sees the environment variable but the IDE, plugin, or new window does not.

Provider values

Settings file locations

TOKENHUB_API_KEY=sk-...

custom_providers:
  - name: tokenhub-custom
    base_url: '__API_BASE_URL__/v1'
    key_env: TOKENHUB_API_KEY
    api_mode: chat_completions

model:
  provider: 'custom:tokenhub-custom'
  default: 'gpt-4.1'

This follows Hermes' current named custom provider schema: base_url is the OpenAI-compatible Base URL, key_env reads the secret without writing it into YAML, and api_mode: chat_completions selects /v1/chat/completions.

Always keep the custom: prefix. Hermes treats bare tokenhub as a built-in provider alias; custom:tokenhub-custom unambiguously selects this self-hosted endpoint.

/model custom:tokenhub-custom:gpt-4.1

hermes chat

Hermes stores the named custom provider, Base URL, API mode, and default model in ~/.hermes/config.yaml. The API key remains in ~/.hermes/.env. You can also run hermes model, select Custom Endpoint, and enter the same values interactively.

If the tool separates chat, edit, apply, and fast models, use the same TokenHub model for the first test. Split models later by cost, latency, and reasoning strength.

Temporary environment variables for debugging

Use temporary variables only to confirm the key, network, and model name. After validation, move the same values into the persistent configuration above.

export TOKENHUB_API_KEY="sk-..."

Verify the connection

Test with a read-only prompt first, confirming that the model can read context without changing files. Then test edits, Apply, or agent tasks.

Read the project README and summarize it in three sentences. Do not modify any files.

After a successful prompt, check TokenHub request logs for model name, endpoint, token usage, and billing group.

Troubleshooting