E2B

PASS consensus from 2 PASS, 1 PARTIAL.

The quickstart covers signup, API-key setup, installation, sandbox creation, hello-world execution, root listing, and the launch command. The quickstart covers create, execute, and list in five steps, but it installs @e2b/code-interpreter and calls runCode while the docs home page, /api-key, and /commands all install e2b and call sandbox.commands.run, and no page explains which package to pick. The quickstart provides a clear 5-step path from account creation, API key setup, SDK install, code to run, and execution command with no missing steps.

PASS consensus from 2 PASS, 1 FAIL.

Pro resource ceilings use open-ended plus signs, while most Enterprise fields say Custom; exact cross-tier limits are unavailable. The Plans table on /billing states every requested dimension per tier (vCPUs 8 / 8+ / Custom, memory 8 GB / 8+ GB / Custom, disk 10 GB / 20+ GB / Custom, runtime 1 hour / 24 hours / Custom, concurrent sandboxes 20 / 100-1,100 / 1,100+, concurrent builds 20 / 20 / Custom, creation rate 1 per sec / 5 per sec / Custom) and the numbers are repeated consistently on /sandbox, /filesystem, /template/quickstart, and the FAQ pages. The billing page and pricing page together state all limits for each tier; values are broadly consistent across pages.

FAIL consensus from 3 FAIL.

The reference names the cause but provides no retry timing, response-header guidance, backoff, or limit-remediation steps. Across all 241 documentation pages the only 429 material is this one-line class description (plus its Python twin and a passing mention that fork errors map 429 to RateLimitError); no page states which limit produces a 429, no Retry-After header is documented, and the words backoff and retry never appear in a rate-limit context, so there is no recovery path to follow. RateLimitError is documented as a class with a one-line description, but the docs give no recovery path: no retry strategy, no backoff guidance, no rate limit headers, and no connection between sandbox creation rate (1/sec Hobby, 5/sec Pro on the billing page) and the 429 error.

PASS consensus from 3 PASS.

One page documents registration, payload receipt, signature verification, retry triggers, and idempotent deduplication by event ID. One page carries the whole job: registration with signatureSecret, the full JSON payload schema, working e2b-signature verification code in JavaScript, Python, and Go, all four e2b-* request headers, the retry count (up to 3 attempts total), what counts as a failed delivery, and the instruction to deduplicate on the payload id field. Registration, payload format, signature verification code (SHA-256(secret+payload) base64) in JS/Python/Go, retry policy (3 attempts, 4xx/5xx failure), and idempotency guidance are all documented on one page.

PASS consensus from 2 PASS, 1 PARTIAL.

The quickstart and SDK reference both import @e2b/code-interpreter and call Sandbox.create without arguments. The e2b package, the import { Sandbox } from 'e2b' minimum example, and the commands and files modules on the versioned v2.38.2 reference match the home page snippet and the /commands page exactly. The quickstart has a complete working example using @e2b/code-interpreter, but the lifecycle events API page imports { Sandbox } from 'e2b' , two different npm packages exposing the same API shape, creating confusion when cross-referencing pages.