Head to head · Sandbox persist · October 2026 research run

Agent 37 Cloud vs Deno Sandbox

Deno Sandbox scores 50.3 (D) on agent readiness against Agent 37 Cloud's 46.1 (D), and leads in 4 of 7 scored categories. Agent 37 Cloud leads on maintenance & community. Both do sandbox persist.

Which one, for what

Agent 37 Cloud D

Good for A product that gives each end user a long-lived agent machine that is idle most of the day and needs a harness preinstalled.

Ahead on

  • Maintenance & community, 65 against 45

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No status page was found. status.agent37.com returns 404, and the terms promise no uptime level

Deno Sandbox D

Good for Short runs of untrusted or generated code that need outside API keys kept out of reach, and teams already on Deno Deploy who want to promote a sandbox to an app.

Ahead on

  • Reliability, 48 against 27
  • Schema & documentation, 66 against 57
  • Security & auth, 61 against 49

Watch for

Beta since 3 February 2026. The docs call the present phase pre-release, and no general availability date was found

Score by category

CategoryWeight this runAgent 37 CloudDeno SandboxEdge
Reliability16%202748Deno Sandbox +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25766Deno Sandbox +9
Agent ergonomics13%16.26060even
Security & auth14%17.54961Deno Sandbox +12
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86545Agent 37 Cloud +20
Transparency & trust7%8.85658Deno Sandbox +2
Negative events≤150-2
Total46.1 · D50.3 · D

Facts side by side

FactAgent 37 CloudDeno Sandbox
KindHTTP APIHTTP API
VendorAgent 37 Inc.Deno Land Inc.
Hosted endpointhttps://api.agent37.com/v1no (local only)
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePaid
x402nono
LicenceProprietary service under Agent 37's terms of service. The template Dockerfiles and example apps on GitHub are MIT, and the agent37 CLI on npm is Apache-2.0Proprietary service under the Deno Deploy terms and conditions. The @deno/sandbox and deno-sandbox SDKs are MIT
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-052026-07-22
Terms last updated2026-08-042026-09-30
Privacy policy last updated2026-09-012026-09-30
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity74 npm/wk6 stars, 2k npm/wk, 32k PyPI/wk

Verdicts

Agent 37 Cloud

Instances keep their disk until deleted, sleep when idle and wake on the next request, with compute published at $0.80 a vCPU-month and stable error codes on both APIs. The product launched on 29 September 2026. No status page, OpenAPI file, SDK library or published rate limits were found, and the starter credit needs a card.

Deno Sandbox

Secrets stay outside the microVM and are substituted only on outbound requests to approved hosts, and an allowlist limits egress. The service is still in beta, sandboxes need the $20 Pro plan, lifetime is capped at 30 minutes, and no sandbox operation appears in the published OpenAPI document.

Before you call either

Agent 37 Cloud

  1. Send the key as Authorization: Bearer to api.agent37.com and as X-Agent37-Key to the instance URL. The Bearer form on instance URLs is deprecated
  2. Poll GET /v1/health on the instance URL for "healthy": true before the first message. status: running only means the machine is up
  3. Check whether error is a string before reading error.code. Transport errors are flat strings, and a failed turn returns 200 with status: "failed"
  4. Don't blindly retry an exec that timed out after 13 minutes. The command keeps running, so a retry starts a second copy
  5. Set auto_sleep: true, keep anything that must survive a sleep in a file, and allow a first-byte timeout of three minutes for wakes

Deno Sandbox

  1. Set DENO_DEPLOY_TOKEN to an organisation token (prefix ddo_) from Settings in console.deno.com. The organisation must be on Pro or above
  2. Pass allowNet on every Sandbox.create(). The Security page says outbound access is unrestricted when it is omitted
  3. Pass credentials through secrets with a hosts list, not env, so code in the VM sees only a placeholder
  4. The default timeout ends the VM when the client disconnects. Pass a duration such as "10m" and reconnect with Sandbox.connect({ id }), up to 30 minutes
  5. Create volumes in ord and start the sandbox in ord. A volume mounts only in its own region
  6. exposeHttp URLs are public with no authentication. Treat the random subdomain as a secret

Questions

Which is better for AI agents, Agent 37 Cloud or Deno Sandbox?

Deno Sandbox scores 50.3 (D) on agent readiness against Agent 37 Cloud's 46.1 (D), and leads in 4 of 7 scored categories. Agent 37 Cloud leads on maintenance & community.

Do Agent 37 Cloud and Deno Sandbox need an API key?

Both need an API key.

Can an agent call Agent 37 Cloud and Deno Sandbox without installing anything?

Agent 37 Cloud has a hosted endpoint at https://api.agent37.com/v1. No hosted endpoint is listed for Deno Sandbox.

Other comparisons with Agent 37 Cloud or Deno Sandbox

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.