Nous Portal and Tool Gateway Operations

Nous Portal is the recommended streamlined setup for Hermes Agent. One OAuth login can configure a model provider and the managed Tool Gateway, reducing the number of long-lived API keys and separate vendor accounts an operator must maintain.

Official documentation: https://hermes-agent.nousresearch.com/docs/integrations/nous-portal

Separate model routing from tool routing

The Portal can supply model inference and managed tool backends, but those are distinct routing decisions. hermes portal info should show which provider handles inference and which gateway tools are enabled. Teams can mix Portal services with their own backends when there is a clear privacy, capability, or cost reason.

Treat OAuth state as a credential

Portal removes many API keys from .env, but the refresh token in the Hermes authentication store still grants access. Protect the Hermes home directory, use normal OS account separation, and re-authenticate through hermes auth add nous when a token is revoked or quarantined.

Operational checklist

Run hermes setup --portal for a fresh streamlined setup.
Inspect hermes portal info.
Enable only the managed tools the workflow needs.
Confirm the selected model is appropriate for agentic tool use.
Protect the authentication store with OS permissions.
Document any tool that uses a non-Portal backend.

Common pitfalls

Assuming model and tool traffic always use the same route.
Selecting a chat-oriented model for a demanding agent loop without testing.
Treating OAuth as permission-free because no API key is visible.
Forgetting that remote browser and sandbox tools run on managed infrastructure.
Diagnosing billing before checking the active provider in portal info.

Verification steps

Complete Portal login.
Run hermes portal info and confirm inference routing.
Perform one web-search test.
If enabled, perform one image, speech, or browser test with public-safe input.
Switch models and confirm the intended provider remains active.
Revoke or log out only in a controlled test, then verify re-authentication recovery.

A reliable Hermes workflow is defined by observable behavior, bounded authority, and repeatable verification—not by configuration alone.