RunBerth Documentation

RunBerth gives your agents every computer they need. One account and one API key start sandboxes, Linux and Windows desktops and Android phones on demand, billed per second on one invoice. Drive all of it from the dashboard, the CLI, the API, the SDK or MCP.

One account and key; three families of machines; agents, add-ons, end users, activity and one bill around them.

Which one do I need?

You needUse
Run code a model wrote and throw the machine awaySandbox
A workspace per user that keeps its files and toolsAgent box
The same job on many machines at once (evals, rollouts, batches)Swarm
A browser or a Linux app with a screen, driven by your modelLinux desktop
Software that only runs on WindowsWindows desktop
A mobile app with no APIAndroid phone
A long-running agent with memory, channels and schedulesAgent (in its own Agent box)

The machines

Agent boxes

Sandboxes

Computers on demand

Around every machine

  • Agents and templates

    Run OpenClaw, Hermes, Claude Code or your own container in an agent box.

  • Add-ons

    Static and residential IPs, private networks, warm pools and daily backups.

  • End users

    One machine per user of your product, keyed by your own id.

  • Activity

    Every start, sleep, wake and error across your account.

  • One bill

    Per-second usage from the plan credit, one invoice a month.

References

Driving RunBerth from a coding agent?

Copy the instructions into Claude Code, Cursor or Codex and it sets up RunBerth for you. The machine-readable contract is runberth guide --json; the full index is /llms.txt.

The AI-agent guide