Introduction to Hosted Agents

Hosted Agents are fully managed virtual machines that run an open-source agent framework for you. You pick a framework and a plan, and DeepInfra provisions the instance, installs and configures the agent, and wires it to a dedicated DeepInfra API key — no servers to set up, no config files to bootstrap. Your instance is up and running in a few minutes, and its state persists across stops and restarts. Manage your instances at Dashboard → Hosted Agents.

Available frameworks

Framework	Access	Description
OpenClaw	Web dashboard + SSH	Your personal AI assistant, reachable on the messaging channels you already use. Open source.
Hermes-Agent	SSH only	Self-improving autonomous agent by Nous Research, driven from the terminal. Open source.

Plans

Plan	vCPU	RAM	Included monthly transfer	Available for
`standard`	2	4 GB	4 TB	OpenClaw
`budget`	2	2 GB	3 TB	OpenClaw, Hermes-Agent
`tiny`	2	1 GB	2 TB	Hermes-Agent

Current per-hour pricing for each plan is shown in the Create Instance dialog and on each instance’s details page.

Billing

Two separate line items make up the cost of a hosted agent:

Compute — a per-hour rate for the instance itself, billed only while the instance is active (creating, starting, running, or stopping). A stopped instance costs nothing.
Inference — whatever the agent spends on model calls. Each instance gets its own DeepInfra API key, and its LLM usage is billed at standard token prices against your account.

Both appear on your Usage page; compute shows up as Hosted Agent.

Fair use: instances that exceed an average of their plan’s included network transfer per month (inbound + outbound, prorated by uptime) may be temporarily paused. You can start the instance again from the dashboard once usage normalizes.

Create an instance

Add an SSH key

Register your public SSH key at Dashboard → SSH Keys. It’s installed on every instance you create, and you’ll need it to connect over SSH.

Open Hosted Agents

Go to Dashboard → Hosted Agents and click Create Instance.

Configure and create

Pick a Name (up to 64 characters), an Instance Type (the agent framework), and a Plan, then click Create.

Wait for it to come up

Setup is fully automated and takes a few minutes. Once the instance is running, connect via the dashboard link (OpenClaw) or SSH (any framework).

Instance lifecycle

State	Description
`creating`	The instance is being provisioned
`starting`	The instance is booting up
`stopping`	The instance is shutting down; a snapshot of its state is captured
`running`	The instance is active and accessible
`stopped`	The instance is shut down — not billed for compute
`failed`	The instance hit an unrecoverable error (see the fail reason on its details page)

Stopping an instance shuts it down so you’re not billed for compute while it’s idle. Starting it again restores everything as it was.

The instance gets a new public IP address on every restart. Check the details page for the current one.

Manage an instance

From the instance list or its details page you can:

Start / Stop — pause compute billing without losing state.
Update — when a newer framework version is available, upgrade in place. No restart needed; the agent may be unresponsive for a few minutes.
Backup — trigger a snapshot on demand (see below).
Delete — stop and permanently remove the instance. This cannot be undone.

DeepInfra retains administrative SSH access to your instance to automate maintenance tasks (update and restore from backups for example).

Backups

Backups are created automatically every 24 hours, and one is also captured whenever you stop the instance. Snapshots older than 5 days are cleaned up, with at least 2 always retained. You can create one manually anytime with Create Backup on the details page. To roll back, pick a backup in the Backups table and click Restore.

Restoring overwrites the instance’s current data with the backup. This cannot be undone — take a fresh backup first if you might need the current state.

HTTP API

Everything above is also available programmatically. Authenticate with your API key. Create an instance:

curl -X POST https://api.deepinfra.com/v1/agents \
  -H "Authorization: Bearer $DEEPINFRA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "my-agent",
    "agent_type_id": "openclaw",
    "plan_id": "standard"
  }'

List your instances:

curl "https://api.deepinfra.com/v1/agents?state=all" \
  -H "Authorization: Bearer $DEEPINFRA_TOKEN"

Start, stop, or update:

curl -X POST https://api.deepinfra.com/v1/agents/{instance_id}/start \
  -H "Authorization: Bearer $DEEPINFRA_TOKEN"

curl -X POST https://api.deepinfra.com/v1/agents/{instance_id}/stop \
  -H "Authorization: Bearer $DEEPINFRA_TOKEN"

curl -X POST https://api.deepinfra.com/v1/agents/{instance_id}/update \
  -H "Authorization: Bearer $DEEPINFRA_TOKEN"

Delete:

curl -X DELETE https://api.deepinfra.com/v1/agents/{instance_id} \
  -H "Authorization: Bearer $DEEPINFRA_TOKEN"

Other endpoints: GET /v1/agents/catalog (frameworks, plans, and current pricing), GET /v1/agents/{instance_id}/backups, POST /v1/agents/{instance_id}/backup, and POST /v1/agents/{instance_id}/backups/{backup_id}/restore. See the API Reference for full schemas.

FAQ

How many instances can I run? Up to 5 active instances per account. Where does my instance run? Instances run in us-west-2 by default. Accounts subject to EU data-protection rules are placed in eu-central-1. The region is shown on the instance details page. What happens to my data when I stop an instance? Nothing is lost — state is captured in a snapshot and restored when you start it again. Only the public IP changes. Can DeepInfra access my instance? DeepInfra retains administrative SSH access for automated maintenance (updates and backup restores for example). Why was my instance paused? Most likely it exceeded the fair-use network transfer threshold for its plan. Start it again from the dashboard once usage normalizes. What happens if my account is suspended? If your account is suspended — for example when your balance runs out — your instances are automatically stopped within a minute or two, and creating, starting, or restoring instances is blocked. Nothing is deleted: state is preserved the same way as a regular stop, and once your account is back in good standing you can start your instances again. Keep in mind that a running agent spends on inference on its own, so consider enabling Automatic Top-Up if you plan to leave it unattended. Where do I see what my agent is costing me? On the Usage page — compute appears as Hosted Agent, and the agent’s model calls appear as regular inference usage.

​Available frameworks

​Plans

​Billing

​Create an instance

​Instance lifecycle

​Manage an instance

​Backups

​HTTP API

​FAQ

Available frameworks

Plans

Billing

Create an instance

Instance lifecycle

Manage an instance

Backups

HTTP API

FAQ