Get an audit

Head to head · Sandbox persist · October 2026 research run

Agent 37 Cloud vs Together Code Sandbox

Together Code Sandbox scores 53.6 (D) on agent readiness against Agent 37 Cloud's 46.1 (D), and leads in 4 of 7 scored categories. Both do sandbox persist.

Agent 37 CloudAgent 37 Inc. · HTTP API D46.1/100#758 of 841 Together Code SandboxTogether AI · HTTP API D53.6/100#628 of 841

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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Together Code Sandbox D

Good for Teams already buying from Together, and former CodeSandbox SDK users, who want Docker-defined sandboxes with disk and memory snapshots from Python or TypeScript.

Ahead on

  • Schema & documentation, 86 against 57
  • Agent ergonomics, 70 against 60
  • Maintenance & community, 83 against 65

Watch for

The SDK and CLI work only for organisations Together has enabled, and the docs say to contact Together for access

Score by category

CategoryWeight this runAgent 37 CloudTogether Code SandboxEdge
Reliability16%202725Agent 37 Cloud +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25786Together Code Sandbox +29
Agent ergonomics13%16.26070Together Code Sandbox +10
Security & auth14%17.54947Agent 37 Cloud +2
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86583Together Code Sandbox +18
Transparency & trust7%8.85660Together Code Sandbox +4
Negative events≤1500
Total46.1 · D53.6 · D

Facts side by side

FactAgent 37 CloudTogether Code Sandbox
KindHTTP APIHTTP API
VendorAgent 37 Inc.Together AI
Hosted endpointhttps://api.agent37.com/v1https://api.bartender.codesandbox.io
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
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 Together's terms of service. The SDKs, CLI and OpenAPI documents on GitHub are MIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-052026-10-07
Terms last updated2026-08-04no date given
Privacy policy last updated2026-09-01no date given
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 textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity74 npm/wk3 stars, 1.3k npm/wk, 3.4k 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.

Together Code Sandbox

Two public OpenAPI documents, MIT clients for Python and TypeScript, cursor pagination and built-in retries make the surface easy for an agent to drive. Access is the limit. Together enables the SDK per organisation on request, publishes no rate limits or SLA, and neither status page names the sandbox service.

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

Together Code Sandbox

  1. Confirm the organisation is on Together's allowlist before installing. A valid TOGETHER_API_KEY alone is not enough
  2. Build a snapshot first with snapshots.create. No default image exists, and every sandbox needs snapshot_id or snapshot_alias
  3. Set ttl at creation or call terminate(). Nothing stops a sandbox otherwise, and closing the Python client leaves it running
  4. Store the snapshot alias, not the sandbox ID. A terminated sandbox can't restart, and its state lives at sandbox:<id>
  5. Exclude snapshots.create from retries with should_retry, and set experimental.network_policy before serving anything private on a port

Questions

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

Together Code Sandbox scores 53.6 (D) on agent readiness against Agent 37 Cloud's 46.1 (D), and leads in 4 of 7 scored categories.

Do Agent 37 Cloud and Together Code Sandbox need an API key?

Both need an API key.

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

Yes. Agent 37 Cloud has a hosted endpoint at https://api.agent37.com/v1 and Together Code Sandbox at https://api.bartender.codesandbox.io.

Other comparisons with Agent 37 Cloud or Together Code 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.

Get an auditSee a sample report