How xHermes works

Overview

xHermes runs Hermes, an autonomous agent from Nous Research, as a managed service. When you sign in, we provision one Hermes for you, in its own container, and you talk to it through a branded dashboard and console.

You don't set up a server. You don't mind a queue. You don't patch a runtime. You arrive, your agent is there, and it stays there.

Getting started

Two onboarding paths, the same outcome. Pick whichever you already have.

@xHermesBot I need an agent

Either way, you land on the same dashboard with the same agent underneath. Switching paths later is fine — the agent stays yours.

Your agent

Hermes is not a chat box. It's a full autonomous agent with real tools and a deep skill library. From the dashboard you open its console and put it to work on multi-step tasks.

Hermes is a project of Nous Research. xHermes is the managed provisioning layer; the agent itself is open and documented.

Personality (SOUL.md)

Your agent's personality lives in one editable file called SOUL.md. It's plain Markdown: a voice, a few rules, things it cares about. You can edit it any time from the dashboard, and the agent reflects the change immediately.

We also offer a one-click suggestion that drafts a SOUL.mdfrom your X profile, so a new agent doesn't start blank. You always edit the result before saving.

Models & credit

Your agent talks to a language model through a per-agent key that we mint for you. The key carries a credit cap — a hard ceiling on what it can ever spend. If the agent runs up against it, it stops. There is no surprise bill, because there is no bill that can grow past the cap.

Inside that cap, you pick the model from the dashboard. The credit readout in your account is the live number, not a monthly estimate.

SuperGrok + xurl

If you already pay xAI for SuperGrok, you can drop your own key onto your agent and run it on Grok 4 with no LLM cap from us — billing goes direct to your xAI account. The connection happens once on the dashboard.

With a SuperGrok key connected, your agent can also talk to X through the bundled xurlskill — post, reply, search, DM — using the official X developer CLI under the hood. Authorization lives on your agent; we don't mediate the calls.

Walkthrough: @XDevelopers + Nous Research.

Security & isolation

Isolation is the pitch and the implementation. Here are the guarantees in plain language:

• One container per user. Your agent runs in its own container, with its own filesystem and its own memory. No shared process, no shared state, no neighbor.
• Reachable only through xHermes. The container has no public port. Every request to it passes our authenticated front door, which checks that the caller is you.
• Hibernated when idle.If you aren't using it, it stops. It comes back the moment you do. Nothing runs in the background it wasn't asked to.
• Capped LLM spend.The model key tied to your agent has a hard credit ceiling. A runaway loop can't cost more than the cap.
• Sealed secrets.Anything sensitive your agent uses (model key, integrations) is encrypted before it's stored, with the encryption key held outside the agent box. The agent box itself holds no application secrets at rest.
• No wallet custody. Wallet onboarding is a signature on a one-time message. We never see, hold, or move your tokens.

What we store

The short list. Nothing more than the service needs:

Conversation content lives inside your agent's own memory, under your account. Deleting the agent removes it with the container.

FAQ