Skip to main content
Agent Sandbox charges for the vCPU and memory a sandbox uses while it runs, and for the storage that keeps templates, paused sandboxes and snapshots. This page covers what is metered, how the sandbox state changes the bill, and where to check usage and bills.

Billed resources

vCPU

Cores used times runtime, billed per second and shown in AGENT SANDBOX › Usage.

Memory

Allocated memory times runtime, billed per second and shown in AGENT SANDBOX › Usage.

Ephemeral storage

Included while running, retained as persistent storage when paused.

Persistent storage

Templates and snapshots, billed daily and shown in AGENT SANDBOX › Usage.
Model calls that an agent makes inside a sandbox are billed separately, at the model’s own rate.

Billing while paused

Once a sandbox is paused, vCPU and memory stop being billed. Only the persistent storage that retains the sandbox data is charged. A paused sandbox resumes with its state intact. A killed sandbox and its data are gone. To see how many sandboxes currently count toward the concurrency limit, read usage from the quota API. For the SDK calls, see Pause and resume a sandbox.

Where to check usage

AGENT SANDBOX › Usage shows the daily vCPU hours, memory hours and usage costs across all sandboxes; see Usage for what each figure covers and how it relates to the final bill.

Prices

Agent Sandbox prices

Unit prices for vCPU, memory and persistent storage.

Export a bill

Bill data can be viewed and exported as an .xlsx file.
1

Open the bill

Open Billing › Overview in the console.
2

Set the query

Set the time range and how the results are grouped.
3

Export the bill

Export the query results as an .xlsx file.

Overdue balance

If the balance cannot cover the bill, the team is overdue. While a team is overdue, new sandboxes cannot be started and running sandboxes are terminated. Overdue payments result in data loss.
Keep the balance sufficient for the workloads that run. Notification emails are sent after the team becomes overdue. Recharge promptly. Check the balance and top up in Billing › Overview.
Set up a low balance alert on the Billing › Overview page. When the balance drops below the alert threshold, a notification email is sent.
Before an overdue event, persist anything that cannot be lost:

Push code to Git

Save a snapshot

Copy files out

When the balance cannot cover a new sandbox, the API rejects the request and the SDK raises an exception. See Errors for the class and the message.

Control the cost of a task

Size the template to the workload

CPU and memory are set when the template is built.

Stop paying for idle time

Set an idle timeout, or pause sandboxes between steps.

Check what a task spent

AGENT SANDBOX › Usage shows the current day.
To pause a sandbox between steps, see Pause and resume a sandbox.
Last modified on November 19, 2026