Crusoe Cloud vs Runpod

Crusoe Cloud

The v1 REST API has a published OpenAPI description, Markdown docs, HMAC-signed keys, reader roles and a 90-day audit log, with on-demand GPU prices public. No idempotency keys or control-plane rate limits were found, spot and B200 prices go through sales, and a storage outage in eu-norway1 lasted about four hours on 29 September 2026.

Runpod

Per-second billing across more than a dozen serverless GPU classes, H100 at $4.79 and A100 80 GB at $2.72 an hour. Data-centre outages of 6 to 24 hours in each of July, August and September 2026.

Crusoe Cloud

1. Sign every request. Build the payload from path, sorted query string, verb and X-Crusoe-Timestamp, HMAC-SHA256 it with the base64url-decoded secret, and send Authorization: Bearer 1.0:<access_key_id>:<signature>.
2. Use https://api.cloud.crusoe.ai/v1. Some docs pages and the MCP server still name api.crusoecloud.com and /v1alpha5.
3. Creates, updates and deletes return an operation. Poll the matching operations endpoint for state, and list existing resources by name before retrying a create, because no idempotency key was found.
4. Managed AI uses separate Intelligence API keys and hosts, api.inference.crusoecloud.com for OpenAI-compatible calls and api.intelligence.crusoecloud.com for files and fine-tuning jobs.
5. Delete a VM and its disks to stop charges. A stopped on-demand VM is not billed for compute, but its 128 GB OS disk still bills at $0.08 a GiB-month.

Runpod

1. Create a Restricted or Read Only key per endpoint for the agent, not an All key
2. Use REST v2 at api.runpod.io/v2 with a Bearer header; avoid GraphQL, which puts the key in the URL
3. Fetch /run results within 30 minutes and /runsync results within 1 minute, or they're gone
4. Call /retry on a failed job ID rather than submitting a duplicate job
5. Check /health before relying on an endpoint idle for a week, since max workers drop to 0