Skip to main content
Sandbox0 provides AI agent sandboxes so you can give every user their own cloud computer. The following table shows what CostGraph runs on this provider. CI runners: no. AutoPilot compares runners by price, and this provider publishes no sandbox price.

​
Connect

Connect Sandbox0 on Integrations, and CostGraph starts sandboxes in your Sandbox0 account. You don’t run anything yourself.
  1. In CostGraph, go to Integrations > Sandbox > Sandbox0.
  2. Enter these fields:
    • API key (SANDBOX0_TOKEN, required): A team-scoped Sandbox0 API key.
  3. Click Connect.

​
Your own dispatcher

To keep the key out of CostGraph or reach a private network, run your own dispatcher instead. Set provider to sandbox0 and the preceding fields as environment variables, as described in Run your own dispatcher.

​
Key and permissions

SANDBOX0_TOKEN (or SANDBOX0_API_KEY) is a team-scoped Sandbox0 API key: “s0 auth login”, s0 team use <team-id>, then s0 apikey create --name ... --role developer --expires-in 30d --raw. Keys are team-scoped and carry a role, such as developer. Sandbox0 doesn’t document what each role permits. Sources: sandbox0.ai: get started, sandbox0.ai: pause resume, github.com: sandbox0.

​
Limits

  • Soft TTL (ttl) auto-pauses, hard TTL (hard_ttl) deletes state; both default 0 (disabled), so a sandbox can run as long as needed. (source)
  • Sandbox0 Cloud auto-pauses running sandboxes when unpaid usage reaches 10% of the last top-up (filesystem-only checkpoint; processes and memory lost). (source)
  • vCPU/RAM caps, regions, architecture: not documented. (source)