E2B compatibility

Point the SDK at rent.dev

export E2B_DOMAIN=rent.dev
export E2B_API_KEY=e2b_<the 64 hex characters of your rent.dev key>

import { Sandbox } from "e2b";

const sandbox = await Sandbox.create("base");
const result = await sandbox.commands.run("echo hello");
console.log(result.stdout);
await sandbox.kill();

A rent.dev key works in either spelling: rent_sk_ plus 64 hex characters, or e2b_ plus the same 64. The second is there for tools that check the prefix. Get a key with POST /v1/accounts; see the agent quickstart.

Sandbox ports are served at https://{port}-{sandboxID}.rent.dev, which is where sandbox.getHost(port) points.

What it costs

A sandbox created through the SDK is a rent.dev sandbox: it draws on the prepaid balance by the second, at rent.dev's own price. Creating one takes a hold first, so a short balance answers 402 before anything starts.

Errors keep E2B's shape, {code, message}, so the SDK reads them as it reads E2B's own. A refusal from rent.dev adds its Problem code as error_code, and a 402 keeps balance_required_micros and the topup links:

{
  "code": 402,
  "message": "Insufficient balance",
  "error_code": "insufficient_balance",
  "balance_required_micros": 9075,
  "topup": {
    "checkout_url": "https://api.rent.dev/pay/<token>",
    "x402_url": "https://api.rent.dev/v1/credits/x402?amount_usd=0.009075"
  }
}

rent.dev options through metadata

Two metadata keys on create carry what the E2B API has no field for:

Keys starting rentdev_ are reserved for rent.dev's own labels and are dropped from a request.

Known gaps

• Template builds work from an image or another template with command steps. A copy() step needs a file upload, and uploads are closed.
• volumeMounts, iam, mcp and an egress proxy are refused on create with 400 unsupported_parameter.
• A pause always keeps memory. Asking for a filesystem-only pause is refused.
• cpuCount must match the template's; a sandbox cannot be resized on create or resume.
• getMetrics is not supported.
• These paths reach a sandbox that runs on E2B's API: rent.dev's own, or one on your own E2B key. A sandbox placed on your own Vercel token answers 404 here. Manage it through /v1, where it cannot be paused or resumed and has no log stream; the table lists what each vendor can do.
• Team, node, admin, volume, secret, API-key and webhook routes are not served. They answer 404.

Measured 2026-11-11 18:49 UTC with npm:e2b@2.46.1 and 2.63.0, npm:@e2b/code-interpreter@2.9.1, pypi:e2b@2.46.0 and 2.63.0, pypi:e2b-code-interpreter@2.11.9.

Sandbox routes

Template routes

Request parameters

SDK calls

Measured behaviour

Routes not served

The spec this is measured against

The route rows come from e2b-dev/runtime at commit f3eee1ae84e2b1d893bc7806280a9a33f2e9001e, whose spec lists 126 routes.