Skip to main content
BoxCompute provides isolated VM sandboxes inside account-owned workspaces that agents create and run commands in through a single account-scoped API. The following table shows what CostGraph runs on this provider.

​
Connect

Run the dispatcher with provider set to boxcompute and these variables:
  • BOXCOMPUTE_API_KEY
  • BOXCOMPUTE_WORKSPACE_ID
To see what BoxCompute costs, connect the BoxCompute integration.

​
Key and permissions

BOXCOMPUTE_API_KEY is a BoxCompute API key (bc_live_…), created at app.boxcompute.ai/api-keys via New API key > Create key; shown once. BOXCOMPUTE_WORKSPACE_ID is the id of a workspace owned by the account (listable with sandbox:read). Keys have scopes: workspace:create, sandbox:read, sandbox:create, sandbox:execute, sandbox:delete, usage:read, email:send. CostGraph needs sandbox:create, sandbox:read (inspect/list), sandbox:execute and sandbox:delete. However, keys created on the API keys page get all seven scopes and there is no scope picker, so in practice a dashboard key has full account access. Sources: boxcompute.ai: docs, boxcompute.ai: api keys, boxcompute.ai: sandboxes, boxcompute.ai: execute.

​
Limits

  • Execute timeoutSeconds 1-900 (default 120); maxOutputBytes up to 1,048,576. (source)
  • A running VM stops 30 minutes after the last API call that used it, and requests sleep after about 42 hours of continuous uptime (disk kept, processes stop). (source)
  • VM Sandboxes are labelled Beta; root disk 30 GiB; max 10 workspaces per account; each run billed at least 60 s. Sizes, regions and architecture are not documented. (source)