Give Hermes
real compute, pay per second.
Register one skill in Hermes Agent and your flows can spin up persistent sandbox environments, deploy full projects, and expose services publicly — without an account, without infrastructure configuration. Billed per second of active sandbox runtime.
Real Hermes flows that need live compute.
Each pattern below is a Hermes Agent flow with the compute skill registered once. Each uses a different sandbox property — short-lived isolation, stateful pipelines, public deployment, or tiered compute.
Execute generated code safely inside the flow.
A Hermes flow that generates code needs somewhere safe to run it. The flow creates a sandbox as a skill call, executes the code via the process API, reads results back via the filesystem API, and tears down. Per-second billing means the sandbox charges only for the execution window — not the time the flow spends reasoning before or after.
Deploy a project and return a live URL.
A Hermes flow can take a project archive, upload it to a sandbox, and get back a public preview URL — all in a single chain of skill calls. The gateway handles dependency installation and process startup; the flow just receives the URL and passes it downstream. No DNS, no reverse proxy, no infrastructure work inside the flow.
Run a full build inside one environment.
A Hermes build flow checks out code, installs dependencies, runs tests, and reads the artifact — all inside one sandbox that stays alive through every skill call. No reinstalling packages between stages, no state lost between steps. Tear it down when the build finishes; the flow spins up a fresh sandbox for the next run. Pick a tier sized to the build.
Match sandbox tier to the task at hand.
A Hermes orchestration flow can spin up different tiers for different subtasks — a lightweight sandbox for file parsing, a larger one for model inference or compilation. Each sandbox is billed at its tier's per-second rate. Hermes flow budget caps keep total compute spend predictable across all sandbox interactions.
One skill. Real compute inside every flow.
Sandboxes are persistent environments your Hermes flows interact with via process, filesystem, and network APIs. Deploy code by uploading files — JSON or tarball — and the gateway handles dependency installation and process startup. Hermes budget caps bound total sandbox spend; per-second billing means idle flows cost zero.
- Single Hermes skill
- Persistent sandboxes
- Per-second billing
- Flow caps honored
Hermes Agent specific questions.
If something below doesn't cover your case, ping us — we work directly with Hermes Agent builders, no SDR funnel.
How does this register as a Hermes Agent skill?
+
It's a set of POST endpoints — create sandbox, interact via process/filesystem/network, deploy, teardown. Register the base endpoint in Hermes as an HTTP skill with per-second pricing. Hermes uses the rate to estimate sandbox cost before the flow fires and to enforce budget caps across all sandbox interactions in a run.
Does Hermes need a separate account?
+
No. The gateway manages the underlying infrastructure entirely. Hermes pays per second from a wallet you connect — no account to create, no API key to store in flow configuration.
How do sandbox lifetimes work inside a Hermes flow?
+
The flow controls the sandbox lifetime explicitly — create it when compute is needed, use it across as many skill calls as required, and tear it down when done. Billing runs only while the sandbox is active. A flow that creates and tears down within a few seconds pays for only those seconds.
Can a Hermes flow deploy and expose a public URL?
+
Yes. Upload project files via the deploy skill call — the gateway installs dependencies and starts the process. Then call the preview endpoint to get a public URL. The whole sequence is Hermes skill calls; the flow receives the URL and can pass it to the user or downstream steps.
What happens to sandbox state between Hermes skill calls?
+
It persists. The sandbox keeps its process state, installed packages, and filesystem contents between calls. A file written in one skill call is readable in the next. This is what makes multi-step flows efficient — no re-setup, no data shuttling.
How do per-second costs interact with Hermes budget caps?
+
They stack. The sandbox accrues per-second charges while active. Hermes flow budget caps bound total spend across all skill calls — compute included. If the cap is reached mid-task, the flow stops issuing new calls; you can tear down the sandbox and request more budget or hand off the partial result.