Logo

hermes · tool-calling · 312 runs today

Run Hermes agents without building the runtime

Hermes models are good at calling tools. Turning that into something dependable means a loop, a tool registry, retries and somewhere to keep state — that is what we host.

  • Bring your own endpoint
  • Tool registry included
  • Full run traces

From £14.99 a month. Prices exclude VAT. No setup fee, no minimum term.

hermesagent loopplancallobserveanswer

every run, recorded

When an agent does something odd, you can see where it turned

Aggregate metrics tell you a run failed. A trace tells you which tool it reached for, what came back, and which step sent it sideways. Every run keeps one.

run 21b7 · supplier-price-check · hermes
thought

Need current pricing for SKU AX-4120 from three suppliers.

tool

http_get(supplier_a.api/price?sku=AX-4120)

observation

£184.00 · in stock · 3 day lead

tool

sql_query(SELECT last_paid FROM purchases WHERE sku=…)

observation

last paid £201.50 on 12 Aug

answer

Supplier A is £17.50 cheaper than last purchase. Draft raised.

agents on Pro
0agents on Pro
trace retention on Scale
0 motrace retention on Scale
network uptime
0.0%network uptime
UK support
0/7UK support

What you actually have to build

The model call is a few lines. Everything that makes an agent survive contact with a real API is the rest of it.

 Build the loop yourselfA closed agent platformThe Email Shop
Model choiceAnything you likeWhatever the platform supportsAny Hermes endpoint — Nous, OpenRouter, Together or your own
Tool callingYou write the registry, schemas and dispatchBuilt in, within their catalogueRegistry included; register any HTTP or SQL tool you like
Retries and failuresYou handle timeouts, malformed calls and loopsHandled, opaquelyBackoff, retry limits and loop detection, all visible to you
State between runsA database you set upTheirs, in their formatPostgres on your instance, that you can query directly
Seeing what happenedWhatever you loggedTheir dashboardFull traces — every thought, call, response and timing
Where inference happensYour choiceTheir infrastructureYour choice, and your bill — we do not resell tokens

If you need dedicated GPU inference rather than an API endpoint, this is not that product — talk to us about dedicated servers instead.

The runtime, not the model

We host the machinery around the model. Inference stays wherever you choose to buy it.

The agent loop, supervised

Plan, call, observe, repeat — with iteration limits, timeouts and loop detection so a confused agent stops rather than spending your budget in a circle.

A tool registry you control

Register HTTP endpoints, SQL queries and shell commands as tools with typed schemas. Hermes handles the calling; you decide what exists to call.

Any Hermes endpoint

Point the runtime at Nous Research, OpenRouter, Together or your own self-hosted vLLM server. Swap endpoint without rewriting your agent.

State you can inspect

Conversation state, memory and run history live in a Postgres database on your instance. It is your data in ordinary tables, not a proprietary blob.

Traces for every run

Each run records its reasoning steps, tool arguments, responses, token counts and latency. When an agent does something odd you can see exactly where it turned.

Spend limits that bite

Cap tokens per run and per day. When a limit is reached the run stops and you are told, rather than finding out from an invoice at the end of the month.

Why the loop is the hard part

Hermes handles tool calling well. These are the four things that still go wrong once it is talking to real systems.

1

A malformed tool call should not end the run

Models occasionally emit arguments that do not match the schema — a string where a number belongs, a missing required field. Naive implementations either crash or pass the nonsense straight through to your API. The runtime validates every call against its schema, hands the model a specific error it can correct, and only gives up after a set number of attempts. Most malformed calls are fixed on the retry and you never hear about them.

2

Agents loop, and loops cost money

The classic failure is an agent that calls the same tool repeatedly because the response never quite satisfies it. Left alone overnight that is a real bill and nothing to show. We track repeated calls with identical arguments, stop the run when a threshold is crossed, and record why. Combined with per-run and per-day token caps, the worst case is a stopped run and a notification.

3

State has to outlive the process

An agent that forgets everything between runs cannot do anything that spans a week. Keeping state in memory works until the first restart. Every instance gets a Postgres database holding conversation state, memory and run history in ordinary tables — so it survives restarts, and you can query it with psql rather than through an API.

4

You need the trace before you need the dashboard

When an agent does something unexpected, aggregate metrics tell you it happened and nothing more. What you want is the individual run: what it was thinking, which tool it reached for, what came back, and where the reasoning went sideways. We keep the full trace for every run, so debugging starts from evidence rather than from a hypothesis.

Pricing that counts agents, not tokens

Inference is billed to you by your own provider. This is the runtime.

Starter

One agent, in production

£14.99/month

  • 2 vCPU
  • 4 GB RAM
  • 40 GB NVMe
  • 1 agent · 5 tools
  • Supervised agent loop
  • Tool registry with typed schemas
  • Postgres state database
  • Run traces kept 30 days
  • 24/7 UK support
Talk to us about this plan
most chosen

Pro

Several agents sharing tools

£29.99/month

  • 4 vCPU
  • 8 GB RAM
  • 100 GB NVMe
  • 5 agents · unlimited tools
  • Everything in Starter
  • Up to five agents on one instance
  • Shared tool registry across agents
  • Scheduled and webhook triggers
  • Run traces kept 90 days
Talk to us about this plan

Scale

Agents doing continuous work

£59.99/month

  • 8 vCPU
  • 16 GB RAM
  • 200 GB NVMe
  • Unlimited agents
  • Everything in Pro
  • Unlimited agents and parallel runs
  • Separate staging instance
  • Run traces kept 12 months
  • Named technical contact
Talk to us about this plan

Prices exclude VAT. No setup fee, no minimum term.

Frequently asked questions

No, and the distinction matters. We host the agent runtime — the loop, the tools, the state and the traces. Inference happens at an endpoint you choose: Nous Research, OpenRouter, Together, or a vLLM server you run yourself. You bring the endpoint and the key, and the provider bills you for tokens directly.

Because serving Hermes weights properly means dedicated GPUs, and that costs an order of magnitude more than these plans. Bundling it would mean either a much higher price or a quietly rationed service. If you want dedicated GPU hardware, talk to us about a dedicated server and we will quote it honestly.

Yes. The runtime speaks the OpenAI-compatible chat completions format, so any endpoint offering that will work, including Claude, GPT and open-weight models via OpenRouter. The page says Hermes because that is what it is tuned and tested against, particularly for tool calling.

One configured agent: its system prompt, its set of tools, its state and its schedule. Running the same agent a thousand times a day is still one agent. Starter includes one, Pro includes five, and Scale is unlimited.

You set a token ceiling per run and per day. The runtime counts tokens as it goes, and when a limit is reached it stops that run cleanly and notifies you. Because you hold the inference account, you also keep whatever limits your provider offers — this sits on top as a faster-acting brake.

Yes. Agent definitions are plain configuration and your state is in a Postgres database you can dump at any time. Ask us and we will hand you both. Nothing about your agent is stored in a format only we can read.

Stop rebuilding the same agent loop

Bring an endpoint and a list of tools, and we will have your first agent running today. From £14.99 a month.