Agent 37 Cloud vs Maritime

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.

Maritime

Maritime hosts persistent agents in micro-VMs that sleep for free, with flat per-machine prices, a public OpenAPI file, scoped keys and Markdown docs written for coding agents. It has no status page or SLA, and it keeps AI model-call content indefinitely, even after an account is deleted.

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

Maritime

1. Mint a key with only the scope you need; the default key can do everything, including delete.
2. Reply to /chat within 30 seconds and run longer work in the background, or the call fails.
3. Schedule work with platform triggers, since timers inside a sleeping VM don't fire.
4. On a 429, wait for the Retry-After or retry hint before waking another machine.
5. Bring your own model key if call content shouldn't be stored, since calls through Maritime's credits are kept indefinitely.