Nous Portal: one account instead of nine API keys

Running an agent seriously means collecting API keys. One for the model provider, another for whichever model you fall back to, one for search, one for image generation, one for speech, one for the browser automation service, one for the code sandbox. Each with its own billing, its own rate limits, its own dashboard, and its own way of failing at three in the morning.

Nous Portal, which launched in April 2026, is Nous Research's answer to that specific mess: one account covering Hermes Agent, an inference API, and Hermes Cloud hosting.

What is in the box

• A model catalogue — reported at 248 models, so you are not committing to one vendor's line.
• A managed tool gateway — search, image and video generation, speech, browser automation and code sandboxes, all behind the same auth.
• Monthly credits against usage.
• Hermes Cloud hosting, so the agent does not have to live on your laptop.

Setup is a single command in the terminal (hermes setup --portal) or one click in Hermes Desktop. That is the actual product: not any individual capability, but the removal of seven separate signup flows.

The tool gateway is the interesting part

Model access is close to a commodity — several routers will sell you a large catalogue behind one key. The part that is harder to assemble yourself is the tool side.

An agent that can search, generate an image, transcribe audio, drive a browser and execute code in a sandbox is drawing on five different vendors with five different integration shapes. Wiring those up individually is a week of work you will repeat on the next project, and browser automation and code sandboxes in particular are genuinely unpleasant to self-host safely.

Collapsing that into one authenticated surface is worth real money, and it is worth more to a small team than to a large one — because a large one has already built it.

What it locks in

Be clear-eyed about the trade. A bundled gateway means your tool calls route through one provider. That is convenient and it is also a dependency:

• One outage surface. Consolidation cuts both ways — the gateway going down takes search, sandboxes and browser automation with it, where before you would have lost one of them.
• Credit-shaped pricing. Monthly credits are easy to reason about until a workload changes shape. Watch what a heavy month actually costs before committing anything load-bearing.
• Data path. Tool traffic — including whatever your agent searches for and whatever it puts in a sandbox — flows through the gateway. That is a question to answer before pointing it at client work, not after.

The mitigation is the same as with any aggregator: Hermes will also talk to OpenRouter, OpenAI, or a custom endpoint. Keeping your model configuration portable means the Portal stays a convenience rather than a foundation, and you can leave by changing configuration rather than rewriting an integration.

Who should look at it

If you are running Hermes and currently juggling keys, this is aimed squarely at you and the setup cost is one command. If you want an agent running somewhere other than your own machine without standing up infrastructure, Hermes Cloud is the shortest path there.

If you already have a working platform — your own gateway, your own sandboxes, your own billing — the Portal is solving a problem you have already solved, and you should keep your own.

Details are at portal.nousresearch.com. Check current plan pricing there directly; this piece deliberately does not quote a figure, because that is the fastest-rotting fact on the page.