Hermes

Before you start

Install the named client using its official instructions. Pi here means the pi-mono coding agent; Hermes means Nous Research's Hermes Agent.

Once your Inferway account is activated, get an API key from Console → API keys. Use a dedicated key for this client and review its model access and spending limits. Both live and test prefixes use the same inference and billing path; test is an environment label, not a free or simulated inference mode.

Use an Inferway key for Inferway's endpoint. An OpenRouter key belongs to OpenRouter and cannot authenticate to this address.

Keep the key in the client's credential store or your local environment. Do not paste it into a prompt, screenshot, or committed configuration. These examples use bash/zsh on macOS or Linux.

Make the key available to this terminal

The prompt below hides your input and keeps the key out of shell history. Start the client from this same terminal; a separately opened app may not inherit this variable.

printf 'Inferway API key: '
IFS= read -r -s INFERWAY_API_KEY
printf '\n'
export INFERWAY_API_KEY

Confirm the endpoint and model

Use the full model ID inferway/mimo-v2.6-flash. The Base URL ends in /v1 once; do not append /chat/completions to a Base URL setting. Check that the response below contains the model ID.

curl --fail-with-body --silent --show-error --max-time 30 \
  'https://api.inferway.ai/v1/models' \
  -H "Authorization: Bearer $INFERWAY_API_KEY"

Add a named custom provider

Merge the following into ~/.hermes/config.yaml, preserving your other providers and model settings. This uses the current providers dictionary; older releases may use custom_providers. Consult your installed version's provider guide before mixing the two formats.

key_env contains the variable name without a dollar sign. The key stays in the current environment. For persistent setup, use Hermes's credential configuration on your machine and protect ~/.hermes/.env from source control and screenshots.

transport: chat_completions pins the supported protocol instead of relying on detection. context_length is the combined input/output window from the catalog, not an output-token budget.

providers:
  inferway:
    api: "https://api.inferway.ai/v1"
    key_env: INFERWAY_API_KEY
    transport: chat_completions
    default_model: "inferway/mimo-v2.6-flash"
    context_length: 393216
model:
  provider: "custom:inferway"
  default: "inferway/mimo-v2.6-flash"

Start Hermes and select the provider

Launch Hermes from the terminal where the key is set. The model.provider setting chooses the saved provider. You can also use hermes model to configure a Custom endpoint interactively; use the same URL and exact model ID. Inside a session, /model selects an already configured provider.

hermes

Confirm the connection

1. Start a fresh conversation with the configured provider and model. Ask: "Reply with exactly: connected". Confirm that text arrives without an API error.
2. Open Console → Requests to see the request status and token usage.
3. For coding tasks, ask the client to read a non-sensitive file. Review any proposed edits before applying them.

Cost and usage

Actual consumption is recorded by Inferway: open Console → Requests to see each request's status and token usage, and Console → Usage for totals. Numbers a client shows locally are its own estimates, not billing amounts; rely on the Console.

Verification status

Verified on 0.18.2, macOS 26.6.2 arm64, 2026-09-25: basic conversation, and file-read, file-edit and shell-command tool round trips against inferway/mimo-v2.6-flash.

Streaming was not tested in one-shot mode by this receipt; the client may still stream, but this is not verified evidence here.

This evidence does not cover images, session resume, or reasoning control. Client-side cost estimates are not billing amounts; use Console → Requests and usage for actual consumption.

If a request fails

Authentication: check that an API key is present, active, and allowed to use the model. Reopen the client from the terminal containing the variable. Never print the full key when debugging.

Wrong endpoint or model: check for a duplicate /v1, use the exact published model ID, and confirm the client is using Chat Completions. A request to /responses or /completions cannot be repaired by changing the key.

Limits or timeout: check wallet balance and key limits, respect Retry-After, and reduce the prompt or output budget. Keep streaming enabled for long outputs. Avoid repeated agent retries while diagnosing.

When contacting support, share the client version, model ID, timestamp, and request ID if available. Redact credentials and source code.