Maritime vs SPACE

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.

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.

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.

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