E2B vs Blaxel

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   E2B✓fullprobed9/10

   E2B serves a live llms.txt index (HTTP 200) and .md-suffixed doc pages explicitly designed for agent consumption, with the quickstart page itself pointing agents to the llms.txt index. missing for 10: no independent/community confirmation that agents actually consume llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.e2b.dev/llms.txt # E2B Docs - [E2B Documentation](https://docs.e2b.dev/index.md) - [Running your f…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.e2b.dev/quickstart.md > ## Documentation Index > Fetch the complete documentation index at: https://…”

   proof ↗⚑ flag

   Blaxel✓fullprobed9/10

   A probe directly confirms llms.txt is live and returns HTTP 200 with a structured documentation summary at docs.blaxel.ai/llms.txt, and Blaxel also ships agent-oriented skills/MCP docs for agents to consume. Missing for 10: no independent third-party confirmation that agents actually consume/parse this llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.blaxel.ai/llms.txt # Documentation > Blaxel documentation: cloud sandboxes, AI agent hosting, MCP …”
   • [claimed-docs] “Install the Blaxel skill to give your agent the ability to deploy AI agents, create sandboxes for code execution, host MCP servers, run batc…”
   • [claimed-docs] “The open source Blaxel migration skill gives agents the knowledge they need to migrate sandbox code from other providers to Blaxel.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to E2B
   E2B✓fullclaimed8/10

   E2B has a documented CLI, SDK, and non-interactive auth mode explicitly recommended for CI/CD pipelines, servers, and containers, plus scriptable sandbox lifecycle (create, exec with --background, shutdown, snapshot) and webhooks for lifecycle events — all consistent with headless/CI automation. missing for 10: no independent third-party report of a real CI pipeline using E2B, and no explicit CI provider integration examples (e.g., GitHub Actions workflow snippet).

   • [claimed-docs] “This is the recommended option for non-interactive environments like CI/CD pipelines, servers, and containers. Set a single environment vari…”
   • [claimed-docs] “E2B CLI is a command line tool that allows you to manage and interact with sandboxes and templates.”
   • [claimed-docs] “Use the `--background` flag to run a command in the background and return immediately.”
   • [claimed-docs] “You can shutdown single or all running sandboxes with the E2B CLI.”
   • [claimed-docs] “Webhooks provide a way for notifications to be delivered to an external web server whenever certain sandbox lifecycle events occur.”
   • [claimed-docs] “If you need an explicit configuration — for example several API keys, teams, or BYOC or self-hosted deployments — create an `E2B` client and…”
   • [claimed-docs] “If you need an explicit configuration — for example several API keys, teams, or [BYOC or self-hosted deployments](/byoc) in a single process…”

   proof ↗⚑ flag

   Blaxel~partialprobed6/10

   Blaxel documents CLI with API keys usable in CI, and explicitly points to an official GitHub Action for CI pipeline integration, plus batch Jobs for automation-style workloads. However, there's no evidence of a full headless CI walkthrough, no independent corroboration, and no explicit CI examples for deploying/testing agents beyond the brief GitHub Action mention. Missing for 10: detailed CI workflow examples/docs, independent hands-on confirmation of CI usage, broader automation guidance beyond batch jobs.

   • [claimed-docs] “API keys can be used in the Blaxel APIs, CLI and SDK.”
   • [claimed-docs] “The easiest way to integrate the Blaxel CLI into a CI pipeline is with the official Blaxel GitHub Action.”
   • [claimed-docs] “Jobs allow you to run many AI tasks in parallel using batch processing.”
   • [probe] “official CLI documented at https://docs.blaxel.ai/cli-reference/introduction”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Blaxel
   E2B—none0/10

   E2B is a sandbox/code-execution infrastructure product (not itself an agent), so an official MCP server exposing its sandbox tools to agents is a fair, applicable axis. The evidence pack documents SDKs, CLI, templates, and LLM tool-use integration (e2b-docs-32) but never mentions an MCP server, official MCP integration, or MCP protocol support anywhere.

   • [claimed-docs] “E2B can work with any LLM and AI framework. The easiest way to connect an LLM to E2B is to use the tool use capabilities of the LLM”
   • [claimed-docs] “E2B CLI is a command line tool that allows you to manage and interact with sandboxes and templates.”
   • [github] “E2B is an open-source infrastructure that allows you to run AI-generated code in secure isolated sandboxes in the cloud.”

   proof ↗⚑ flag

   Blaxel✓fullprobed7/10

   Blaxel documents that every sandbox is exposed via an official MCP server enabling agents to operate it via tool calls, and it offers a serverless 'MCP Server Hosting' service for hosting remote MCP servers, with a dedicated docs page confirmed by probe. This is a platform (not itself an agent), so the connect-via-official-MCP-server axis clearly applies and is met by first-party evidence. missing for 10: independent/hands-on confirmation of connecting an external agent to these MCP servers, and more detail on the protocol/setup beyond the docs summary.

   • [claimed-docs] “Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.”
   • [claimed-docs] “MCP Server Hosting is a serverless computing service that allows you to host remote MCP servers without having to manage infrastructure.”
   • [probe] “official MCP server documented at https://docs.blaxel.ai/skills-mcp”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to E2B
   E2B✓fullprobed8/10

   E2B ships an official CLI documented extensively (create/connect/exec/list/shutdown/snapshot/auth/metrics commands) covering sandbox lifecycle management, well-suited for AI-native agentic workflows. missing for 10: independent/hands-on community validation of the CLI itself (community evidence only covers SDK usage, not CLI) and no evidence of CLI-specific agent integration examples.

   • [claimed-docs] “E2B CLI is a command line tool that allows you to manage and interact with sandboxes and templates.”
   • [claimed-docs] “You can create a sandbox and connect an interactive terminal to it.”
   • [claimed-docs] “This will return running sandboxes, you can specify `--state` to get paused or both.”
   • [claimed-docs] “You can shutdown single or all running sandboxes with the E2B CLI.”
   • [claimed-docs] “You can manage sandbox snapshots with the `e2b sandbox snapshot` (alias `snap`) commands.”
   • [claimed-docs] “If your E2B account has access to more than one project, you can choose which one the CLI uses”
   • [claimed-docs] “This is the recommended option for non-interactive environments like CI/CD pipelines, servers, and containers. Set a single environment vari…”
   • [claimed-docs] “e2b sandbox create <template>”
   • [claimed-docs] “Unlike the `create` command, `connect` does not kill the sandbox when you disconnect.”
   • [claimed-docs] “Use the `--background` flag to run a command in the background and return immediately.”
   • [claimed-docs] “To shutdown all running sandboxes, run the following command:”
   • [claimed-docs] “You can name the snapshot template with the `--name` flag. If a template with that name already exists, it is reused.”
   • [probe] “official CLI documented at https://docs.e2b.dev/cli”

   proof ↗⚑ flag

   Blaxel✓fullprobed7/10

   Blaxel has an official CLI documented at a dedicated CLI reference, integrable into CI via a GitHub Action, and used for API key auth alongside SDK/API — consistent with AI-native, agentic workflows (deploying agents, sandboxes, MCP servers, jobs). Missing for 10: no independent/hands-on corroboration of CLI usage, no detailed command list or examples in the evidence pack beyond the reference page's existence.

   • [probe] “official CLI documented at https://docs.blaxel.ai/cli-reference/introduction”
   • [claimed-docs] “API keys can be used in the Blaxel APIs, CLI and SDK.”
   • [claimed-docs] “The easiest way to integrate the Blaxel CLI into a CI pipeline is with the official Blaxel GitHub Action.”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to E2B
   E2B✓fullprobed8/10

   E2B ships extensive documented SDK/CLI APIs (Sandbox.create, files.read/write, commands.run, timeouts, metrics, snapshots, webhooks) with quickstart and reference docs, and explicit LLM/agent integration guides (connect-llms, coding-agents), demonstrating a fully documented public API surface for AI-native use. Missing for 10: no discoverable formal OpenAPI/swagger spec (probe found 404s across candidate paths) and no independent third-party audit of API completeness beyond vendor docs/community anecdotes.

   • [claimed-docs] “const sbx = await Sandbox.create() // Creates a persistent sandbox session const execution = await sbx.runCode('print("hello world")')”
   • [claimed-docs] “You can write single files to the sandbox filesystem using the `files.write()` method.”
   • [claimed-docs] “You can run terminal commands inside the sandbox using the `commands.run()` method.”
   • [claimed-docs] “E2B CLI is a command line tool that allows you to manage and interact with sandboxes and templates.”
   • [claimed-docs] “If you need an explicit configuration — for example several API keys, teams, or BYOC or self-hosted deployments — create an `E2B` client and…”
   • [claimed-docs] “E2B can work with any LLM and AI framework. The easiest way to connect an LLM to E2B is to use the tool use capabilities of the LLM”
   • [claimed-docs] “Run AI coding agents like Claude Code, Codex, and Amp in secure E2B sandboxes with full terminal, filesystem, and git access.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.e2b.dev/openapi.json, https://docs.e2b.dev/swagger.json, https://docs.e2b.dev/api/opena…”

   proof ↗⚑ flag

   Blaxel~partialprobed5/10

   Docs confirm a public API exists and that API keys can drive it (used across CLI, SDK, and API) and CLI reference documentation is available, but a dedicated public API reference/OpenAPI spec could not be located (all openapi.json/swagger.json paths returned 404), so the story is only partially evidenced. missing for 10: a discoverable OpenAPI/API reference doc, hands-on example of calling the API directly, independent confirmation of API completeness.

   • [claimed-docs] “API keys can be used in the Blaxel APIs, CLI and SDK.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.blaxel.ai/openapi.json, https://docs.blaxel.ai/swagger.json, https://docs.blaxel.ai/api…”
   • [probe] “official CLI documented at https://docs.blaxel.ai/cli-reference/introduction”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   E2B—none0/10

   Evidence shows E2B supports multiple API keys per team/project (e2b-docs-30, e2b-docs-31, e2b-docs-34, e2b-docs-35) but no documentation of scoped or least-privilege permissions (e.g., read-only, sandbox-restricted, rate-limited keys) that would let an AI-native user issue a restricted credential to an agent.

   • [claimed-docs] “If you need an explicit configuration — for example several API keys, teams, or BYOC or self-hosted deployments — create an `E2B` client and…”
   • [claimed-docs] “If your E2B account has access to more than one project, you can choose which one the CLI uses”
   • [claimed-docs] “If you need an explicit configuration — for example several API keys, teams, or [BYOC or self-hosted deployments](/byoc) in a single process…”
   • [claimed-docs] “This is the recommended option for non-interactive environments like CI/CD pipelines, servers, and containers. Set a single environment vari…”

   proof ↗⚑ flag

   Blaxel—none0/10

   Evidence shows Blaxel issues generic API keys usable across its APIs, CLI, and SDK (blaxel-docs-12), and preview URLs can require an access token (blaxel-docs-8), but there is no documentation of scoping, role-based permissions, or least-privilege credential configuration for agents specifically.

   • [claimed-docs] “API keys can be used in the Blaxel APIs, CLI and SDK.”
   • [claimed-docs] “When you create a private preview URL a token is required to access the URL.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to E2B
   E2B✓fullprobed8/10

   E2B ships official SDKs (JS/Python) with extensive first-party docs covering sandbox creation, code execution, filesystem, commands, metrics, persistence, and explicit guidance for connecting LLMs/agent frameworks (e2b-docs-1,7,8,32,42-44), plus a CLI (e2b-docs-9, e2b-probe-4) and community confirmation of Python/TS SDK availability (e2b-comm-1). missing for 10: broader independent/hands-on validation beyond one HN thread, and no discoverable OpenAPI spec for programmatic SDK generation (e2b-probe-3).

   • [claimed-docs] “const sbx = await Sandbox.create() // Creates a persistent sandbox session const execution = await sbx.runCode('print("hello world")')”
   • [claimed-docs] “You can write single files to the sandbox filesystem using the `files.write()` method.”
   • [claimed-docs] “You can run terminal commands inside the sandbox using the `commands.run()` method.”
   • [claimed-docs] “E2B CLI is a command line tool that allows you to manage and interact with sandboxes and templates.”
   • [claimed-docs] “E2B can work with any LLM and AI framework. The easiest way to connect an LLM to E2B is to use the tool use capabilities of the LLM”
   • [claimed-docs] “E2B provides a pre-built `claude` template with Claude Code already installed.”
   • [claimed-docs] “With the E2B backend, the agent's built-in tools all execute inside an isolated sandbox instead of your machine”
   • [claimed-docs] “your agent's code runs in an isolated Firecracker microVM instead of your server, with a real Debian toolchain, pause/resume persistence, an…”
   • [community] “E2B does support Python, AgentKit is only available in TypeScript for now.”
   • [probe] “official CLI documented at https://docs.e2b.dev/cli”

   proof ↗⚑ flag

   Blaxel~partialclaimed3/10

   Only indirect evidence exists that an SDK exists (API keys usable in "Blaxel APIs, CLI and SDK"), but there is no dedicated SDK documentation, language coverage, install instructions, or examples in the pack. missing for 10: dedicated SDK docs/reference, supported languages, code examples, independent corroboration of SDK usage.

   • [claimed-docs] “API keys can be used in the Blaxel APIs, CLI and SDK.”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to E2B
   E2B✓fullclaimed6/10

   E2B docs explicitly describe webhooks that deliver notifications to an external server on sandbox lifecycle events, directly matching the story. Missing for 10: detailed docs on event types/payload schema, setup/configuration steps, and independent/community corroboration of webhook usage.

   • [claimed-docs] “Webhooks provide a way for notifications to be delivered to an external web server whenever certain sandbox lifecycle events occur.”

   proof ↗⚑ flag

   Blaxel—none0/10

   No evidence in the pack mentions webhooks, event subscriptions, or push notifications from Blaxel; documentation covers sandboxes, MCP hosting, jobs, and CLI/API but nothing about webhook subscription mechanisms.

   ⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   E2B~partialclaimed5/10

   E2B provides persistent, resumable sandboxes, background command execution (--background flag), webhooks for lifecycle events, and long-running session support (up to 24h, pause/resume), which are building blocks for autonomous background automation. However, there's no evidence of a native scheduler/cron, no first-party 'automation' orchestration layer, and no documented trigger system beyond webhooks — the user must build the autonomy logic themselves using an external agent/LLM. missing for 10: native scheduling/cron or trigger orchestration, evidence of fully autonomous multi-step agent loops running unattended, independent case studies of long-running unattended automations.

   • [claimed-docs] “Pause a sandbox and resume it later from the exact state it was in, including the filesystem and the memory, so running processes and loaded…”
   • [claimed-docs] “A paused sandbox is kept indefinitely with no automatic deletion.”
   • [claimed-docs] “Sandboxes can run continuously for up to 24 hours (Pro) or 1 hour (Base). For longer workloads, use pause and resume”
   • [claimed-docs] “Webhooks provide a way for notifications to be delivered to an external web server whenever certain sandbox lifecycle events occur.”
   • [claimed-docs] “Use the `--background` flag to run a command in the background and return immediately.”
   • [claimed-docs] “Run AI coding agents like Claude Code, Codex, and Amp in secure E2B sandboxes with full terminal, filesystem, and git access.”

   proof ↗⚑ flag

   Blaxel~partialclaimed5/10

   Blaxel supports background-running infrastructure like Jobs for batch processing, scale-to-zero agents/sandboxes, and MCP-server hosting, which can enable autonomous background workloads, but there's no explicit documentation of a scheduling/trigger/automation-workflow feature (e.g., cron-like triggers or event-based automation) for setting up self-running automations. missing for 10: explicit scheduler/trigger mechanism for autonomous automations, independent/hands-on evidence of autonomous background execution, and clear docs describing 'automation' as a first-class concept rather than inferred from batch jobs and hosting.

   • [claimed-docs] “Jobs allow you to run many AI tasks in parallel using batch processing.”
   • [claimed-docs] “MCP Server Hosting is a serverless computing service that allows you to host remote MCP servers without having to manage infrastructure.”
   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”
   • [claimed-docs] “Agent Drive is a distributed filesystem that can be mounted to multiple sandboxes or agents at any time, including while they are already ru…”

   proof ↗⚑ flag

2. ai-native userOperate the product with natural-language commands

   weight 2 · round to Blaxel
   E2B~partialclaimed5/10

   E2B's own interface is programmatic (SDK calls like Sandbox.create(), files.read(), commands.run()) and a CLI (e2b-docs-9), not a natural-language command surface; however docs explicitly describe connecting LLMs via tool-use so an AI agent can drive E2B through natural-language-triggered function calls (e2b-docs-32, e2b-docs-28, e2b-docs-43). This shows AI-native operation is possible only indirectly through an LLM/agent layer, not as a built-in NL command mode of the product itself. missing for 10: no first-party NL chat/command interface for E2B itself, no evidence of a natural-language CLI or prompt-driven control plane, only indirect LLM tool-use integration documented.

   • [claimed-docs] “E2B can work with any LLM and AI framework. The easiest way to connect an LLM to E2B is to use the tool use capabilities of the LLM”
   • [claimed-docs] “Run AI coding agents like Claude Code, Codex, and Amp in secure E2B sandboxes with full terminal, filesystem, and git access.”
   • [claimed-docs] “With the E2B backend, the agent's built-in tools all execute inside an isolated sandbox instead of your machine”
   • [claimed-docs] “E2B CLI is a command line tool that allows you to manage and interact with sandboxes and templates.”

   proof ↗⚑ flag

   Blaxel~partialprobed6/10

   Blaxel offers an installable 'skill' that lets an agent deploy agents, create sandboxes, host MCP servers, and run jobs via simple prompts with zero code, directly supporting natural-language operation. However, this is scoped to agent-orchestration skills rather than a full natural-language interface across the entire product surface (e.g., CLI/dashboard operations still require explicit commands). Missing for 10: independent/hands-on verification of the skill's natural-language reliability, and evidence that all major product functions (not just deploy/sandbox/mcp/jobs) are controllable via natural language.

   • [claimed-docs] “Install the Blaxel skill to give your agent the ability to deploy AI agents, create sandboxes for code execution, host MCP servers, run batc…”
   • [claimed-docs] “The open source Blaxel migration skill gives agents the knowledge they need to migrate sandbox code from other providers to Blaxel.”
   • [probe] “official MCP server documented at https://docs.blaxel.ai/skills-mcp”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   E2B—none0/10

   Evidence shows extensive static documentation with code snippets (e2b-docs-1, e2b-docs-2, etc.) but no evidence of an interactive, runnable API reference — the probe explicitly found no OpenAPI/Swagger spec (e2b-probe-3), and no playground or 'try it' console is mentioned anywhere in the pack.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.e2b.dev/openapi.json, https://docs.e2b.dev/swagger.json, https://docs.e2b.dev/api/opena…”
   • [claimed-docs] “const sbx = await Sandbox.create() // Creates a persistent sandbox session const execution = await sbx.runCode('print("hello world")')”
   • [claimed-docs] “We’ll write the minimal code for starting Sandbox, executing Python inside it and listing all files inside the root directory.”

   proof ↗⚑ flag

   Blaxel—none0/10

   The probe explicitly found no OpenAPI/Swagger spec at any candidate path (404s), and no evidence exists of an interactive API reference with runnable examples—only static markdown docs and CLI/skills references are documented.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.blaxel.ai/openapi.json, https://docs.blaxel.ai/swagger.json, https://docs.blaxel.ai/api…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   E2B—none0/10

   E2B exposes SDKs and a CLI, but active probing found no OpenAPI/swagger spec at any standard location (all candidate paths returned 404), and no documentation page references a machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.e2b.dev/openapi.json, https://docs.e2b.dev/swagger.json, https://docs.e2b.dev/api/opena…”

   proof ↗⚑ flag

   Blaxel—none0/10

   The probe explicitly checked common OpenAPI spec locations and found all returned 404, and no documentation item references a downloadable machine-readable API spec; only an llms.txt for documentation is present.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.blaxel.ai/openapi.json, https://docs.blaxel.ai/swagger.json, https://docs.blaxel.ai/api…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.blaxel.ai/llms.txt # Documentation > Blaxel documentation: cloud sandboxes, AI agent hosting, MCP …”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to E2B
   E2B✓fullclaimed8/10

   E2B provides fully isolated, ephemeral cloud sandboxes (Firecracker microVMs) for running AI-generated code, with no connection to production systems — sandboxes are created fresh from templates, have their own filesystem/network, and can be killed or auto-expire, ensuring test isolation. Persistence/pause-resume and metrics further support safe iterative testing without touching real data. Missing for 10: explicit documentation or case study contrasting sandbox vs production data separation, and independent/hands-on verification beyond vendor docs.

   • [claimed-docs] “const sbx = await Sandbox.create() // Creates a persistent sandbox session const execution = await sbx.runCode('print("hello world")')”
   • [claimed-docs] “Pause a sandbox and resume it later from the exact state it was in, including the filesystem and the memory, so running processes and loaded…”
   • [claimed-docs] “You can shutdown the sandbox any time even before the timeout is up by calling the `kill` method.”
   • [claimed-docs] “Every sandbox has outbound internet access by default. Control and restrict it with a simple on/off switch or fine-grained allow and deny li…”
   • [claimed-docs] “E2B templates allow you to define custom sandboxes. You can define the base image, environment variables, files to copy, commands to run, an…”
   • [github] “E2B is an open-source infrastructure that allows you to run AI-generated code in secure isolated sandboxes in the cloud.”
   • [claimed-docs] “your agent's code runs in an isolated Firecracker microVM instead of your server, with a real Debian toolchain, pause/resume persistence, an…”

   proof ↗⚑ flag

   Blaxel✓fullclaimed7/10

   Blaxel's core product is isolated sandbox environments for code execution, separate from production infra, with dedicated MCP-controlled sandbox instances, custom templates, and preview URLs, clearly enabling safe testing without touching production data. missing for 10: no explicit documentation contrasting sandbox vs production data isolation guarantees, and no independent/hands-on verification of data isolation beyond vendor docs.

   • [claimed-docs] “Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”
   • [claimed-docs] “Agent Drive is a distributed filesystem that can be mounted to multiple sandboxes or agents at any time, including while they are already ru…”
   • [claimed-docs] “When you create a private preview URL a token is required to access the URL.”
   • [claimed-docs] “Install the Blaxel skill to give your agent the ability to deploy AI agents, create sandboxes for code execution, host MCP servers, run batc…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   E2B—none0/10

   The evidence pack covers SDK usage, CLI commands, sandbox lifecycle, and self-hosting, but contains no mention of API versioning scheme, changelog, or a documented deprecation policy; the openapi probe even returned 404s. This is a fair axis for an API-first product, but no evidence supports it.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.e2b.dev/openapi.json, https://docs.e2b.dev/swagger.json, https://docs.e2b.dev/api/opena…”

   proof ↗⚑ flag

   Blaxel—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; the OpenAPI spec probe even returned 404s, and no docs mention version history or deprecation timelines.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.blaxel.ai/openapi.json, https://docs.blaxel.ai/swagger.json, https://docs.blaxel.ai/api…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Blaxel
   E2B~partialclaimed5/10

   E2B supports several bulk-adjacent capabilities: up to 100 concurrent sandboxes, writing multiple files at once, listing all sandboxes, and shutting down single or all running sandboxes via CLI. However there is no unified batch/bulk API (e.g., no evidence of submitting a list of code executions or files to process as one bulk call) — bulk behavior is assembled from separate CLI/SDK primitives rather than a first-class bulk-operations feature. Missing for 10: a documented batch execution or bulk-processing API, evidence of bulk operations on non-sandbox resources (e.g., bulk template management), and independent/hands-on validation of bulk workflows at scale.

   • [claimed-docs] “Up to 24-hour sandbox session length Up to 100 concurrently running sandboxes”
   • [claimed-docs] “You can also write multiple files to the sandbox.”
   • [claimed-docs] “This will return running sandboxes, you can specify `--state` to get paused or both.”
   • [claimed-docs] “You can shutdown single or all running sandboxes with the E2B CLI.”
   • [claimed-docs] “To shutdown all running sandboxes, run the following command:”
   • [claimed-docs] “Use the `--background` flag to run a command in the background and return immediately.”

   proof ↗⚑ flag

   Blaxel~partialclaimed6/10

   Blaxel's Jobs feature explicitly supports running many AI tasks in parallel via batch processing, and the Blaxel skill can invoke batch jobs via simple prompts, showing bulk-operation capability for AI-native users. However, the evidence gives no detail on limits, monitoring, or how a user would trigger operations across a large item set (e.g., bulk API endpoints), nor any independent/hands-on validation of batch performance. Missing for 10: concrete batch API/CLI examples, scale limits, and independent corroboration of bulk job execution.

   • [claimed-docs] “Jobs allow you to run many AI tasks in parallel using batch processing.”
   • [claimed-docs] “Install the Blaxel skill to give your agent the ability to deploy AI agents, create sandboxes for code execution, host MCP servers, run batc…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to E2B
   E2B~partialclaimed3/10

   E2B offers webhooks that deliver notifications for sandbox lifecycle events, which is a minimal building block for event-triggered automation, but there is no evidence of an actual rule-engine (defining conditional actions that execute automatically) beyond forwarding notifications to an external server. missing for 10: built-in conditional rule definitions, in-product automatic action execution, and any hands-on evidence of the webhook mechanism working end-to-end.

   • [claimed-docs] “Webhooks provide a way for notifications to be delivered to an external web server whenever certain sandbox lifecycle events occur.”

   proof ↗⚑ flag

   Blaxel—none0/10

   Blaxel's evidence covers deployment, sandboxes, MCP hosting, batch jobs, and scale-to-zero infrastructure, but nothing describes a rules/trigger engine where users define conditions that automatically fire actions on events (e.g., webhooks, event-based automation rules). Since this is a plausible capability for an agent-hosting platform, absence of evidence means 'none' rather than 'na'.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   E2B—none0/10

   E2B provides sandbox creation, execution, persistence (pause/resume), and lifecycle webhooks, but nothing in the evidence pack describes a native scheduler, cron-like trigger, or recurring workflow mechanism — scheduling would have to be built by the user via external tooling. This axis is fair for an automation-focused sandbox platform, so absence of evidence means 'none' rather than 'na'.

   • [claimed-docs] “Pause a sandbox and resume it later from the exact state it was in, including the filesystem and the memory, so running processes and loaded…”
   • [claimed-docs] “A paused sandbox is kept indefinitely with no automatic deletion.”
   • [claimed-docs] “Webhooks provide a way for notifications to be delivered to an external web server whenever certain sandbox lifecycle events occur.”
   • [claimed-docs] “When you call the set timeout method, the sandbox timeout will be reset to the new value that you specified.”

   proof ↗⚑ flag

   Blaxel—none0/10

   Blaxel documents one-off batch 'Jobs' for parallel AI task processing (blaxel-docs-10) but no evidence shows support for recurring/scheduled triggers, cron-like scheduling, or workflow orchestration over time. missing for 10: scheduling/cron mechanism, recurring trigger configuration, workflow automation docs.

   • [claimed-docs] “Jobs allow you to run many AI tasks in parallel using batch processing.”

   proof ↗⚑ flag

Agent workloads

1. ai-native userRun coding agents like Claude Code or Codex inside the sandbox following the vendor's own recipe

   weight 2 · round to E2B
   E2B✓fullclaimed8/10

   E2B provides a dedicated vendor recipe ('Run AI coding agents like Claude Code, Codex, and Amp in secure E2B sandboxes with full terminal, filesystem, and git access') and a pre-built `claude` template with Claude Code already installed, plus similar guides for other agent frameworks. This is a first-party documented recipe with concrete setup instructions. Missing for 10: independent/hands-on confirmation that Codex specifically runs smoothly (community evidence only discusses a different agent framework's rough edges, not Claude Code/Codex directly), and no third-party benchmark of the recipe's reliability.

   • [claimed-docs] “Run AI coding agents like Claude Code, Codex, and Amp in secure E2B sandboxes with full terminal, filesystem, and git access.”
   • [claimed-docs] “E2B provides a pre-built `claude` template with Claude Code already installed.”
   • [claimed-docs] “With the E2B backend, the agent's built-in tools all execute inside an isolated sandbox instead of your machine”
   • [claimed-docs] “your agent's code runs in an isolated Firecracker microVM instead of your server, with a real Debian toolchain, pause/resume persistence, an…”

   proof ↗⚑ flag

   Blaxel—none0/10

   The evidence describes Blaxel sandboxes, MCP exposure, skills, and job/batch features, but nowhere mentions a documented recipe or guide for running Claude Code or Codex specifically inside a Blaxel sandbox. Missing for 10: any vendor recipe/tutorial naming Claude Code or Codex, or a hands-on report of doing so.

   • [claimed-docs] “Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”
   • [claimed-docs] “Install the Blaxel skill to give your agent the ability to deploy AI agents, create sandboxes for code execution, host MCP servers, run batc…”

   proof ↗⚑ flag

Workloads

1. developerRun a headless browser or full desktop environment inside the sandbox

   weight 2 · round to E2B
   E2B~partialclaimed6/10

   E2B's GitHub README confirms a separate 'Desktop SDK' providing mouse, keyboard, screenshot, application, and desktop streaming APIs for full desktop environments, but this is an add-on SDK rather than a built-in feature of the core Sandbox class documented elsewhere. There's no first-party doc page (e.g., under docs.e2b.dev) detailing headless browser support or code examples for it. missing for 10: dedicated docs/quickstart for the Desktop SDK, headless browser (e.g., Chromium/Playwright) usage examples, independent hands-on confirmation of desktop streaming reliability.

   • [github] “For mouse, keyboard, screenshot, application, and desktop streaming APIs, install the Desktop SDK”

   proof ↗⚑ flag

   Blaxel—none0/10

   Evidence describes sandboxes for code execution, MCP server exposure, filesystem mounting, and batch jobs, but no mention of headless browser support or full desktop/GUI environment capability inside a sandbox.

   ⚑ flag

2. developerAttach GPUs to sandboxed workloads

   weight 2 · round drawn
   E2B—none0/10

   No evidence anywhere in the pack mentions GPU support, GPU attachment, or GPU-enabled sandboxes; docs only reference customizable CPU & RAM, disk, and memory metrics. This is a fair question for a sandbox/compute infrastructure product, but nothing indicates GPU capability is offered.

   • [claimed-docs] “Customize your Sandbox CPU & RAM”
   • [claimed-docs] “Up to 24-hour sandbox session length Up to 100 concurrently running sandboxes”
   • [claimed-docs] “The sandbox metrics allows you to get information about the sandbox's CPU, memory and disk usage.”

   proof ↗⚑ flag

   Blaxel—none0/10

   No evidence pack item mentions GPU support, GPU instance types, or hardware acceleration for sandboxes; documentation covers scaling, preview URLs, filesystems, jobs, and MCP hosting but never GPU attachment. missing for 10: any mention of GPU-enabled sandbox instances, GPU pricing/config, or GPU-specific workload examples.

   ⚑ flag

Files

1. developerRead, write, upload, and download files in the sandbox filesystem via the SDK

   weight 2 · round to E2B
   E2B✓fullclaimed8/10

   E2B SDK docs clearly document files.write() and files.read() for single and multiple files, plus files.list() for directory listing, covering read/write/list operations via the SDK. Upload/download is implicit in write/read of file content but not explicitly named as 'upload/download' with byte-stream examples. missing for 10: explicit upload/download terminology or examples (e.g., binary file transfer, streaming), independent/hands-on corroboration beyond docs.

   • [claimed-docs] “You can write single files to the sandbox filesystem using the `files.write()` method.”
   • [claimed-docs] “You can read files from the sandbox filesystem using the `files.read()` method.”
   • [claimed-docs] “You can also write multiple files to the sandbox.”
   • [claimed-docs] “const files = await sbx.files.list('/')”

   proof ↗⚑ flag

   Blaxel—none0/10

   The evidence describes sandboxes, MCP-based tool operation, and a separate 'Agent Drive' distributed filesystem, but nothing documents SDK methods for reading, writing, uploading, or downloading files within a sandbox. Missing for 10: SDK file I/O API reference, upload/download examples, hands-on confirmation of file operations in sandbox.

   • [claimed-docs] “Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.”
   • [claimed-docs] “Agent Drive is a distributed filesystem that can be mounted to multiple sandboxes or agents at any time, including while they are already ru…”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”

   proof ↗⚑ flag

Runtimes

1. developerDefine custom sandbox templates or bring my own container image

   weight 2 · round to E2B
   E2B✓fullclaimed9/10

   E2B templates explicitly let developers define a custom base image, environment variables, files, commands, and start command, and the CLI supports building/naming/snapshotting templates for reuse; this is well-documented first-party functionality with CLI tooling support. Missing for 10: no independent/hands-on third-party confirmation of custom template builds succeeding in practice.

   • [claimed-docs] “E2B templates allow you to define custom sandboxes. You can define the base image, environment variables, files to copy, commands to run, an…”
   • [claimed-docs] “This gives you fully configured sandboxes with running processes ready to use with zero wait time for your users.”
   • [claimed-docs] “You can name the snapshot template with the `--name` flag. If a template with that name already exists, it is reused.”
   • [claimed-docs] “You can manage sandbox snapshots with the `e2b sandbox snapshot` (alias `snap`) commands.”
   • [claimed-docs] “e2b sandbox create <template>”
   • [claimed-docs] “E2B CLI is a command line tool that allows you to manage and interact with sandboxes and templates.”

   proof ↗⚑ flag

   Blaxel~partialclaimed6/10

   Docs explicitly reference 'Sandbox images' allowing creation of customized & reusable sandbox environments (blaxel-docs-7), which is direct evidence of custom template/image support. However, no evidence details how to bring an arbitrary Dockerfile/OCI image, base image customization workflow, or CLI/SDK commands for building/pushing custom images. missing for 10: concrete docs/examples on bring-your-own-container-image workflow, supported base image formats, and CLI commands for building/publishing custom sandbox templates.

   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”

   proof ↗⚑ flag

2. developerExecute code in multiple language runtimes (Python, JavaScript, and more) and get rich results back

   weight 2 · round to E2B
   E2B✓fullclaimed8/10

   E2B's docs show runCode execution (e2b-docs-1, e2b-docs-21) with sandboxes supporting Python and JavaScript SDKs, plus file I/O and terminal command execution for rich interaction with results (e2b-docs-7, e2b-docs-8, e2b-docs-19). It's explicitly positioned for running AI-generated code across languages with tool-use integration (e2b-docs-32, e2b-docs-33). missing for 10: explicit enumeration of all supported language runtimes beyond Python/JS/CLI, and independent hands-on confirmation of 'rich results' (e.g., charts/images) beyond docs claims.

   • [claimed-docs] “const sbx = await Sandbox.create() // Creates a persistent sandbox session const execution = await sbx.runCode('print("hello world")')”
   • [claimed-docs] “We’ll write the minimal code for starting Sandbox, executing Python inside it and listing all files inside the root directory.”
   • [claimed-docs] “You can write single files to the sandbox filesystem using the `files.write()` method.”
   • [claimed-docs] “You can run terminal commands inside the sandbox using the `commands.run()` method.”
   • [claimed-docs] “You can read files from the sandbox filesystem using the `files.read()` method.”
   • [claimed-docs] “E2B can work with any LLM and AI framework. The easiest way to connect an LLM to E2B is to use the tool use capabilities of the LLM”
   • [claimed-docs] “You can use E2B Sandbox to run AI-generated code to analyze data.”

   proof ↗⚑ flag

   Blaxel~partialclaimed3/10

   Blaxel's docs confirm sandboxes exist for code execution (blaxel-docs-1, blaxel-docs-7) and can be customized via templates, but there is no explicit evidence of specific language runtime support (Python, JavaScript, etc.) or of structured/rich result output formats from executed code. Missing for 10: explicit list of supported language runtimes, documentation of output/result format (e.g., stdout, images, rich objects), and any hands-on demonstration of multi-language execution.

   • [claimed-docs] “Install the Blaxel skill to give your agent the ability to deploy AI agents, create sandboxes for code execution, host MCP servers, run batc…”
   • [claimed-docs] “Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”

   proof ↗⚑ flag

Untrusted code

1. developerExecute untrusted, AI-generated code without risking my own infrastructure

   weight 3 · round to E2B
   E2B✓fullclaimed9/10

   E2B is explicitly designed as isolated sandbox infrastructure (Firecracker microVMs) to run AI-generated/untrusted code without touching the developer's own machine, with persistence, network controls, resource limits, and self-hosting/BYOC options for stricter isolation needs (e2b-gh-3, e2b-docs-44, e2b-docs-10, e2b-gh-2). Docs also show direct integration for coding agents (Claude Code, Codex, Amp) executing in these sandboxes with full filesystem/terminal access (e2b-docs-28, e2b-docs-42). Missing for 10: independent third-party security audit or hands-on penetration-test evidence beyond vendor docs/GitHub description.

   • [github] “E2B is an open-source infrastructure that allows you to run AI-generated code in secure isolated sandboxes in the cloud.”
   • [claimed-docs] “your agent's code runs in an isolated Firecracker microVM instead of your server, with a real Debian toolchain, pause/resume persistence, an…”
   • [claimed-docs] “Every sandbox has outbound internet access by default. Control and restrict it with a simple on/off switch or fine-grained allow and deny li…”
   • [github] “Read the self-hosting guide to learn how to set up the E2B infrastructure on your own. The infrastructure is deployed using Terraform.”
   • [claimed-docs] “Run AI coding agents like Claude Code, Codex, and Amp in secure E2B sandboxes with full terminal, filesystem, and git access.”
   • [claimed-docs] “E2B provides a pre-built `claude` template with Claude Code already installed.”
   • [claimed-docs] “Pause a sandbox and resume it later from the exact state it was in, including the filesystem and the memory, so running processes and loaded…”

   proof ↗⚑ flag

   Blaxel✓fullclaimed7/10

   Blaxel provides sandboxes explicitly for isolated code execution, exposed via MCP tool calls, with scale-to-zero/resume infrastructure meaning execution happens off the developer's own infra, plus custom sandbox images and private preview URLs with tokens for security. Missing for 10: independent/hands-on evidence of isolation guarantees (e.g., security audits, escape testing) and explicit detail on resource/network sandboxing limits beyond docs claims.

   • [claimed-docs] “Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”
   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”
   • [claimed-docs] “When you create a private preview URL a token is required to access the URL.”
   • [claimed-docs] “Install the Blaxel skill to give your agent the ability to deploy AI agents, create sandboxes for code execution, host MCP servers, run batc…”

   proof ↗⚑ flag

2. developerRun arbitrary shell commands and install packages inside the sandbox

   weight 2 · round to E2B
   E2B✓fullclaimed9/10

   E2B docs explicitly document commands.run() for executing arbitrary shell commands inside sandboxes, plus CLI exec-command support with background flag, and templates allow custom package installation via build commands. Combined with file read/write and persistent sandbox sessions, this directly delivers arbitrary shell execution and package installation. Missing for 10: independent hands-on benchmark specifically verifying package installation success/failure rates.

   • [claimed-docs] “You can run terminal commands inside the sandbox using the `commands.run()` method.”
   • [claimed-docs] “Use the `--background` flag to run a command in the background and return immediately.”
   • [claimed-docs] “E2B templates allow you to define custom sandboxes. You can define the base image, environment variables, files to copy, commands to run, an…”
   • [claimed-docs] “You can create a sandbox and connect an interactive terminal to it.”
   • [claimed-docs] “e2b sandbox create <template>”

   proof ↗⚑ flag

   Blaxel~partialclaimed5/10

   Blaxel's sandboxes are documented as code-execution environments exposed via MCP tool calls, and customizable sandbox images imply support for installing packages/dependencies, but no evidence explicitly shows arbitrary shell command execution or package installation examples/APIs. missing for 10: explicit shell/exec command documentation, package manager install examples, hands-on demonstration of arbitrary command execution.

   • [claimed-docs] “Install the Blaxel skill to give your agent the ability to deploy AI agents, create sandboxes for code execution, host MCP servers, run batc…”
   • [claimed-docs] “Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”

   proof ↗⚑ flag

Agent lifecycle

1. ai-native userMy agent can provision its own sandbox, execute code, read the results, and tear it down — end to end without a human

   weight 3 · round to E2B
   E2B✓fullclaimed9/10

   E2B's SDK API directly supports programmatic sandbox creation, code execution, filesystem read/write, and teardown/kill — all callable by an agent without human intervention (e2b-docs-1, e2b-docs-6, e2b-docs-19, e2b-docs-8). Docs explicitly describe running AI coding agents like Claude Code/Codex end-to-end in sandboxes with full terminal/filesystem access (e2b-docs-28, e2b-docs-42, e2b-docs-43), and timeouts/kill provide automated teardown. Missing for 10: no independent hands-on benchmark of a fully autonomous end-to-end agent loop (only vendor docs and one community note about agent friction, not a failure of the core provision/execute/teardown flow).

   • [claimed-docs] “const sbx = await Sandbox.create() // Creates a persistent sandbox session const execution = await sbx.runCode('print("hello world")')”
   • [claimed-docs] “You can shutdown the sandbox any time even before the timeout is up by calling the `kill` method.”
   • [claimed-docs] “You can read files from the sandbox filesystem using the `files.read()` method.”
   • [claimed-docs] “You can run terminal commands inside the sandbox using the `commands.run()` method.”
   • [claimed-docs] “Run AI coding agents like Claude Code, Codex, and Amp in secure E2B sandboxes with full terminal, filesystem, and git access.”
   • [claimed-docs] “E2B provides a pre-built `claude` template with Claude Code already installed.”
   • [claimed-docs] “With the E2B backend, the agent's built-in tools all execute inside an isolated sandbox instead of your machine”
   • [claimed-docs] “When you call the set timeout method, the sandbox timeout will be reset to the new value that you specified.”

   proof ↗⚑ flag

   Blaxel✓fullclaimed8/10

   Blaxel docs describe agents provisioning sandboxes via a skill/API with zero code, exposing each sandbox as an MCP server so agents can execute code via tool calls, and scale-to-zero/teardown behavior after inactivity — covering provision, execute, read results, and teardown end-to-end without human intervention. missing for 10: independent hands-on verification of a full agentic loop and explicit documentation of an agent reading back execution results programmatically.

   • [claimed-docs] “Install the Blaxel skill to give your agent the ability to deploy AI agents, create sandboxes for code execution, host MCP servers, run batc…”
   • [claimed-docs] “Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.”
   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”

   proof ↗⚑ flag

Isolation

1. platform-engineerRely on a documented hard isolation boundary (microVM or equivalent) between sandboxes and my systems

   weight 3 · round to E2B
   E2B✓fullclaimed8/10

   E2B docs explicitly state that code runs 'in an isolated Firecracker microVM instead of your server' with network controls and pause/resume, directly documenting the hard isolation boundary platform engineers need. Missing for 10: independent third-party security audit or pentest report, and more detail on the isolation boundary's guarantees beyond a single doc line.

   • [claimed-docs] “your agent's code runs in an isolated Firecracker microVM instead of your server, with a real Debian toolchain, pause/resume persistence, an…”
   • [claimed-docs] “With the E2B backend, the agent's built-in tools all execute inside an isolated sandbox instead of your machine”
   • [claimed-docs] “Every sandbox has outbound internet access by default. Control and restrict it with a simple on/off switch or fine-grained allow and deny li…”
   • [github] “E2B is an open-source infrastructure that allows you to run AI-generated code in secure isolated sandboxes in the cloud.”

   proof ↗⚑ flag

   Blaxel—none0/10

   The evidence pack describes Blaxel's sandbox features (scale-to-zero, MCP exposure, preview URLs, templates) but never documents the underlying isolation mechanism (e.g., microVM, gVisor, container hardening) or any explicit security boundary guarantee between sandboxes and host systems. Missing for 10: any mention of microVM/hypervisor-based isolation, a security/architecture whitepaper describing the isolation boundary, or third-party/independent verification of sandbox isolation.

   • [claimed-docs] “Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”
   • [claimed-docs] “When you create a private preview URL a token is required to access the URL.”

   proof ↗⚑ flag

2. ai-native userGive an agent a sandbox where host secrets and credentials are unreachable by the code it runs

   weight 2 · round to E2B
   E2B✓fullclaimed7/10

   E2B's docs and repo repeatedly describe sandboxes as isolated Firecracker microVMs separate from the host/server ('your agent's code runs in an isolated Firecracker microVM instead of your server', 'isolated sandbox instead of your machine'), and network access to the sandbox can be restricted via allow/deny lists, all supporting the claim that a sandboxed agent cannot reach host resources. However, there is no explicit documentation or hands-on test specifically confirming host secrets/credentials (e.g., env vars, cloud IAM creds) are unreachable from sandboxed code, nor independent security audit evidence. Missing for 10: explicit secret/credential-isolation guarantees, third-party security audit or hands-on penetration test confirming host secrets are unreachable.

   • [github] “E2B is an open-source infrastructure that allows you to run AI-generated code in secure isolated sandboxes in the cloud.”
   • [claimed-docs] “your agent's code runs in an isolated Firecracker microVM instead of your server, with a real Debian toolchain, pause/resume persistence, an…”
   • [claimed-docs] “With the E2B backend, the agent's built-in tools all execute inside an isolated sandbox instead of your machine”
   • [claimed-docs] “Every sandbox has outbound internet access by default. Control and restrict it with a simple on/off switch or fine-grained allow and deny li…”

   proof ↗⚑ flag

   Blaxel~partialclaimed5/10

   Blaxel provides isolated sandboxes for code execution with MCP-based control and access tokens for API/CLI/SDK auth, implying separation between host credentials and sandbox execution, but there's no explicit documentation stating host secrets/credentials are unreachable by sandbox code or describing secret-injection isolation guarantees. missing for 10: explicit secret-isolation architecture docs, third-party security audit or penetration-test evidence, and confirmation that host credentials cannot leak into sandbox runtime.

   • [claimed-docs] “Install the Blaxel skill to give your agent the ability to deploy AI agents, create sandboxes for code execution, host MCP servers, run batc…”
   • [claimed-docs] “Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”
   • [claimed-docs] “API keys can be used in the Blaxel APIs, CLI and SDK.”

   proof ↗⚑ flag

Network policy

1. platform-engineerRestrict or allow the sandbox's network egress with explicit policy

   weight 3 · round to E2B
   E2B✓fullclaimed8/10

   E2B docs explicitly document network egress control: outbound internet access is on by default and can be restricted via 'a simple on/off switch or fine-grained allow and deny lists,' directly matching the platform-engineer's need for explicit egress policy. missing for 10: independent/hands-on verification of allow/deny list behavior, and detailed policy syntax/API reference beyond the summary.

   • [claimed-docs] “Every sandbox has outbound internet access by default. Control and restrict it with a simple on/off switch or fine-grained allow and deny li…”
   • [claimed-docs] “your agent's code runs in an isolated Firecracker microVM instead of your server, with a real Debian toolchain, pause/resume persistence, an…”

   proof ↗⚑ flag

   Blaxel—none0/10

   No evidence describes any network egress control, firewall, or allow/deny-list policy for sandboxes—docs cover scaling, preview URLs, filesystem mounting, and regions but nothing about network access restriction. missing for 10: any mention of egress policy configuration, allow/deny lists, network isolation controls, or firewall rules for sandboxes.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to E2B
   E2B~partialprobed6/10

   E2B is API/SDK-first, so most core operations (sandbox create, exec, filesystem, commands, metrics, templates, snapshots, webhooks) are documented as API/CLI actions rather than gated behind a UI, and the CLI mirrors sandbox lifecycle management. However, some UI-surfaced features like Desktop streaming (mouse/keyboard/screenshot) require a separate Desktop SDK, and no public OpenAPI spec was found, making full parity hard to verify. Missing for 10: a confirmed OpenAPI/full REST spec, explicit confirmation that dashboard-only features (e.g., billing, team management) are also API-accessible, independent verification of full UI/API parity.

   • [claimed-docs] “const sbx = await Sandbox.create() // Creates a persistent sandbox session const execution = await sbx.runCode('print("hello world")')”
   • [claimed-docs] “E2B CLI is a command line tool that allows you to manage and interact with sandboxes and templates.”
   • [claimed-docs] “E2B templates allow you to define custom sandboxes. You can define the base image, environment variables, files to copy, commands to run, an…”
   • [claimed-docs] “You can manage sandbox snapshots with the `e2b sandbox snapshot` (alias `snap`) commands.”
   • [claimed-docs] “Webhooks provide a way for notifications to be delivered to an external web server whenever certain sandbox lifecycle events occur.”
   • [github] “For mouse, keyboard, screenshot, application, and desktop streaming APIs, install the Desktop SDK”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.e2b.dev/openapi.json, https://docs.e2b.dev/swagger.json, https://docs.e2b.dev/api/opena…”
   • [claimed-docs] “If you need an explicit configuration — for example several API keys, teams, or BYOC or self-hosted deployments — create an `E2B` client and…”

   proof ↗⚑ flag

   Blaxel~partialprobed5/10

   Blaxel offers API keys usable across API, CLI, and SDK, and documents CLI/SDK for core resources (sandboxes, agents, jobs, MCP servers), suggesting broad programmatic control. However, no OpenAPI/spec was found (all candidate paths 404), and there is no explicit documentation claiming full UI/API feature parity. Missing for 10: a public OpenAPI reference, an explicit parity statement, and independent confirmation that all UI actions are exposed via API.

   • [claimed-docs] “API keys can be used in the Blaxel APIs, CLI and SDK.”
   • [probe] “official CLI documented at https://docs.blaxel.ai/cli-reference/introduction”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.blaxel.ai/openapi.json, https://docs.blaxel.ai/swagger.json, https://docs.blaxel.ai/api…”
   • [claimed-docs] “The easiest way to integrate the Blaxel CLI into a CI pipeline is with the official Blaxel GitHub Action.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to E2B
   E2B~partialclaimed4/10

   E2B is open-source and self-hostable (Terraform-based), and sandbox files can be read/downloaded via files.read()/CLI, giving a technical path to extract data and avoid lock-in, but there is no documented 'export all account data' feature or guarantee of open data formats for account-level artifacts like snapshots/templates. missing for 10: explicit data-export tooling, documented open format guarantees for exported data, account-level export across all sandboxes/snapshots.

   • [github] “Read the self-hosting guide to learn how to set up the E2B infrastructure on your own. The infrastructure is deployed using Terraform.”
   • [github] “E2B is an open-source infrastructure that allows you to run AI-generated code in secure isolated sandboxes in the cloud.”
   • [claimed-docs] “You can read files from the sandbox filesystem using the `files.read()` method.”
   • [claimed-docs] “You can manage sandbox snapshots with the `e2b sandbox snapshot` (alias `snap`) commands.”

   proof ↗⚑ flag

   Blaxel—none0/10

   No evidence pack items address data export or portability in open formats, or any means to leave the platform with one's data; the closest is a migration skill for importing sandbox code from other providers, not exporting data out of Blaxel.

   ⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to E2B
   E2B✓fullclaimed7/10

   GitHub repo description explicitly states 'E2B is an open-source infrastructure' and provides a self-hosting guide with Terraform, corroborating that the source is publicly available and usable, not just marketing docs. Missing for 10: explicit citation of the license name (e.g., Apache/MIT) and independent confirmation of license terms.

   • [github] “E2B is an open-source infrastructure that allows you to run AI-generated code in secure isolated sandboxes in the cloud.”
   • [github] “Read the self-hosting guide to learn how to set up the E2B infrastructure on your own. The infrastructure is deployed using Terraform.”

   proof ↗⚑ flag

   Blaxel—none0/10

   No evidence indicates Blaxel's core source code is published under an open license; only one skill (migration skill) is mentioned as open source, but the product itself (platform/CLI/SDK) has no cited open-license repository or licensing statement.

   • [claimed-docs] “The open source Blaxel migration skill gives agents the knowledge they need to migrate sandbox code from other providers to Blaxel.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to E2B
   E2B~partialclaimed6/10

   E2B is explicitly open-source and provides a documented self-hosting guide using Terraform to deploy the infrastructure on your own, plus BYOC/self-hosted deployment options referenced in client docs. However, the evidence lacks depth on self-hosting: no details on required components, hardware/scale limits, maintenance burden, or independent reports of someone successfully self-hosting. missing for 10: detailed self-hosting setup docs/tutorial, independent verification of a working self-hosted deployment, and clarity on feature parity between self-hosted and cloud versions.

   • [github] “Read the self-hosting guide to learn how to set up the E2B infrastructure on your own. The infrastructure is deployed using Terraform.”
   • [github] “E2B is an open-source infrastructure that allows you to run AI-generated code in secure isolated sandboxes in the cloud.”
   • [claimed-docs] “If you need an explicit configuration — for example several API keys, teams, or BYOC or self-hosted deployments — create an `E2B` client and…”
   • [claimed-docs] “If you need an explicit configuration — for example several API keys, teams, or [BYOC or self-hosted deployments](/byoc) in a single process…”

   proof ↗⚑ flag

   Blaxel—none0/10

   Blaxel is presented entirely as a serverless/managed cloud platform (scale-to-zero, regions, hosted MCP servers, hosted sandboxes) with no mention of a self-hostable core product, on-prem deployment, or open-source server component that a user could run themselves; only a migration skill and CLI/SDK for interacting with the hosted service are documented.

   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”
   • [claimed-docs] “you can optionally pin an agent or MCP server to a specific region by setting the region field in your blaxel.toml”
   • [claimed-docs] “MCP Server Hosting is a serverless computing service that allows you to host remote MCP servers without having to manage infrastructure.”
   • [claimed-docs] “When deploying a resource on Blaxel, you sometimes have the option to choose the deployment region.”

   proof ↗⚑ flag

Latency

1. developerStart sandboxes with documented sub-second-to-few-second cold starts

   weight 3 · round to Blaxel
   E2B—none0/10

   The evidence pack describes sandbox creation, persistence, pausing/resuming, and templates with 'zero wait time,' but contains no documented benchmark or specific claim of sub-second-to-few-second cold start times. Missing for 10: any explicit startup latency figures, benchmark data, or documentation stating cold-start speed in seconds.

   • [claimed-docs] “const sbx = await Sandbox.create() // Creates a persistent sandbox session const execution = await sbx.runCode('print("hello world")')”
   • [claimed-docs] “This gives you fully configured sandboxes with running processes ready to use with zero wait time for your users.”
   • [claimed-docs] “E2B templates allow you to define custom sandboxes. You can define the base image, environment variables, files to copy, commands to run, an…”

   proof ↗⚑ flag

   Blaxel~partialclaimed6/10

   Docs claim resume from standby under 25ms even after weeks of inactivity, implying sub-second warm start, and scale-to-zero after 5s inactivity, which is documented performance behavior specific to sandboxes. However, this is vendor-claimed only with no independent benchmark or hands-on cold-start timing (first-boot from image) reported, and no numbers for true 'cold start' (first creation) vs resume-from-standby. Missing for 10: independent benchmarks/hands-on cold-start measurements, explicit distinction between first-time cold start and standby resume times.

   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”

   proof ↗⚑ flag

Scale

1. platform-engineerRun large concurrent fleets of sandboxes with documented concurrency limits

   weight 3 · round to E2B
   E2B~partialclaimed6/10

   E2B publishes concrete documented concurrency limits (up to 100 concurrently running sandboxes, up to 24-hour session length on Pro plans) and metrics/CLI tooling to manage fleets, giving platform engineers real numbers to plan around. However missing for 10: no documentation of how limits scale for enterprise/self-hosted deployments, no guidance on requesting higher concurrency, no independent/hands-on benchmarks validating fleet behavior at scale, and no discussion of failure modes or queuing when limits are hit.

   • [claimed-docs] “Up to 24-hour sandbox session length Up to 100 concurrently running sandboxes”
   • [claimed-docs] “Sandboxes can run continuously for up to 24 hours (Pro) or 1 hour (Base). For longer workloads, use pause and resume”
   • [claimed-docs] “The sandbox metrics allows you to get information about the sandbox's CPU, memory and disk usage.”
   • [claimed-docs] “Getting the metrics of a sandbox returns an array of timestamped metrics containing CPU, memory and disk usage information.”
   • [github] “Read the self-hosting guide to learn how to set up the E2B infrastructure on your own. The infrastructure is deployed using Terraform.”

   proof ↗⚑ flag

   Blaxel~partialclaimed3/10

   Docs show sandboxes can run in parallel (Jobs batch processing, scale-to-zero/resume, regional pinning) suggesting fleet-scale operation, but no evidence anywhere states explicit concurrency limits, quotas, or maximum fleet sizes a platform-engineer could plan against. missing for 10: documented per-account/per-region concurrency limits, quota API or dashboard, load-test or benchmark data showing fleet scale in practice.

   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”
   • [claimed-docs] “Jobs allow you to run many AI tasks in parallel using batch processing.”
   • [claimed-docs] “you can optionally pin an agent or MCP server to a specific region by setting the region field in your blaxel.toml”
   • [claimed-docs] “Agent Drive is a distributed filesystem that can be mounted to multiple sandboxes or agents at any time, including while they are already ru…”

   proof ↗⚑ flag

2. developerKeep a sandbox session running for hours or days for long agent tasks

   weight 2 · round to E2B
   E2B~partialclaimed7/10

   E2B sandboxes can run continuously for hours (up to 24h on Pro plans, with configurable/resettable timeouts via setTimeout), covering the 'hours' part of the story fully, and for multi-day tasks E2B explicitly recommends pause/resume to preserve full memory and filesystem state indefinitely rather than true continuous execution. This satisfies long-running agent tasks but with a documented architectural limitation (base tier capped at 1h, Pro at 24h continuous) requiring the pause/resume workaround for day-scale persistence. Missing for 10: evidence of truly continuous multi-day execution without pause/resume, and independent/hands-on confirmation of stability over such long sessions.

   • [claimed-docs] “Sandboxes can run continuously for up to 24 hours (Pro) or 1 hour (Base). For longer workloads, use pause and resume”
   • [claimed-docs] “Pause a sandbox and resume it later from the exact state it was in, including the filesystem and the memory, so running processes and loaded…”
   • [claimed-docs] “A paused sandbox is kept indefinitely with no automatic deletion.”
   • [claimed-docs] “When you call the set timeout method, the sandbox timeout will be reset to the new value that you specified.”
   • [claimed-docs] “You can change the sandbox timeout when it's running by calling the `setTimeout` method in JavaScript or `set_timeout` method in Python.”
   • [claimed-docs] “Up to 24-hour sandbox session length Up to 100 concurrently running sandboxes”

   proof ↗⚑ flag

   Blaxel~partialclaimed5/10

   Docs describe scale-to-zero after 5s inactivity with sub-25ms resume even after weeks, implying persistent state across long periods, but this describes a serverless suspend/resume model rather than an explicit 'keep running continuously for hours/days' capability, and there is no documentation of session duration limits or long-running execution during active agent work. missing for 10: explicit session/timeout limits, evidence of continuous multi-hour/day execution without suspension, independent confirmation of long-running task support.

   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”

   proof ↗⚑ flag

Pricing

1. developerStart building with a free tier or included credits without talking to sales

   weight 1 · round to E2B
   E2B✓fullclaimed8/10

   E2B explicitly gives every new account $100 in credits with no sales contact required (e2b-docs-41), and the pricing page details a self-serve tier with concrete limits (24-hour sessions, 100 concurrent sandboxes, e2b-docs-14) alongside quickstart docs showing immediate SDK usage without any account-approval step. missing for 10: no independent/community confirmation of the signup flow or credit amount, and no explicit mention of a free tier distinct from trial credits.

   • [claimed-docs] “Every new E2B account get $100 in credits.”
   • [claimed-docs] “Up to 24-hour sandbox session length Up to 100 concurrently running sandboxes”
   • [claimed-docs] “Customize your Sandbox CPU & RAM”
   • [claimed-docs] “const sbx = await Sandbox.create() // Creates a persistent sandbox session const execution = await sbx.runCode('print("hello world")')”

   proof ↗⚑ flag

   Blaxel—none0/10

   No evidence pack items mention pricing, free tier, included credits, or self-service signup without sales contact; all evidence covers technical features (sandboxes, MCP, jobs, regions).

   ⚑ flag

2. platform-engineerPay per second only for the compute a sandbox actually uses

   weight 3 · round to E2B
   E2B~partialclaimed4/10

   The pricing page confirms usage-based configuration (customizable CPU/RAM, session-length/concurrency tiers) and the SDK/CLI let you kill a sandbox or reset its timeout at any moment, plus real-time CPU/memory/disk metrics — all consistent with paying only for compute actually consumed. However, no evidence pack item explicitly states a per-second billing granularity or shows a billing/invoice example. Missing for 10: explicit per-second billing rate documentation, an invoice/billing dashboard example, or a stated billing unit (e.g., 'billed per second of sandbox uptime').

   • [claimed-docs] “Customize your Sandbox CPU & RAM”
   • [claimed-docs] “Up to 24-hour sandbox session length Up to 100 concurrently running sandboxes”
   • [claimed-docs] “When you call the set timeout method, the sandbox timeout will be reset to the new value that you specified.”
   • [claimed-docs] “You can shutdown the sandbox any time even before the timeout is up by calling the `kill` method.”
   • [claimed-docs] “The sandbox metrics allows you to get information about the sandbox's CPU, memory and disk usage.”
   • [claimed-docs] “Getting the metrics of a sandbox returns an array of timestamped metrics containing CPU, memory and disk usage information.”

   proof ↗⚑ flag

   Blaxel~partialclaimed3/10

   Docs describe scale-to-zero after 5s of inactivity and fast resume (blaxel-docs-2), implying sandboxes only consume compute while active, which is suggestive of fine-grained usage-based billing, but no evidence explicitly states a per-second pricing/billing model or shows pricing pages confirming this granularity. missing for 10: explicit pricing/billing documentation stating per-second metering, evidence of actual invoicing granularity, independent confirmation of cost savings from scale-to-zero.

   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Blaxel
   E2B~partialclaimed4/10

   E2B docs mention BYOC and self-hosted deployment options (Terraform-based) which would let an organization control where infrastructure/data physically resides, but there is no evidence of an explicit region/residency selector or documented list of hosting regions for the standard managed service. missing for 10: explicit region-selection UI/API, documented list of available data-residency regions, compliance certifications tied to specific regions.

   • [claimed-docs] “If you need an explicit configuration — for example several API keys, teams, or BYOC or self-hosted deployments — create an `E2B` client and…”
   • [claimed-docs] “If you need an explicit configuration — for example several API keys, teams, or [BYOC or self-hosted deployments](/byoc) in a single process…”
   • [github] “Read the self-hosting guide to learn how to set up the E2B infrastructure on your own. The infrastructure is deployed using Terraform.”

   proof ↗⚑ flag

   Blaxel~partialclaimed6/10

   Docs confirm users can pin agents/MCP servers to a specific region via blaxel.toml and that deployment region choice is sometimes available, which directly supports data residency control. Missing for 10: a full list of available regions, compliance/certification details (e.g., GDPR, SOC2 residency guarantees), and independent confirmation that this pinning is enforced for all data at rest (not just compute location).

   • [claimed-docs] “you can optionally pin an agent or MCP server to a specific region by setting the region field in your blaxel.toml”
   • [claimed-docs] “When deploying a resource on Blaxel, you sometimes have the option to choose the deployment region.”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   E2B—none0/10

   The evidence pack contains no mention of E2B's data-training policies, opt-out controls, or data-use terms for AI model training; all evidence concerns sandbox execution, CLI, persistence, and networking features. This axis is a fair question for a product processing user code/data, but nothing in the pack shows E2B addressing it.

   ⚑ flag

   Blaxel—none0/10

   No evidence pack item addresses data usage for AI model training, opt-out policies, or privacy commitments regarding training data; this is an infrastructure/agent-hosting product where such a policy could exist but is undocumented here. Missing for 10: any privacy policy or ToS statement on training data usage, opt-out mechanism, or data retention controls.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to E2B
   E2B~partialclaimed6/10

   E2B gives concrete lifecycle controls over sandbox data: sandboxes can be killed/shutdown anytime, timeouts set/reset, and paused sandboxes are 'kept indefinitely with no automatic deletion' until explicitly resumed or removed via CLI shutdown/kill commands, giving users direct control over when sandbox state (filesystem, memory) persists or is destroyed. However, there's no evidence of broader data-retention policy documentation (e.g., logs, telemetry, backups) or explicit deletion/export guarantees at the account or compliance level (GDPR/SOC2-style retention statements). Missing for 10: explicit data-retention/deletion policy documentation beyond sandbox kill/pause mechanics, account-level data deletion guarantees, and compliance/regulatory retention statements.

   • [claimed-docs] “A paused sandbox is kept indefinitely with no automatic deletion.”
   • [claimed-docs] “You can shutdown the sandbox any time even before the timeout is up by calling the `kill` method.”
   • [claimed-docs] “You can change the sandbox timeout when it's running by calling the `setTimeout` method in JavaScript or `set_timeout` method in Python.”
   • [claimed-docs] “You can shutdown single or all running sandboxes with the E2B CLI.”
   • [claimed-docs] “To shutdown all running sandboxes, run the following command:”
   • [claimed-docs] “Pause a sandbox and resume it later from the exact state it was in, including the filesystem and the memory, so running processes and loaded…”

   proof ↗⚑ flag

   Blaxel—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or data lifecycle management for user data/sandboxes; the docs focus on infrastructure, scaling, and access tokens rather than privacy/retention controls.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   E2B—none0/10

   No evidence pack item mentions telemetry, analytics collection, or an opt-out/opt-in setting for usage tracking; E2B's self-hosting option (e2b-gh-2) implies infrastructure control but does not document any telemetry toggle for the hosted product.

   ⚑ flag

   Blaxel—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or any opt-out mechanism; the docs cover deployment, sandboxes, MCP hosting, and security tokens but nothing about data collection settings. missing for 10: any documentation or setting related to telemetry collection or opt-out, privacy policy mention, or usage-tracking configuration.

   ⚑ flag

Lifecycle

1. developerSet timeouts so sandboxes shut down automatically and stop billing when idle or done

   weight 2 · round to E2B
   E2B✓fullclaimed8/10

   E2B documents explicit timeout controls (setTimeout/set_timeout), default and configurable session lengths (24h Pro/1h Base), automatic kill on timeout, and manual kill/shutdown via SDK and CLI, directly enabling idle sandboxes to auto-terminate. missing for 10: explicit first-party confirmation that billing stops precisely at timeout/kill (only inferred from lifecycle docs), and independent/hands-on verification of billing behavior.

   • [claimed-docs] “When you call the set timeout method, the sandbox timeout will be reset to the new value that you specified.”
   • [claimed-docs] “You can shutdown the sandbox any time even before the timeout is up by calling the `kill` method.”
   • [claimed-docs] “You can change the sandbox timeout when it's running by calling the `setTimeout` method in JavaScript or `set_timeout` method in Python.”
   • [claimed-docs] “Sandboxes can run continuously for up to 24 hours (Pro) or 1 hour (Base). For longer workloads, use pause and resume”
   • [claimed-docs] “You can shutdown single or all running sandboxes with the E2B CLI.”
   • [claimed-docs] “To shutdown all running sandboxes, run the following command:”

   proof ↗⚑ flag

   Blaxel~partialclaimed6/10

   Docs confirm automatic scale-to-zero after 5s of inactivity with fast resume, which directly supports idle shutdown and implies billing stops when inactive (blaxel-docs-2). However, there is no evidence of a developer-configurable timeout parameter (e.g., custom idle duration) or explicit confirmation that billing halts during scale-to-zero, and no independent/hands-on corroboration of this behavior. Missing for 10: explicit configurable timeout setting, billing-stop confirmation, independent verification.

   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”

   proof ↗⚑ flag

2. developerSpin up an isolated sandbox with one API/SDK call and get a live environment in seconds

   weight 3 · round to E2B
   E2B✓fullclaimed9/10

   Docs clearly show a single SDK call (Sandbox.create()) provisions an isolated sandbox with near-instant readiness, plus templates offering 'zero wait time' startup, CLI equivalents, and evidence of the core create/run/kill/timeout lifecycle. missing for 10: independent hands-on benchmarking of actual boot latency beyond vendor claims.

   • [claimed-docs] “const sbx = await Sandbox.create() // Creates a persistent sandbox session const execution = await sbx.runCode('print("hello world")')”
   • [claimed-docs] “This gives you fully configured sandboxes with running processes ready to use with zero wait time for your users.”
   • [claimed-docs] “const sbx = await Sandbox.create() // Creates a persistent sandbox session”
   • [claimed-docs] “We’ll write the minimal code for starting Sandbox, executing Python inside it and listing all files inside the root directory.”
   • [claimed-docs] “e2b sandbox create <template>”
   • [github] “E2B is an open-source infrastructure that allows you to run AI-generated code in secure isolated sandboxes in the cloud.”

   proof ↗⚑ flag

   Blaxel~partialprobed6/10

   Docs confirm sandboxes are a core primitive with fast resume (<25ms from standby), customizable/reusable images, API/CLI/SDK access via API keys, and MCP-server exposure for tool control, all pointing to programmatic creation. However, there's no explicit example or evidence of a single one-call SDK/API invocation creating a sandbox with a concrete latency claim for cold creation (only resume-from-standby timing is given), and no independent/hands-on confirmation of 'seconds to live environment' for a fresh (non-cached) sandbox. missing for 10: explicit one-call code sample creating a sandbox, documented cold-start provisioning latency, independent verification of speed claims.

   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”
   • [claimed-docs] “API keys can be used in the Blaxel APIs, CLI and SDK.”
   • [claimed-docs] “Every sandbox is exposed via an MCP server that allows agents to operate it using tool calls.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.blaxel.ai/llms.txt # Documentation > Blaxel documentation: cloud sandboxes, AI agent hosting, MCP …”

   proof ↗⚑ flag

Preview access

1. developerExpose a port from the sandbox on a public preview URL to reach services running inside

   weight 2 · round to Blaxel
   E2B—none0/10

   The evidence pack covers sandbox lifecycle (create, pause/resume, timeouts, files, commands, metrics, CLI) but contains no mention of exposing ports or generating public preview URLs to reach services running inside a sandbox. This is a fair capability question for a sandbox execution platform, so the axis applies, but nothing in the evidence supports it.

   ⚑ flag

   Blaxel✓fullclaimed8/10

   Docs confirm sandboxes support preview URLs, including custom domains and private/token-protected URLs, directly enabling exposing a port to reach services running inside the sandbox via a public URL. Missing for 10: no explicit hands-on example showing the port-to-URL mapping mechanics or independent third-party confirmation.

   • [claimed-docs] “Preview URLs with your own custom domain.”
   • [claimed-docs] “When you create a private preview URL a token is required to access the URL.”

   proof ↗⚑ flag

Snapshots

1. developerPause a running sandbox and resume it later with filesystem and memory state intact

   weight 2 · round to E2B
   E2B✓fullclaimed8/10

   E2B's docs explicitly document pausing a sandbox and resuming it later 'from the exact state it was in, including the filesystem and the memory, so running processes and loaded variables survive,' with paused sandboxes kept indefinitely, plus CLI support for snapshot/pause management (e2b sandbox snapshot, list --state paused). This directly matches the story's core claim. missing for 10: independent/hands-on third-party verification of state fidelity after resume, and more detail on any limitations (e.g., GPU/network state, long-running process edge cases) beyond first-party docs.

   • [claimed-docs] “Pause a sandbox and resume it later from the exact state it was in, including the filesystem and the memory, so running processes and loaded…”
   • [claimed-docs] “A paused sandbox is kept indefinitely with no automatic deletion.”
   • [claimed-docs] “Sandboxes can run continuously for up to 24 hours (Pro) or 1 hour (Base). For longer workloads, use pause and resume”
   • [claimed-docs] “You can manage sandbox snapshots with the `e2b sandbox snapshot` (alias `snap`) commands.”
   • [claimed-docs] “This will return running sandboxes, you can specify `--state` to get paused or both.”
   • [claimed-docs] “your agent's code runs in an isolated Firecracker microVM instead of your server, with a real Debian toolchain, pause/resume persistence, an…”

   proof ↗⚑ flag

   Blaxel~partialclaimed5/10

   Docs mention automatic scale-to-zero after inactivity with resume from standby in under 25ms 'even after weeks' (blaxel-docs-2), implying state is preserved across pause/resume cycles, and Agent Drive provides a persistent distributed filesystem mountable to sandboxes (blaxel-docs-9). However, there is no explicit developer-triggered pause/resume API, and no confirmation that in-memory process state (not just filesystem) is preserved. missing for 10: explicit manual pause/resume command, explicit statement that memory/process state (not just filesystem) survives resume, independent verification of the claim.

   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”
   • [claimed-docs] “Agent Drive is a distributed filesystem that can be mounted to multiple sandboxes or agents at any time, including while they are already ru…”

   proof ↗⚑ flag

2. developerSnapshot a sandbox and later restore or fork new sandboxes from that snapshot

   weight 3 · round to E2B
   E2B✓fullclaimed8/10

   E2B explicitly supports pause/resume of a sandbox preserving filesystem and memory, and exposes CLI/SDK snapshot management (`e2b sandbox snapshot`), naming snapshot templates that can be reused to create new sandboxes, effectively enabling fork-like behavior from a saved state. missing for 10: explicit documentation/example of forking multiple independent sandboxes from a single snapshot simultaneously, and independent hands-on verification of restore/fork fidelity beyond vendor docs.

   • [claimed-docs] “Pause a sandbox and resume it later from the exact state it was in, including the filesystem and the memory, so running processes and loaded…”
   • [claimed-docs] “A paused sandbox is kept indefinitely with no automatic deletion.”
   • [claimed-docs] “Sandboxes can run continuously for up to 24 hours (Pro) or 1 hour (Base). For longer workloads, use pause and resume”
   • [claimed-docs] “You can manage sandbox snapshots with the `e2b sandbox snapshot` (alias `snap`) commands.”
   • [claimed-docs] “You can name the snapshot template with the `--name` flag. If a template with that name already exists, it is reused.”

   proof ↗⚑ flag

   Blaxel—none0/10

   The evidence covers sandbox creation, scale-to-zero/resume, preview URLs, templates, and filesystem mounting, but nowhere mentions snapshotting a sandbox's state or forking new sandboxes from a saved snapshot. Sandbox images/templates ([blaxel-docs-7]) are pre-built environments, not runtime snapshots of a live sandbox's state.

   • [claimed-docs] “Automatic scale-to-zero after 5s inactivity, resume from standby under 25ms even after weeks.”
   • [claimed-docs] “Sandbox images allow you to create customized & reusable sandbox environments.”
   • [claimed-docs] “Agent Drive is a distributed filesystem that can be mounted to multiple sandboxes or agents at any time, including while they are already ru…”

   proof ↗⚑ flag