Agent 37 Cloud vs SPACE

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.

SPACE

Once deployed, SPACE's native API has a public OpenAPI 3.1 contract, stable error codes with a retryable flag and 24-hour idempotency keys, and egress and credential controls sit outside the VM. A person must first deploy it on a Linux x86_64 host with KVM and Kubernetes. Version 0.8.0 has no tagged release, changelog or public container images.

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

SPACE

1. Ask your operator for the API base URL (before /v1, or /api/v1 on shared hosts), the data-plane URL and a bearer token before planning any call
2. Poll the returned operation until it succeeds and the sandbox is running before creating a command. A 202 response is not readiness
3. Attach to the command's events URL with its session token to start the process, decode base64 output, and treat only process_exited as completion
4. Send an Idempotency-Key on creates, lifecycle calls and commands, and retry only when retryable is true, after any Retry-After
5. Save output as it arrives. Reconnecting with Last-Event-ID returns resync_required, not the missed output