Skip to main content
Compute is metered from the seconds a computer actually ran, booked against your budget at the end of each turn and drawn from the organization’s real-USD balance. This page is the reference for the caps and the exact per-unit rates.
Every rate on this page is the price you pay — the number booked to the ledger and reported on your spend breakdown. Model inference is priced separately; see Model router & inference.

​
The compute meter

While a computer is running, it is metered per second on its provisioned resources — vCPU and memory. There is no creation fee, and disk is not metered: the boot disk is inside the allowance the computer ships with. Billing granularity is per-second. A session’s computer is 1 vCPU / 1 GiB, so a full hour of running time is $0.0504 + $0.0162 = $0.0666. Because idle maps onto the runtime’s wake/sleep cycle, a computer waiting between turns is metered for nothing at all — the mechanism behind Vetta’s low cost on multi-hour tasks.

​
The browser

The optional browser carries no charge of its own. Browser time is not metered, there is no browser line on the ledger and no browser component on your spend breakdown — what a browsing agent pays for is the tokens it spends driving the browser and the computer time of the session driving it. Its limits are still real: see the per-session timeout and the concurrency cap below.

​
Concurrency

Every computer counts toward your organization’s concurrency cap the entire time it is not destroyed — running, sleeping, and parked all occupy a slot; only a destroy frees one. The defaults below are per organization and are raised on request — they are safety rails, not hard product ceilings.

​
Boot & wake latency

Only cold boots pay the full provisioning cost; the wake/sleep cycle the runtime uses between turns is near-instant, which is what makes idle cheap.
The fully virtualized isolate mode (mode: "isolate", coming soon) targets near-instant boot and near-zero idle; the numbers above describe the micro-VM that ships today.

​
Limits

max_duration_hours bounds a computer’s total lifetime from create to destroy — it is wall-clock, not billed compute-seconds, so a computer that sleeps most of that window still hits the ceiling on schedule. Only running seconds are metered; the ceiling is a safety cap on how long the computer may exist.
A computer is auto-destroyed when it exceeds its max runtime or the organization’s balance reaches zero. Persist anything you need to keep with publish_file or a volume before then.

​
Inspecting spend

Compute spend appears as the computer component of the agent’s spend breakdown and as a line item on the organization ledger.
CLI
Spend is reported on the wire as integer micro-USD (1 USD = 1_000_000); the CLI renders dollars for humans.

Back to the computer overview

The full computer surface at a glance.