# Hermes Agent integration

The [AgenticFI Hermes plugin](https://github.com/AgenticFI/onchain-router-hermes) `0.1.0` is a public MIT alpha with an immutable [GitHub release](https://github.com/AgenticFI/onchain-router-hermes/releases/tag/v0.1.0). It is directly installable through Hermes' native GitHub plugin path. It is not a PyPI release or a production-qualified funded integration; PyPI is not required for the native installation.

## What it adds

- native provider `onchain-router` for chat with one explicit live model;
- free discovery tools and commands for models, prices, and voices;
- bounded paid tools for images, MP3 speech, and MP3 transcription;
- redacted status and diagnostics commands;
- explicit recovery guidance and stable idempotency across host retries;
- human-run setup, update, status, stop, and client-removal commands.

The plugin connects only to the authenticated Buyer Runtime proxy on `127.0.0.1`. Wallet and payment authority remain outside Hermes. The plugin does not create, import, inspect, unlock, fund, or back up a wallet; implement x402; download during a model call; choose a fallback; or blindly retry a paid request.

## Requirements and install

- Python `>=3.11,<3.14`;
- Hermes Agent `0.21.0`;
- Node.js 20.18 or newer and npm;
- macOS or Linux;
- a Buyer Runtime profile created and unlocked by a human.

```bash
hermes plugins install AgenticFI/onchain-router-hermes --enable
hermes plugins doctor onchain-router --ci
hermes onchain-router setup
```

Hermes records the installed Git commit. For a reproducible install, append `--ref c9a5ea5e73003c4286a13b0aa81e99259e0a9b14` to the first command. The release page also provides the wheel and source distribution for inspection. Repository qualification checks provider/plugin discovery against Hermes `0.21.0`, build/install/update/uninstall behavior, and makes no paid request.

## Local trust boundary

The plugin uses exact pinned versions of the AgenticFI CLI and proxy and keeps the non-wallet proxy bearer in an owner-only local file. Never expose the proxy outside loopback or put its bearer in a prompt, log, screenshot, or source file.

The current public alpha pins both `@agenticfi/onchain-router-cli@0.1.2` and `@agenticfi/onchain-router-proxy@0.1.2`.

Native chat retries reuse one deterministic idempotency key for the same logical call. Media tools require a caller-supplied stable key. A timeout, disconnect, ambiguous `409`, provider-unknown, settlement-unknown, or receipt-verification failure is not permission for a fresh request.

The complete setup lifecycle, media examples, retention disclosure, tool list, and troubleshooting are in the [public repository](https://github.com/AgenticFI/onchain-router-hermes). A funded Hermes request remains an explicit operator acceptance step because it spends from the operator's Buyer Runtime wallet.