# Run Hermes Agent on AnyRouter

> Install the official AnyRouter plugin for Hermes Agent, add one key, and pick from tool-capable models, including the anyrouter/hermes meta-model with automatic fallback.

- Date: November 9, 2026
- Category: guides
- HTML: https://anyrouter.dev/blog/hermes-agent-anyrouter

## What you'll set up

[Hermes Agent](https://hermes-agent.nousresearch.com) is Nous Research's terminal coding agent. The official AnyRouter provider plugin, listed on the [Hermes plugin marketplace](https://hermes-agent.nousresearch.com/marketplace/anyrouter), connects it to any AnyRouter model with one key.

The `/model` picker lists only routes that can call tools, read live from the model catalog, so the agent loop does not break on a model that cannot use tools. `anyrouter/hermes` is AnyRouter's own routing meta-model, not a Nous model: it sends each request to the best available tool-calling model and falls back automatically. It bills at the underlying model's rate.

## 1. Install the plugin

From a terminal, install the plugin from the marketplace catalog:

```bash
hermes plugins install anyrouter
hermes plugins list
```

`hermes plugins list` should show `anyrouter` enabled. Prefer clicking? The [marketplace listing](https://hermes-agent.nousresearch.com/marketplace/anyrouter) has an Install in Hermes button, and the [plugin source](https://github.com/AnyRouterHQ/hermes-provider-anyrouter) is on GitHub.

## 2. Add your key

Get a key at [anyrouter.dev](https://anyrouter.dev). It starts with `sk-ar-`. Add it to `~/.hermes/.env`:

```bash
ANYROUTER_API_KEY=sk-ar-your-anyrouter-key
```

The same key also works against the OpenAI-compatible endpoint `https://anyrouter.dev/api/v1`, so you can drive Hermes from any other OpenAI client too.

## 3. Pick a model

Pick interactively with `hermes model` and choose `anyrouter`, or set it per run:

```bash
hermes --provider anyrouter -m anyrouter/hermes
```

| Model | Notes |
| --- | --- |
| `anyrouter/hermes` | Best tool-calling models, with automatic fallback. The agentic default. |
| `anyrouter/auto` | Top platform models. Tools optional. Not for agent loops. |
| `anyrouter/latest` | Latest stable chat model. |
| `moonshotai/kimi-k3` | 1M context, agentic. |
| `deepseek/deepseek-v4-flash` | Fast, reasoning-capable. |

The picker reads the live model list, so new tool-capable routes show up without updating the plugin. Switch mid-session with `/model`. This resets the prompt cache.

## 4. Check it works

`hermes plugins list` shows `anyrouter` enabled, and your next `hermes chat` message appears in your [request logs](https://anyrouter.dev/dashboard/logs). If the picker is empty, the key is missing or wrong, re-check `ANYROUTER_API_KEY` in `~/.hermes/.env`.

## Optional settings

Set these in `~/.hermes/.env`:

- `ANYROUTER_BASE_URL`, override `https://anyrouter.dev/api/v1` (proxy or relay). The picker then stops filtering by tool support.
- `ANYROUTER_APP_ATTRIBUTION=1`, credit Hermes traffic in the public app rankings. Off by default.
- Hermes forwards a `provider_routing` block as `extra_body.provider`: `sort: price | throughput | latency`, plus `only` / `ignore` / `data_collection: deny`. See [Provider Routing](https://anyrouter.dev/docs/guides/provider-routing).
- See the [Hermes Agent guide](https://anyrouter.dev/docs/guides/hermes-agent) for MCP setup, troubleshooting, and the full `provider_routing` reference.

Everything on this page, as a checklist: the Hermes Agent use case.

[Open the use case](https://anyrouter.dev/use-cases/hermes-agent)
