Tool
Nous Portal Login, Pricing, API Keys, and Hermes Agent Setup
Open Nous Portal, understand login vs subscription vs API access, run hermes setup --portal, compare Nous Portal with OpenRouter/Ollama/FlyHermes, and avoid provider-credit or rate-limit failures before gateways or cron depend on it.
Quick answer
Nous Portal is Nous Research’s account for Hermes model access, Tool Gateway services and optional Hermes Cloud hosting. Paid plans currently include Hermes Agent usage with reset windows and one Cloud agent up to the plan’s size; API-key requests normally use pay-as-you-go credits. Standard Hermes setup uses OAuth through hermes setup --portal, not a manually pasted Portal API key. Inspect the actual route and allowance before paying again. FlyHermes is a separate, independent managed service.
Use this guide to find the official Portal, choose OAuth or API access, and establish which allowance pays for your requests. Signing in, having an active subscription and having a cash-credit balance are separate facts. Start with the account and route on the machine running your agent; then verify a small model request and the tool or channel workflow you actually need.
Setup steps
- 1Open the official Nous Portal from this page and confirm the account/subscription/API access you intend to use. This Hermes page is not the portal login itself.
- 2Run `hermes setup --portal` when you want Hermes to log in, set Nous as the provider route, and enable Tool Gateway support.
- 3Run `hermes doctor`, then `hermes chat -q "Reply with exactly: nous provider ok"` from the same profile that will later run gateways or cron jobs.
- 4Only after the CLI provider turn works should you add Telegram, Discord, cron jobs, Docker services, Web UI/dashboard checks, or MCP/tool workflows.
- 5If the CLI provider test fails, fix portal login, subscription/API access, quota, model selection, or auxiliary-provider settings before blaming gateway delivery.
- 6If CLI works but Telegram/Discord fails, switch from provider setup to gateway troubleshooting and verify the exact profile/env path used by the service.
Command map
hermes setup --portalFast path for setting Nous Portal as the Hermes provider route and enabling Tool Gateway setup.
Do this before debugging dashboards or gateways; provider auth must work first.
hermes portal info && hermes portal toolsInspect the active Portal login, model and per-tool routing before changing accounts or topping up.
Routing is not an invoice. Review output privately and use the same profile and host as the failing workload.
hermes doctorChecks config, dependencies, provider state, and common setup failures after portal login.
If this fails with provider/auth errors, do not move on to Telegram, Discord, or cron yet.
hermes chat -q "Reply with exactly: provider ok"Small smoke test proving the active Hermes profile can complete one provider-backed model call.
Run it under the same profile/service environment that will own the gateway or cron job.
hermes config path && hermes config env-pathShows where the active profile stores non-secret provider settings and secret environment values.
Never paste raw provider keys into chat, screenshots, logs, or Git.
Self-hosted Web UI or FlyHermes?
Use Nous Portal
You want the official Nous account, included Hermes usage within plan limits, Tool Gateway setup, or the plan’s included Cloud-agent size.
Avoid when: You require local-only processing or a hosting/support policy the current Nous offer does not document.
Use OpenRouter
You want one key for many hosted models, explicit credit limits, fallback choices, and quick experimentation across providers.
Avoid when: Your organization standardizes on Nous Portal or direct provider billing.
Use Ollama/local models
You want privacy, zero API spend, local inference, or a fallback for repetitive low-risk work.
Avoid when: You need frontier reasoning, strong long-context behavior, or low-maintenance team uptime.
Use FlyHermes
You want hosted browser/mobile chat, connected channels, managed uptime, and less provider/VPS/gateway maintenance.
Avoid when: You specifically want to self-host and own every provider key, route, and server boundary.
What you can verify
Features
- ✓OAuth setup for Hermes model access through hermes setup --portal
- ✓Per-tool routing for supported Tool Gateway services
- ✓Included Hermes usage with reset windows on current paid plans
- ✓Separate pay-as-you-go API credits and explicit eligible ChatGPT plan sharing
- ✓One included Hermes Cloud agent up to the paid plan's stated size
- ✓Login, model and tool-routing inspection with portal info and portal tools
- ✓A billing checklist that keeps Portal, direct providers and independent FlyHermes accounts separate
Why this tool matters
Checked November 17, 2026: Portal’s public plan cards describe included Hermes Agent usage with daily, weekly and monthly reset windows. More expensive models use the allowance faster. API keys normally use pay-as-you-go credits, not included usage, so do not interpret the cash-credit balance as the entire subscription.
Eligible ChatGPT plan sharing is a distinct account option. Approve sharing in Linked accounts and check its switch; signing in alone does not enable it. Only eligible inference is covered. Tools and Cloud hosting remain separately charged, and ChatGPT limits apply. The official help page says failed shared requests are not automatically retried against Nous credits; buying credits does not switch sharing off. Team sharing is opt-in and applies only within its documented account/key scope.
Paid Portal plans also advertise one Hermes Cloud agent up to their plan size; extra agents and larger resources can use credits. This is not a reason to infer an exact hosting invoice from a balance screenshot. The older Cloud FAQ also describes running/stopped resource metering: reconcile the account’s actual included allowance and settled charges instead of adding a full hypothetical instance bill.
The standard Hermes OAuth setup does not require you to create a Portal API key. A Portal API key is for the separate API workflow. The Portal account, direct OpenRouter account and FlyHermes subscription do not share a wallet. If usage is unexpected, preserve redacted request times and routes, then use the provider-cost guide linked below before buying more capacity.
Best use cases
How this fits with Hermes Agent
Provider-first setup
Configure Nous Portal, prove one CLI model turn, then add dashboard, gateway, cron, tools, or Docker. This prevents provider errors from being misread as broken Telegram/Discord delivery.
Cost and quota check
Before using Nous Portal for always-on work, confirm subscription/API access, quota, model availability, and auxiliary-provider behavior. Scheduled agents fail differently from one-off chats.
Gateway escalation path
If a portal-backed CLI smoke test works but Telegram or Discord does not, stop changing provider keys and inspect gateway status, allowed chats, topic routing, profile env, and service restarts.
Managed path decision
If the team wants browser/mobile access, channels, uptime, provider operations, and fewer VPS/Docker chores, use FlyHermes instead of turning a self-hosted provider setup into an operations project.
Related Hermes Agent guides
Hermes API key setup
Where provider keys belong, how to smoke test safely, and how to avoid leaking secrets.
Model provider costs and rate limits
Choose provider routes by workload, budget, credits, and reliability instead of picking a single universal model.
OpenRouter for Hermes Agent
Use broad hosted model routing and credit controls when Nous Portal is not the best provider route.
Hermes Dashboard / Web UI
Verify active profile, model/provider state, cron, logs, sessions, and gateway health after provider setup.
FlyHermes pricing
Choose managed cloud when provider operations, gateway uptime, browser/mobile access, and team workflows should be bundled.
FAQ
Nous Portal is the account and model-access portal. For Hermes Agent users, it is relevant because it can be used as a provider route for hosted models and Tool Gateway services.
It is the fast setup path for Nous Portal: Hermes logs you in, sets Nous as the provider, and enables the Tool Gateway. After it completes, run hermes doctor and one tiny chat smoke test before adding gateways or cron jobs.
Tool Gateway gives Hermes managed access to auxiliary capabilities such as web search, image generation, TTS, and cloud browser without juggling separate keys for each tool. Treat it as provider/tool infrastructure, not as a replacement for gateway delivery tests.
Use the external Nous Portal link on this page to open the portal and sign in. This Hermes Agent page is an explainer and provider-setup guide, not the portal login itself.
No. Hermes Agent is model-provider agnostic. Nous Portal is one supported route; OpenRouter, Ollama, OpenAI, Anthropic, Hugging Face, and OpenAI-compatible endpoints are other options.
Use Nous Portal for Nous-hosted model access, OpenRouter for broad model choice and fallback routing, Ollama for local/private inference, and FlyHermes if you want a managed Hermes Agent experience without maintaining provider setup yourself.
Hermes Agent can route model calls through supported providers. Nous Portal is one provider option for users who want to run Hermes Agent with Nous-hosted models while keeping Hermes' tools, skills, memory, and gateway workflows.
Check logs for provider HTTP errors, credit exhaustion, auxiliary model failures, and retry/fallback messages. If a DM or CLI smoke test fails with the same provider error, fix the model route first. If CLI works but Telegram or Discord does not, switch to gateway delivery checks.
Yes. Many searchers type 'nousportal' as one word, but the product intent is Nous Portal: the account, subscription, and model-access portal.
A Nous Portal subscription or account is used for Nous-hosted access and account management. Hermes Agent can use that route when you want Nous-hosted models, but it can also use other providers.
No manual Portal API key is needed for the standard OAuth setup: run hermes setup --portal and approve sign-in. Portal API keys are a separate API workflow, normally billed to pay-as-you-go credits rather than included Hermes usage. Check the explicit ChatGPT plan-sharing scope separately.
No. Nous Portal offers model/tool access and paid plans with one Cloud agent up to their included size. FlyHermes is an independent managed Hermes service with its own hosting, AI credits, billing and support terms. Neither wallet transfers to the other.
Run `hermes doctor`, then `hermes chat -q "Reply with exactly: provider ok"` from the same profile that will run your gateway or cron job. If that fails, fix provider access before touching Telegram, Discord, Docker, or Web UI settings.
No. Nous Portal is best for a Nous-native provider route and Tool Gateway setup. OpenRouter is better when you want many hosted model choices, explicit credit controls, and fallback routes behind one key.
A gateway can look broken when the actual failure is provider quota, exhausted credits, a stale service environment, or a different profile env path. Prove one CLI provider turn first, then test the exact Telegram or Discord surface.
Use FlyHermes when the desired outcome is hosted browser/mobile access, connected Telegram/Discord-style channels, managed uptime, and less provider/VPS/gateway maintenance. Nous Portal is provider infrastructure; FlyHermes is the managed Hermes experience.
Not necessarily. Portal account/subscription access, provider API billing, and other consumer chat subscriptions are separate entitlements. Prove the selected Hermes provider with one CLI smoke test and check the exact account quota before adding gateways or cron.
It is a separate Hermes provider route with its own subscription and model-access terms. Use it when you want the official Portal and Tool Gateway path, and compare it with Claude Code using the same representative task rather than assuming either route is unlimited.
Included Hermes usage and pay-as-you-go API credits are separate meters under the current public plan cards. Inspect the plan’s reset windows, exact route and error. A zero cash balance alone does not prove missing subscription usage; an unresolved purchase discrepancy still belongs with Nous support.