Skip to main content
E2B provides isolated Linux VM sandboxes for AI agents that can be created, paused, resumed and killed via its SDKs and CLI. The following table shows what CostGraph runs on this provider.

​
Connect

Run the dispatcher with provider set to e2b and these variables:
  • E2B_API_KEY
Sandbox size comes from the template. Build a template with the size your jobs need and set it as providerTemplate. If you connected E2B for cost data, CostGraph’s dispatcher can start sandboxes with the key from your E2B integration. That key then needs the permissions in the next section as well.

​
Key and permissions

E2B_API_KEY is an E2B API key, found in the E2B console keys tab (https://console.e2b.dev/?tab=keys); the same key works for the SDKs and CLI. Keys are not scoped by permission: “every API key is scoped to exactly one project” (formerly team) and acts on all of that project’s sandboxes, templates and limits. No per-key permissions are documented. Sources: docs.e2b.dev: api key, docs.e2b.dev: projects, docs.e2b.dev: billing, docs.e2b.dev: sandbox, docs.e2b.dev: sandbox lifetime.

​
Limits

  • Max continuous runtime without pausing: Hobby 1 hour, Pro 24 hours; pausing resets it and paused sandboxes are kept indefinitely. (source)
  • Default sandbox timeout is 5 minutes and the default onTimeout is ‘kill’ (destructive); set timeoutMs/timeout or call setTimeout to extend. (source)
  • Max 8 vCPU / 8 GiB on Hobby (8+ on Pro via support), disk 10 GiB Hobby / 20+ GiB Pro; default 2 vCPU / 512 MiB; concurrent sandboxes Hobby 20, Pro 100-1,100. (source)
  • A single streaming connection is not guaranteed past one hour; reconnect with commands.connect(pid). (source)
  • EU region available on request for workspaces with a payment method. (source)