Hermes Agent setup
Use Batchwell in Hermes Agent by adding a custom provider to ~/.hermes/config.yaml with base_url set to the Batchwell base URL.
To use Batchwell in Hermes Agent, set the model block of ~/.hermes/config.yaml to provider: custom, with base_url
set to https://api.batchwell.ai/v1, a Batchwell model id as default, and key_env naming the environment variable that holds your
Batchwell API key. This is Hermes Agent's documented setup for a custom OpenAI-compatible endpoint.
Create a key as described in the Quickstart and Authentication, then run:
It writes ~/.hermes/config.yaml and ~/.hermes/.env: the model settings through hermes config set, and the key line in ~/.hermes/.env (readable only by you). It reads your key from BATCHWELL_API_KEY, or asks for it on the
terminal with the input hidden, and checks it with GET /v1/models before it writes anything. Then start the agent with
hermes. Every file it changes is first copied to <file>.; to undo
it, copy that backup back over the file, or delete a file the command created. The command runs on macOS, Linux and WSL;
see Connect an agent for every option.
Paste this prompt into the agent, or into any coding agent, and it sets itself up the same way. It names the variable that holds the key, never the key itself, and tells the agent to back up each file before it changes it.
The snippet is made for batchwell/kimi-k3.1-pro-uncensored, a model Batchwell serves today. Put your key in ~/.hermes/.env as
BATCHWELL_API_KEY= followed by the key, so no key is written into config.. Create a key as described in the
Quickstart and Authentication.
You can also run hermes model and choose "Custom endpoint (self-hosted / VLLM / etc.)". It asks for the same three
values: the API base URL, the API key and the model name.
defaultis the model Hermes Agent uses. Set it to the model id fromGET /v1/models; see models.provider: customselects Hermes Agent's custom endpoint provider, for any OpenAI-compatible API.base_urlis the address Hermes Agent sends its requests to. Set it to the Batchwell base URL, which ends in/v1.key_envnames the environment variable that holds the key. Hermes Agent readsBATCHWELL_API_KEYfrom your shell or from~/.hermes/.env. The key starts withbw_live_orbw_test_.
Hermes Agent treats config. as the single source of truth for the model and endpoint. It needs a model with a
context window of at least 64,000 tokens for agent use with tools, and refuses to start with a smaller one. Check the
context length of the model you choose on models.
That model lists these supported parameters: temperature, top_p, max_tokens, max_completion_tokens, stop, stream_options, tools, tool_choice, reasoning_effort. These are the model's tunable
parameters, not the whole request: Batchwell accepts only the fields listed under
accepted fields, including stream and stream_options. Any other field fails
with 400 unsupported_parameter, and the error message names the field.
Batchwell rejects n greater than 1, logprobs and top_logprobs with 400 unsupported_parameter, and accepts text content only (parts of
type image_url, input_audio or file get 400 unsupported_content). The full list is on
chat completions.
- Connect an agent compares the five agents and every option of the connect command.
- Routing covers fallback models and routing preferences.
- Errors lists every error code and what to do about it.
- OpenClaw setup shows the same model in OpenClaw's
openclaw..json - Claude Code setup and Codex setup show it in the two coding agents.