Skip to main content

Nous Portal

Nous Portal is Nous Research's unified subscription gateway and the recommended way to run Hermes Agent. One OAuth login replaces the juggling act of separate accounts, API keys, and billing relationships across every model lab, search API, image generator, and browser provider you'd otherwise need to wire up by hand.

If you only have time to set up one thing, set up this. The fastest path:

hermes setup --portal

That single command runs the Portal OAuth, sets Nous as your inference provider in config.yaml, and turns on the Tool Gateway. You're ready to hermes chat immediately after.

Don't have a subscription yet? portal.nousresearch.com/manage-subscription — sign up, then come back and run the command above.

What's in the subscription​

300+ frontier models, one bill​

The Portal proxies a curated catalog of agentic models from across the ecosystem — billed against your Nous subscription instead of one credit balance per lab.

FamilyModels
Anthropic ClaudeOpus, Sonnet, Haiku (4.x series)
OpenAIGPT-5.4, o-series reasoning models
Google Gemini2.5 Pro, 2.5 Flash
DeepSeekDeepSeek V3.2, DeepSeek-R1
QwenQwen3 family, Qwen Coder
Kimi / MoonshotKimi-K2, Kimi-Latest
GLM / ZhipuGLM-4.6, GLM-4-Plus
MiniMaxM2.7, M1
xAIGrok-4, Grok-3
HermesHermes-4-70B, Hermes-4-405B (chat, see note below)
+ everything else240+ additional models — the full agentic frontier

Routing happens through OpenRouter under the hood, so model availability and failover behavior matches what you'd get with an OpenRouter key — just billed against your Nous subscription instead. Switch between Claude Sonnet 4.6 for code and Gemini 2.5 Pro for long context with /model mid-session — no new credentials, no top-ups, no surprise zero-balance errors.

The Nous Tool Gateway​

The same subscription unlocks the Tool Gateway, which routes Hermes Agent's tool calls through Nous-managed infrastructure. Five backends, one login:

ToolPartnerWhat it does
Web search & extractFirecrawlAgent-grade search and full-page extraction. No Firecrawl API key, no rate limit babysitting.
Image generationFALNine models under one endpoint: FLUX 2 Klein 9B, FLUX 2 Pro, Z-Image Turbo, Nano Banana Pro (Gemini 3 Pro Image), GPT Image 1.5, GPT Image 2, Ideogram V3, Recraft V4 Pro, Qwen Image.
Text-to-speechOpenAI TTSHigh-quality TTS without a separate OpenAI key. Enables voice mode across messaging platforms.
Cloud browser automationBrowser UseHeadless Chromium sessions for browser_navigate, browser_click, browser_type, browser_vision. No Browserbase account needed.
Cloud terminal sandboxModalServerless terminal sandboxes for code execution (optional add-on).

Without the gateway, hooking each of those up means a Firecrawl account, a FAL account, a Browser Use account, an OpenAI key, and a Modal account — five separate signups, five separate dashboards, five separate top-up flows. With the gateway, all of it routes through one subscription.

You can also enable just specific gateway tools (e.g. web search but not image generation) — see Mixing the gateway with your own backends below.

Nous Chat​

Your Portal account also covers chat.nousresearch.com — Nous Research's web chat interface with the same model catalog. Useful when you're away from your terminal, or for non-agent conversation work.

No credentials in your dotfiles​

Because everything routes through one OAuth-authenticated Portal session, you don't accumulate a .env file with a dozen long-lived API keys. The refresh token at ~/.hermes/auth.json is the only credential on disk, and Hermes mints short-lived JWTs from it per request — see Token handling below.

Cross-platform parity​

Native Windows is still early beta, and per-tool API key setup is its rough edge — installing a Firecrawl account, a FAL account, a Browser Use account, an OpenAI key from Windows is the highest-friction part of getting a useful agent. A Portal subscription smooths that out: one OAuth covers the model and every gateway tool, so Windows users get the same experience as macOS/Linux without manually configuring four backends.

A note on Hermes 4​

Nous Research's own Hermes 4 family (Hermes-4-70B, Hermes-4-405B) is available through the Portal at heavily discounted rates. These are frontier hybrid-reasoning chat models — strong at math, science, instruction following, schema adherence, roleplay, and long-form writing.

They are not recommended for use inside Hermes Agent, however. Hermes 4 is tuned for chat and reasoning, not the rapid-fire tool-calling loop the agent relies on. Use them for Nous Chat, for research workflows, or via the subscription proxy from other tooling — but for agent work, pick a frontier agentic model from the catalog instead:

/model anthropic/claude-sonnet-4.6     # best general-purpose agentic model
/model openai/gpt-5.4                  # strong reasoning + tool calling
/model google/gemini-2.5-pro           # huge context window
/model deepseek/deepseek-v3.2          # cost-effective coder

The Portal's own model info page carries the same warning, so this isn't a Hermes-side opinion — it's the official guidance from Nous Research.

Setup​

Fresh install — one command​

hermes setup --portal

This runs the full setup in one shot:

  1. Opens your browser to portal.nousresearch.com for OAuth login
  2. Stores the refresh token at ~/.hermes/auth.json
  3. Sets Nous as your inference provider in ~/.hermes/config.yaml
  4. Turns on the Tool Gateway (web, image, TTS, browser routing)
  5. Returns you to your terminal ready to hermes chat

If you don't have a subscription yet, sign up at portal.nousresearch.com/manage-subscription first.

Existing install — add Portal alongside other providers​

If you already have Hermes configured with OpenRouter, Anthropic, or any other provider and you want to add the Portal alongside them:

hermes model
# pick "Nous Portal" from the provider list
# browser opens, sign in, done

Your existing providers stay configured. You can switch between them with /model mid-session or hermes model between sessions — the Portal becomes one of your available providers, not your only one.

Headless / SSH / remote setup​

OAuth needs a browser, but the loopback callback runs on the machine where Hermes is running. For remote hosts, see OAuth over SSH / Remote Hosts — the same patterns work for the Portal as for any other OAuth-based provider (ssh -L port forwarding, --manual-paste for browser-only environments like Cloud Shell / Codespaces).

Profile setup​

If you use Hermes profiles, the Portal refresh token is automatically shared across all profiles via a shared token store. Sign in once on any profile, and the rest pick it up automatically — no need to repeat the OAuth flow per profile.

Using the Portal day-to-day​

Inspecting what's wired up​

hermes portal status     # login status, subscription info, model + gateway routing
hermes portal tools      # detailed Tool Gateway catalog with per-tool routing
hermes portal open       # open the subscription management page in your browser

hermes portal status (or just hermes portal) gives you the high-level overview:

  Nous Portal
  ───────────
  Auth:    ✓ logged in
  Portal:  https://portal.nousresearch.com
  Model:   ✓ using Nous as inference provider

  Tool Gateway
  ────────────
  Web search & extract  via Nous Portal
  Image generation      via Nous Portal
  Text-to-speech        via Nous Portal
  Browser automation    via Nous Portal
  Cloud terminal        not configured

Switching models​

Inside a session:

/model anthropic/claude-sonnet-4.6
/model openai/gpt-5.4
/model google/gemini-2.5-pro

Or open the picker:

/model
# arrow keys, enter to select

Outside a session (the full setup wizard, useful when adding a new provider):

hermes model

Mixing the gateway with your own backends​

If you already have, say, a Browserbase account and want to keep using it while routing web search and image generation through Nous, that's supported. Use hermes tools to pick backends per tool:

hermes tools
# → Web search       → "Nous Subscription"
# → Image generation → "Nous Subscription"
# → Browser          → "Browserbase"  (your existing key)
# → TTS              → "Nous Subscription"

The Tool Gateway is opt-in per tool, not all-or-nothing. See the Tool Gateway docs for the full per-tool configuration matrix.

Subscription management​

Manage your plan, view usage, or upgrade/cancel at any time:

Configuration reference​

After hermes setup --portal, ~/.hermes/config.yaml will look like:

model:
  provider: nous
  default: anthropic/claude-sonnet-4.6     # or whatever model you picked
  base_url: https://inference.nousresearch.com/v1

The Tool Gateway settings live under their respective tool sections:

web:
  backend: nous       # web search/extract routes through Tool Gateway

image_gen:
  provider: nous

tts:
  provider: nous

browser:
  backend: nous

The OAuth refresh token is stored separately at ~/.hermes/auth.json (not in config.yaml — credentials and configuration are kept separate by design).

Token handling​

Hermes mints a short-lived JWT from your stored Portal refresh token on each inference call rather than reusing a long-lived API key. The token lifecycle is fully automatic — refresh, mint, retry on transient 401 — and you never see it.

If the Portal invalidates the refresh token (password change, manual revoke, session expiry), the invalid refresh token is quarantined locally so Hermes stops replaying it and you don't see a stream of identical 401s. The next call surfaces a clear "re-authentication required" message. Run hermes auth add nous to log in again; the quarantine clears on the next successful login.

Troubleshooting​

hermes portal status shows "not logged in"​

You haven't completed the OAuth flow, or your refresh token was wiped. Run:

hermes auth add nous --type oauth

or use hermes model and re-select Nous Portal.

Got a "re-authentication required" message mid-session​

Your Portal refresh token was invalidated (password change, manual revoke, or session expiry). Run hermes auth add nous and your next request will use the new credentials. Any quarantine on the old token clears automatically on successful re-login.

Want to use a specific provider model that the Portal doesn't expose​

The Portal proxies through OpenRouter, so any model that OpenRouter supports is generally available. If a specific model isn't appearing in /model, try the OpenRouter-style slug directly:

/model anthropic/claude-opus-4.6

If a model is genuinely missing, open an issue — we surface the Portal's catalog to Hermes and gaps usually mean a routing config we can update.

Bills not appearing on my Portal account​

Check hermes portal status first — if it shows you're using a different provider (Model: currently openrouter instead of using Nous as inference provider), your local config has drifted. Run hermes model, pick Nous Portal, and the next request will route through your subscription.

See also​

  • Tool Gateway — Full details on every gateway tool, per-tool config, and pricing
  • Subscription proxy — Use your Portal subscription from non-Hermes tools (other agents, scripts, third-party clients)
  • Voice mode — Voice conversations using the Portal's OpenAI TTS
  • AI Providers — Full provider catalog if you want to compare alternatives
  • OAuth over SSH — Login from remote hosts or browser-only environments
  • Profiles — Multiple Hermes configurations sharing one Portal login