Nous Tool Gateway: Unified Tool Access for Hermes Agent

Configuration Reference

Most users never need to touch configuration files directly, as hermes model and hermes tools cover every workflow interactively. The following is for writing config.yaml directly or scripting setups.

Per-tool use_gateway flag

Each tool's config block takes a use_gateway boolean. Here is an example config.yaml:

web :
  backend : firecrawl
  use_gateway : true

image_gen :
  use_gateway : true

tts :
  provider : openai
  use_gateway : true

browser :
  cloud_provider : browser - use
  use_gateway : true

Precedence: use_gateway: true routes through Nous regardless of any direct keys in .env. use_gateway: false (or absent) uses direct keys if available and only falls back to the gateway when none exist.

Disabling the gateway

To disable the gateway for a specific tool, set use_gateway: false in its config block:

web :
  use_gateway : false # Hermes now uses FIRECRAWL_API_KEY from .env

hermes tools automatically clears the flag when you pick a non-gateway provider, so this usually happens for you.

Self-hosted gateway (advanced)

If you are running your own Nous-compatible gateway, you can override endpoints in ~/.hermes/.env:

TOOL_GATEWAY_DOMAIN = your-domain.example.com
TOOL_GATEWAY_SCHEME = https
TOOL_GATEWAY_USER_TOKEN = your-token # normally auto-populated from Portal login
FIRECRAWL_GATEWAY_URL = https:// .. . # override one endpoint specifically

These knobs exist for custom infrastructure setups such as enterprise deployments or dev environments. Regular subscribers never set them.

Using individual image models

Image generation defaults to FLUX 2 Klein 9B for speed. You can override per-call by passing the model ID to the image_generate tool. The following table lists the available models and their IDs:

The set evolves over time. Run hermes tools and select Image Generation to see the current live list.

How It Works

The Tool Gateway operates as a routing layer between Hermes Agent and the underlying third-party APIs. When a tool call is made, Hermes checks the use_gateway flag for that tool. If true, the call is sent to Nous infrastructure, which forwards it to the appropriate backend (Firecrawl, FAL, OpenAI, Browser Use) using Nous's own API keys and billing agreements. The result is returned to Hermes as if the call had been made directly. This means the same backends are used as the direct-key route, just fronted by Nous. The gateway is per-tool, so you can mix and match: turn it on for just web and images while keeping your own keys for TTS, or route everything through Nous. You can switch any tool at any time via hermes tools. No config editing is required. If you are not logged into Nous Portal yet, picking Nous Subscription kicks off the Portal login inline.

Requirements and Limitations

• The Tool Gateway is a paid-subscription feature. Free-tier Nous accounts can use Portal for inference but do not include managed tools. Upgrade your plan to unlock the gateway.
• Some accounts are entitled to a free tool pool, a small managed-tool allowance that covers gateway tool calls without a paid subscription. This is surfaced by the gateway on first use.
• If your subscription expires, tools routed through the gateway stop working until you renew or swap in direct API keys via hermes tools. Hermes shows a clear error pointing at the portal.
• Modal (serverless terminal) is available as an optional add-on through the Nous subscription, not part of the default Tool Gateway bundle. Configure it via hermes setup terminal or directly in config.yaml.
• You do not need to delete your existing API keys when you enable the gateway. Keep them in .env. When use_gateway: true, Hermes skips direct keys and uses the gateway. Flip the flag back to false and your keys become the source again. The gateway is not a lock-in.
• The gateway is supported on any platform where Hermes Agent runs, as it operates at the tool-execution layer, not the CLI. Every interface that can call a tool (CLI, Telegram, Discord, Slack, IRC, Teams, the API server) benefits from it transparently.

Troubleshooting

No specific failure modes or troubleshooting steps are documented in the source material beyond the following:

• Subscription expired: Tools routed through the gateway stop working. Renew your subscription or swap in direct API keys via hermes tools. Hermes shows a clear error pointing at the portal.
• Free pool available but not active: The gateway surfaces the free tool pool and shows a setup prompt on first use. Opt in to start using managed tools right away.
• Gateway not appearing in hermes tools: Ensure you have a paid subscription or a free tool pool entitlement. Free-tier accounts without a pool will not see the gateway options.
• Self-hosted gateway not connecting: Verify that TOOL_GATEWAY_DOMAIN, TOOL_GATEWAY_SCHEME, and TOOL_GATEWAY_USER_TOKEN are correctly set in ~/.hermes/.env. The user token is normally auto-populated from Portal login, so if you are self-hosting, you must provide it manually.