{ "data": { "a": { "slug": "crusoe-cloud", "name": "Crusoe Cloud", "vendor": "Crusoe", "vendorUrl": "https://www.crusoe.ai", "kind": "http-api", "category": "gpu-compute", "summary": "Crusoe Cloud rents NVIDIA and AMD GPU virtual machines with managed Kubernetes and Slurm, and runs hosted model inference, dedicated deployments and LoRA fine-tuning. Resources are managed through a REST API, a CLI, a Terraform provider and a Go client.", "url": "https://www.anchorterminal.com/tools/crusoe-cloud", "markdownUrl": "https://www.anchorterminal.com/tools/crusoe-cloud.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/crusoe-cloud.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/crusoe-cloud.json", "repo": "https://github.com/crusoecloud/client-go", "license": "Proprietary service under the Crusoe Cloud Platform Terms of Service. The Go client and the MCP server package are MIT. The CLI ships as binaries, and no licence file was found in the Terraform provider repository", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.cloud.crusoe.ai/v1", "packages": [ { "registry": "go", "name": "github.com/crusoecloud/client-go" }, { "registry": "npm", "name": "@crusoeai/cloud-mcp" } ], "auth": "api-key", "authNotes": "Self-serve. A person signs up in the console with Google, GitHub or an email code, then creates an access key ID and secret key under Security, with an optional alias and expiry. Each request carries `X-Crusoe-Timestamp` and `Authorization: Bearer 1.0:\u003caccess_key_id\u003e:\u003csignature\u003e`, where the signature is an HMAC-SHA256 of the path, sorted query string, verb and timestamp. Keys inherit the roles of the user who made them (`org-admin`, `org-editor`, `org-reader`, `project-editor`, `project-reader`). Managed AI uses separate Intelligence API keys sent as a Bearer token. Service accounts appear in the API description and the Terraform provider 1.6.0, with no docs page found.", "pricing": "usage", "pricingNotes": "Pay as you go, billed per second for on-demand VMs. Per GPU-hour, H200 $4.29, H100 $3.90, MI300X $3.45, A100 $2.00 to $2.30 and L40S $1.50. GB200, B200, MI355X and all spot prices are contact sales. Compute needs a non-prepaid credit card. $5 of introductory credits cover Serverless Inference and Fine-Tuning without a card. Ingress and egress are free (https://www.crusoe.ai/cloud/pricing).", "priceSummary": "$0.04 / vCPU-hr", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the API description or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": 41, "popularity": { "githubStars": null, "npmWeekly": 7, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.crusoecloud.com/", "llmsTxt": "https://docs.crusoecloud.com/llms.txt", "openapi": "https://api.crusoecloud.com/v1/openapi.json", "capabilities": [ "compute.gpu", "compute.containers", "compute.batch", "compute.endpoints" ], "tags": [ "hosted", "usage-priced", "openapi", "llms-txt", "mcp", "cli", "terraform", "go", "status-page", "soc2", "enterprise" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 63.4, "grade": "B", "agentReady": false, "rank": 396, "ranked": true, "rankOf": 950, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 45, "maintenance": 76, "payments": 30, "reliability": 66, "schema": 79, "security": 74, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "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.", "bestFor": "Teams that want whole GPU machines or clusters with managed Kubernetes or Slurm in the US, Iceland or Norway, under an SLA, and are content to manage lifecycles themselves.", "strengths": [ "Requests are signed with HMAC-SHA256 over the path, query, verb and timestamp, so the secret key never travels with a request.", "The API description is published for `/v1` and `/v1alpha5`, with 1,231 examples, and the docs serve `llms.txt` and a Markdown twin of each page.", "On-demand prices are public and billed per second. H100 is $3.90 and H200 $4.29 a GPU-hour, with no charge for ingress or egress.", "Organisation and project roles include read-only `org-reader` and `project-reader`, and the audit log keeps 90 days of control-plane actions readable through the API.", "The Terms of Service promise 90 days' notice before a service is discontinued or a customer-facing API changes in a backwards-incompatible way." ], "weaknesses": [ "No idempotency key or safe-retry guidance was found for create and delete calls, which return asynchronous operations to poll.", "No request rate limits were found for the infrastructure API. Numbers are published only for Serverless Inference.", "Spot prices and on-demand prices for GB200, B200 and MI355X are listed as contact sales, and provisioning compute needs a non-prepaid credit card.", "The status page shows a critical storage incident in eu-norway1 on 29 September 2026 (about 3 hours 54 minutes) and a 7.5-hour VM and cluster creation fault in us-east2 on 2 September.", "The Service Specific Terms let customers publish benchmark results only with Crusoe's written consent, and the Intelligence Foundry terms bar competitive analysis or benchmarking. Recorded as a fact, and it matters before any probe is run." ], "agentNotes": [ "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:\u003caccess_key_id\u003e:\u003csignature\u003e`.", "Use `https://api.cloud.crusoe.ai/v1`. Some docs pages and the MCP server still name `api.crusoecloud.com` and `/v1alpha5`.", "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.", "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.", "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." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.4 } ], "editorialScores": { "ergonomics": 45, "maintenance": 76, "payments": 30, "reliability": 66, "schema": 79, "security": 74, "transparency": 64 }, "provenanceScore": 90 }, "connect": { "install": "brew install crusoecloud/cli/crusoe", "http": "curl https://api.cloud.crusoe.ai/v1/capacities -H \"X-Crusoe-Timestamp: \u003cRFC3339 timestamp\u003e\" -H \"Authorization: Bearer \u003cversion:access_key_id:base64_encoded_signature\u003e\"", "claudeCode": "claude mcp add crusoe-cloud -- npx -y @crusoeai/cloud-mcp", "config": { "mcpServers": { "crusoe-cloud": { "args": [ "-y", "@crusoeai/cloud-mcp" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/crusoe-cloud" }, "area": "models", "unitPrices": [ { "item": "NVIDIA H100 80 GB HGX, on demand", "unit": "gpu-hour", "usd": 3.9, "note": "Billed per second while running. Spot is contact sales" }, { "item": "NVIDIA H200 141 GB HGX, on demand", "unit": "gpu-hour", "usd": 4.29 }, { "item": "NVIDIA A100 80 GB SXM, on demand", "unit": "gpu-hour", "usd": 2.3 }, { "item": "NVIDIA A100 80 GB PCIe, on demand", "unit": "gpu-hour", "usd": 2 }, { "item": "NVIDIA L40S 48 GB, on demand", "unit": "gpu-hour", "usd": 1.5 }, { "item": "AMD MI300X 192 GB, on demand", "unit": "gpu-hour", "usd": 3.45 }, { "item": "NVIDIA H100, Self-Serve Deployment", "unit": "gpu-hour", "usd": 5.5, "note": "Dedicated inference endpoint, billed until deleted. H200 $6.00, B200 $9.65, MI355X $7.40" }, { "item": "General-purpose CPU instance", "unit": "vcpu-hour", "usd": 0.04, "note": "Storage-optimised $0.09" }, { "item": "Persistent disk", "unit": "gb-month", "usd": 0.08, "note": "Per GiB. Shared disks $0.07, Object Storage $0.06" } ], "provenance": { "legalEntity": "Crusoe Technologies LLC", "domain": "crusoe.ai", "domainRegistered": "2019-01-28", "endpointOnVendorDomain": true, "terms": "https://legal.crusoe.ai/#terms-of-service", "privacy": "https://legal.crusoe.ai/#cloud-privacy-policy", "statusPage": "https://status.crusoecloud.com", "changelog": "https://docs.crusoecloud.com/updates", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The Crusoe Cloud Platform Terms of Service, version 1.10, effective 10 August 2026, are a contract with Crusoe Technologies LLC and its affiliates. Ten earlier versions are kept on the same page.", "legal.crusoe.ai is one page that holds every legal document and its earlier versions, reached by anchor. The terms and privacy links point at the anchors for the platform terms and the Crusoe Cloud Platform Privacy Notice, not at the separate website terms and website privacy notice.", "The Crusoe Cloud Platform Privacy Notice, version 1.3, effective 12 March 2026, covers Service Data only. Customer Data falls under the Data Processing and Security Terms, version 1.3, effective 14 July 2026.", "The API reference gives `https://api.cloud.crusoe.ai/v1`, under the vendor domain. Other docs pages and the MCP server name `api.crusoecloud.com`, and Managed AI answers at `api.inference.crusoecloud.com` and `api.intelligence.crusoecloud.com`. crusoecloud.com was registered on 14 April 2020 per RDAP and redirects to www.crusoe.ai.", "security.txt at www.crusoe.ai gives security@crusoe.ai and expires on 1 March 2027. It has no Policy field.", "RDAP for crusoe.ai gives a registration date of 2019-01-28. The website footer reads Crusoe, Inc, and the licence files in the CLI and Go client repositories name Crusoe Energy Systems LLC." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/crusoe-cloud.json", "live": { "slug": "crusoe-cloud", "probe": { "target": "https://api.cloud.crusoe.ai/v1", "method": "get", "lastAt": "2026-10-10T01:37:49.056909047Z", "lastOk": true, "lastStatus": 200, "lastMs": 184, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 194, "p95ms24h": 307, "samples24h": 102, "samples30d": 102, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.crusoecloud.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T01:33:35.04437209Z" }, "versions": [ { "registry": "npm", "name": "@crusoeai/cloud-mcp", "version": "0.1.6", "seenAt": "2026-10-09T16:48:11.482960233Z" } ], "githubStars": 4, "npmWeekly": 7, "pages": [ { "url": "https://docs.crusoecloud.com/updates", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:37:05.621891732Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "49f564f8d6cc" }, { "url": "https://www.crusoe.ai/cloud/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:49:22.174984932Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c8964d1b8c97" }, { "url": "https://legal.crusoe.ai/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:41:07.513334155Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "60dd879bf821" } ], "updatedAt": "2026-10-10T01:37:49.056909047Z" } }, "answer": "Crusoe Cloud scores 63.4 (B) on agent readiness against Massed Compute's 42.3 (E), and leads in 6 of 7 scored categories. Massed Compute leads on agent ergonomics.", "b": { "slug": "massed-compute", "name": "Massed Compute", "vendor": "Massed Compute", "vendorUrl": "https://massedcompute.com", "kind": "http-api", "category": "gpu-compute", "summary": "Massed Compute is a US GPU cloud that rents NVIDIA GPU virtual machines by the hour from hardware it owns, with bare metal and clusters by quote. Agents use its REST API or a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/massed-compute", "markdownUrl": "https://www.anchorterminal.com/tools/massed-compute.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/massed-compute.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/massed-compute.json", "repo": "https://github.com/Massed-Compute/massed-compute-mcp", "license": "Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://vm.massedcompute.com/api/v1", "packages": [ { "registry": "npm", "name": "massed-compute-mcp" }, { "registry": "pypi", "name": "massed-compute-mcp" } ], "auth": "mixed", "authNotes": "Self-serve. The owner signs up in a browser, verifies an email address and creates a named API token at vm.massedcompute.com/settings/api, choosing Full access or Read only. The token is shown once, travels as a Bearer header and is revoked from the token table. The same token works for the REST API and the MCP server. MCP clients that send no token get a 401 with an OAuth challenge, and the owner signs in and approves full or read-only access. Grants are listed and revoked under Connected Apps. The older marketplace API on `api.massedcompute.com` issues keys only through support.", "pricing": "usage", "pricingNotes": "No free tier or trial credit was found. The owner adds a card or pays in crypto, makes a first deposit and sets an auto-recharge threshold of at least $5 before any launch. Running VMs are debited every minute at a published hourly rate. On 9 October 2026 a single A30 was $0.35 an hour, an RTX A6000 $0.57, an L40S $0.97, an A100 80 GB $1.35 and an H100 80 GB $2.73. No bandwidth charge per the pricing page. Bare metal, clusters and the marketplace API are by quote (https://vm.massedcompute.com/pricing).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the two OpenAPI files, the MCP server card or the pricing page. The billing docs describe crypto top-ups made by the account owner, which is not a machine payment protocol (checked 2026-10-09).", "endpoints": [] }, "toolCount": 17, "popularity": { "githubStars": 1, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://vm-docs.massedcompute.com", "llmsTxt": "https://massedcompute.com/llms.txt", "openapi": "https://vm-docs.massedcompute.com/redocusaurus/plugin-redoc-0.yaml", "registryName": "io.github.Massed-Compute/mcp", "capabilities": [ "compute.gpu" ], "tags": [ "hosted", "usage-priced", "openapi", "mcp", "oauth", "api-key", "read-only-keys", "node", "python", "card-required", "crypto-payments", "closed-source" ], "lastRelease": "2026-07-24", "graded": true, "anchor": { "graded": true, "score": 42.3, "grade": "E", "agentReady": false, "rank": 896, "ranked": true, "rankOf": 950, "categoryRank": 18, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 51, "payments": 20, "reliability": 20, "schema": 69, "security": 61, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -5, "negativeNotes": [ "8 June 2026. The `instances_list` and `instances_get` MCP tools returned the cleartext VM password although their descriptions said it was redacted. Fixed in `massed-compute-mcp` 1.0.3 and later moved server-side, with rotation advice in the changelog. No GitHub advisory is published. Fixed and documented, so 3 points (https://github.com/Massed-Compute/massed-compute-mcp/blob/main/CHANGELOG.md).", "9 October 2026. The product page lists SDKs for Go and a Terraform provider, webhooks and per-project quotas. None appears in the docs, the OpenAPI file or the vendor's public GitHub organisation. 2 points (https://massedcompute.com/products/inventory-api/)." ], "verdict": "The hosted MCP server and REST API accept OAuth grants or API tokens in read-only and full-access tiers, and all 17 tools carry typed schemas and safety annotations in a public server card. No status page, rate limit figures or API changelog were found, a launch has no idempotency key, and the governing terms could not be read.", "bestFor": "Agents that rent whole GPU VMs by the hour for training, fine-tuning or a model server and want a small MCP tool set with a read-only mode.", "strengths": [ "API tokens and OAuth grants come in read-only and full-access tiers, and tokens are revoked one at a time in the console", "A public server card lists all 17 MCP tools with JSON Schema inputs and `readOnlyHint`, `destructiveHint` and `idempotentHint` annotations", "Hourly prices for 23 GPU configurations, from $0.35 for an A30 to $52.80 for eight B300s, are public without a login", "A public OpenAPI 3.0 file covers the 14 REST operations at `https://vm.massedcompute.com/api/v1`", "The sub-processor list names 23 processors with locations, was updated on 10 September 2026 and has an RSS feed for changes" ], "weaknesses": [ "No status page, incident history or security.txt was found on any of the vendor's hosts", "A 429 answer exists but no rate limit figures are published, and the OpenAPI file documents no error response", "`POST /instance/launch` has no idempotency key, so a retried launch can start a second billed VM", "Until a fix dated 8 June 2026, `instances_list` and `instances_get` returned the cleartext VM password although their descriptions said it was redacted", "The product page lists Go and Terraform SDKs and webhooks that the docs, the OpenAPI file and the public GitHub organisation do not show", "A stopped instance is billed at the full hourly rate. Only termination ends billing, and it deletes the data" ], "agentNotes": [ "Use `https://vm.massedcompute.com/api/v1`. The older docs at api-docs.massedcompute.com describe a separate marketplace API on `api.massedcompute.com` whose keys come from support.", "Ask the owner for a read-only token unless the task must launch or terminate. Read-only credentials cannot call launch, restart, terminate or SSH key changes.", "Call `gpu_inventory_list` and `images_list` before `instances_launch`. Product names and image IDs are free values, and SXM-only images do not run on PCIe cards.", "Expect 402 on launch until the owner has added credit and set a recharge amount and threshold. List instances before retrying a launch.", "Terminate to end billing. Stopping keeps the full hourly charge, and termination deletes the instance data." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.3 } ], "editorialScores": { "ergonomics": 56, "maintenance": 51, "payments": 20, "reliability": 20, "schema": 69, "security": 61, "transparency": 53 }, "provenanceScore": 68 }, "connect": { "install": "npm install -g massed-compute-mcp", "claudeCode": "claude mcp add --transport http massed-compute https://vm.massedcompute.com/api/mcp --header \"Authorization: Bearer MC_TOKEN\"", "config": { "mcpServers": { "massed-compute": { "headers": { "Authorization": "Bearer MC_TOKEN" }, "type": "http", "url": "https://vm.massedcompute.com/api/mcp" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/massed-compute" }, "area": "models", "unitPrices": [ { "item": "A30 24 GB VM", "unit": "gpu-hour", "usd": 0.35, "note": "Billed per minute" }, { "item": "RTX A5000 24 GB VM", "unit": "gpu-hour", "usd": 0.44, "note": "Billed per minute" }, { "item": "RTX A6000 48 GB VM", "unit": "gpu-hour", "usd": 0.57, "note": "Billed per minute. An alternative configuration is $0.55" }, { "item": "RTX 6000 Ada 48 GB VM", "unit": "gpu-hour", "usd": 0.79, "note": "Billed per minute" }, { "item": "L40 48 GB VM", "unit": "gpu-hour", "usd": 0.86, "note": "Billed per minute" }, { "item": "RTX PRO 4500 Blackwell 32 GB VM", "unit": "gpu-hour", "usd": 0.92, "note": "Billed per minute" }, { "item": "L40S 48 GB VM", "unit": "gpu-hour", "usd": 0.97, "note": "Billed per minute" }, { "item": "A100 80 GB VM", "unit": "gpu-hour", "usd": 1.35, "note": "Billed per minute. SXM4 and DGX variants are $1.38" }, { "item": "RTX PRO 6000 Blackwell 96 GB VM", "unit": "gpu-hour", "usd": 2.19, "note": "Billed per minute" }, { "item": "H100 80 GB VM", "unit": "gpu-hour", "usd": 2.73, "note": "Billed per minute. H100 NVL is $3.11 and H100 SXM5 $3.14" }, { "item": "H200 NVL 141 GB VM", "unit": "gpu-hour", "usd": 3.62, "note": "Billed per minute" }, { "item": "B200 SXM6 VM, 8 GPUs", "unit": "gpu-hour", "usd": 5.43, "note": "Sold only as eight GPUs at $43.46 an hour. Our division, rounded" }, { "item": "B300 SXM6 VM, 8 GPUs", "unit": "gpu-hour", "usd": 6.6, "note": "Sold only as eight GPUs at $52.80 an hour. Our division" } ], "provenance": { "legalEntity": "Massed Compute, Inc.", "domain": "massedcompute.com", "domainRegistered": "2021-10-28", "endpointOnVendorDomain": true, "terms": "https://massedcompute.com/legal/terms-conditions/", "privacy": "https://massedcompute.com/legal/privacy-policy/", "statusPage": "", "changelog": "https://github.com/Massed-Compute/massed-compute-mcp/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms \u0026 Conditions page is the document the DPA calls the Principal Agreement. Its body is an embedded Termly viewer drawn by script, and we could not read it.", "The End User Licence Agreement, last updated 15 September 2026, names Massed Compute, Inc. of Las Vegas, Nevada, and applies Nevada law. The older docs site's footer says Massed Compute LLC.", "The privacy policy, last updated 22 July 2026, covers the website, a mobile application and the Services in general.", "The REST API and the MCP server answer at vm.massedcompute.com, on the vendor domain.", "/.well-known/security.txt answers 404 on massedcompute.com and on vm.massedcompute.com.", "RDAP for massedcompute.com gives a registration date of 2021-10-28.", "No status page was found on the site, the docs or the pricing page.", "The changelog linked is the MCP wrapper's. No API changelog was found.", "A Data Processing Agreement, last modified 27 March 2026, and a sub-processor list, last updated 10 September 2026, are published." ], "score": 68 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/massed-compute.json", "live": { "slug": "massed-compute", "probe": { "target": "https://vm.massedcompute.com/api/v1", "method": "get", "lastAt": "2026-10-10T01:37:57.796991169Z", "lastOk": true, "lastStatus": 200, "lastMs": 528, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 566, "p95ms24h": 1577, "samples24h": 102, "samples30d": 102, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 17, "ok": 17 } ] }, "versions": [ { "registry": "github", "name": "Massed-Compute/massed-compute-mcp", "version": "v1.1.0", "released": "2026-07-24", "seenAt": "2026-10-09T17:04:15.605664679Z" }, { "registry": "npm", "name": "massed-compute-mcp", "version": "1.1.0", "seenAt": "2026-10-09T17:04:14.528689429Z" }, { "registry": "pypi", "name": "massed-compute-mcp", "version": "1.1.0", "released": "2026-07-24", "seenAt": "2026-10-09T17:04:15.405015566Z" } ], "githubStars": 1, "npmWeekly": 37, "pypiWeekly": 20, "pages": [ { "url": "https://raw.githubusercontent.com/Massed-Compute/massed-compute-mcp/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:44:33.145231849Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7fa22cb79429" }, { "url": "https://vm.massedcompute.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:47:14.582656601Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "fb389d9be37c" }, { "url": "https://massedcompute.com/legal/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:41:48.306296743Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "71fd70e07907" }, { "url": "https://massedcompute.com/legal/terms-conditions/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:41:50.386665594Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0a8bdfcc06c0" } ], "updatedAt": "2026-10-10T01:37:57.796991169Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Crusoe", "b": "Massed Compute", "name": "Vendor" }, { "a": "https://api.cloud.crusoe.ai/v1", "b": "https://vm.massedcompute.com/api/v1", "name": "Hosted endpoint" }, { "a": "HTTP, stdio", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "not published", "b": "$5.43 per GPU-hour", "name": "Price for gpu compute" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Crusoe Cloud Platform Terms of Service. The Go client and the MCP server package are MIT. The CLI ships as binaries, and no licence file was found in the Terraform provider repository", "b": "Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT", "name": "Licence" }, { "a": "41", "b": "17", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.Massed-Compute/mcp", "name": "MCP registry" }, { "a": "2026-10-08", "b": "2026-07-24", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-07-22", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "7 npm/wk", "b": "1 stars", "name": "Popularity" } ], "faq": [ { "answer": "Crusoe Cloud scores 63.4 (B) on agent readiness against Massed Compute's 42.3 (E), and leads in 6 of 7 scored categories. Massed Compute leads on agent ergonomics.", "question": "Which is better for AI agents, Crusoe Cloud or Massed Compute?" }, { "answer": "Crusoe Cloud needs an API key. Massed Compute takes an API key or an OAuth sign-in.", "question": "Do Crusoe Cloud and Massed Compute need an API key?" }, { "answer": "Yes. Crusoe Cloud has a hosted endpoint at https://api.cloud.crusoe.ai/v1 and Massed Compute at https://vm.massedcompute.com/api/v1.", "question": "Can an agent call Crusoe Cloud and Massed Compute without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 66 against 20", "Schema \u0026 documentation, 79 against 69", "Security \u0026 auth, 74 against 61", "Payments \u0026 pricing, 30 against 20", "Maintenance \u0026 community, 76 against 51", "Transparency \u0026 trust, 77 against 61" ], "also": [ "Runs on your own machine", "No incidents deducted, where Massed Compute loses 5 points for them" ], "goodFor": "Teams that want whole GPU machines or clusters with managed Kubernetes or Slurm in the US, Iceland or Norway, under an SLA, and are content to manage lifecycles themselves.", "slug": "crusoe-cloud", "watchFor": "No idempotency key or safe-retry guidance was found for create and delete calls, which return asynchronous operations to poll." }, { "aheadOn": [ "Agent ergonomics, 56 against 45" ], "also": null, "goodFor": "Agents that rent whole GPU VMs by the hour for training, fine-tuning or a model server and want a small MCP tool set with a read-only mode.", "slug": "massed-compute", "watchFor": "No status page, incident history or security.txt was found on any of the vendor's hosts" } ], "job": { "capability": "compute.gpu", "name": "GPU compute" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-crusoe-cloud.json", "title": "Baseten vs Crusoe Cloud", "url": "https://www.anchorterminal.com/compare/baseten-vs-crusoe-cloud" }, { "json": "https://www.anchorterminal.com/compare/baseten-vs-massed-compute.json", "title": "Baseten vs Massed Compute", "url": "https://www.anchorterminal.com/compare/baseten-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/beam-vs-crusoe-cloud.json", "title": "Beam vs Crusoe Cloud", "url": "https://www.anchorterminal.com/compare/beam-vs-crusoe-cloud" }, { "json": "https://www.anchorterminal.com/compare/beam-vs-massed-compute.json", "title": "Beam vs Massed Compute", "url": "https://www.anchorterminal.com/compare/beam-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-crusoe-cloud.json", "title": "Cerebrium vs Crusoe Cloud", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-crusoe-cloud" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.json", "title": "Cerebrium vs Massed Compute", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/coreweave-vs-crusoe-cloud.json", "title": "CoreWeave vs Crusoe Cloud", "url": "https://www.anchorterminal.com/compare/coreweave-vs-crusoe-cloud" }, { "json": "https://www.anchorterminal.com/compare/coreweave-vs-massed-compute.json", "title": "CoreWeave vs Massed Compute", "url": "https://www.anchorterminal.com/compare/coreweave-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-hugging-face-inference-endpoints.json", "title": "Crusoe Cloud vs Hugging Face Inference Endpoints", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-hugging-face-inference-endpoints" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-hyperbolic.json", "title": "Crusoe Cloud vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-hyperbolic" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-koyeb.json", "title": "Crusoe Cloud vs Koyeb", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-koyeb" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda.json", "title": "Crusoe Cloud vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-modal.json", "title": "Crusoe Cloud vs Modal", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-modal" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-nebius-ai-cloud.json", "title": "Crusoe Cloud vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-northflank.json", "title": "Crusoe Cloud vs Northflank", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-replicate-deploy.json", "title": "Crusoe Cloud vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-runpod.json", "title": "Crusoe Cloud vs Runpod", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-runpod" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute.json", "title": "Crusoe Cloud vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-vast-ai.json", "title": "Crusoe Cloud vs Vast.ai", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda.json", "title": "Crusoe Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute.json", "title": "Hugging Face Inference Endpoints vs Massed Compute", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute.json", "title": "Hyperbolic vs Massed Compute", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/koyeb-vs-massed-compute.json", "title": "Koyeb vs Massed Compute", "url": "https://www.anchorterminal.com/compare/koyeb-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-massed-compute.json", "title": "Lambda Cloud vs Massed Compute", "url": "https://www.anchorterminal.com/compare/lambda-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-modal.json", "title": "Massed Compute vs Modal", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-modal" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud.json", "title": "Massed Compute vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-northflank.json", "title": "Massed Compute vs Northflank", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy.json", "title": "Massed Compute vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-runpod.json", "title": "Massed Compute vs Runpod", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-runpod" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute.json", "title": "Massed Compute vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai.json", "title": "Massed Compute vs Vast.ai", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/massed-compute-vs-verda.json", "title": "Massed Compute vs Verda", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-verda" } ], "scores": [ { "by": 46, "crusoe-cloud": 66, "edge": "crusoe-cloud", "key": "reliability", "massed-compute": 20, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 10, "crusoe-cloud": 79, "edge": "crusoe-cloud", "key": "schema", "massed-compute": 69, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 11, "crusoe-cloud": 45, "edge": "massed-compute", "key": "ergonomics", "massed-compute": 56, "name": "Agent ergonomics", "weight": 13 }, { "by": 13, "crusoe-cloud": 74, "edge": "crusoe-cloud", "key": "security", "massed-compute": 61, "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "crusoe-cloud": 30, "edge": "crusoe-cloud", "key": "payments", "massed-compute": 20, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 25, "crusoe-cloud": 76, "edge": "crusoe-cloud", "key": "maintenance", "massed-compute": 51, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 16, "crusoe-cloud": 77, "edge": "crusoe-cloud", "key": "transparency", "massed-compute": 61, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Crusoe Cloud scores 63.4 (B) on agent readiness against Massed Compute's 42.3 (E), and leads in 6 of 7 scored categories. Massed Compute leads on agent ergonomics. Both do gpu compute.", "verdicts": { "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.", "massed-compute": "The hosted MCP server and REST API accept OAuth grants or API tokens in read-only and full-access tiers, and all 17 tools carry typed schemas and safety annotations in a public server card. No status page, rate limit figures or API changelog were found, a launch has no idempotency key, and the governing terms could not be read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute", "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.md", "slim": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.min.md" }, "markdown": "Crusoe Cloud scores 63.4 (B) on agent readiness against Massed Compute's 42.3 (E), and leads in 6 of 7 scored categories. Massed Compute leads on agent ergonomics. Both do gpu compute.\n\n- Crusoe Cloud: grade B, 63.4/100, rank #396 of 950. Markdown https://www.anchorterminal.com/tools/crusoe-cloud.md · JSON https://www.anchorterminal.com/api/v1/tools/crusoe-cloud.json\n- Massed Compute: grade E, 42.3/100, rank #896 of 950. Markdown https://www.anchorterminal.com/tools/massed-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/massed-compute.json\n- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md\n- All 167 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md\n\n## Which one, for what\n\n### Crusoe Cloud (B)\n\nGood for: Teams that want whole GPU machines or clusters with managed Kubernetes or Slurm in the US, Iceland or Norway, under an SLA, and are content to manage lifecycles themselves.\n\nAhead on:\n- Reliability, 66 against 20\n- Schema \u0026 documentation, 79 against 69\n- Security \u0026 auth, 74 against 61\n- Payments \u0026 pricing, 30 against 20\n- Maintenance \u0026 community, 76 against 51\n- Transparency \u0026 trust, 77 against 61\n\nAlso in its favour:\n- Runs on your own machine\n- No incidents deducted, where Massed Compute loses 5 points for them\n\nWatch for: No idempotency key or safe-retry guidance was found for create and delete calls, which return asynchronous operations to poll.\n\n### Massed Compute (E)\n\nGood for: Agents that rent whole GPU VMs by the hour for training, fine-tuning or a model server and want a small MCP tool set with a read-only mode.\n\nAhead on:\n- Agent ergonomics, 56 against 45\n\nWatch for: No status page, incident history or security.txt was found on any of the vendor's hosts\n\n\n## Score by category\n\n| Category | Weight | Crusoe Cloud | Massed Compute | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 66 | 20 | Crusoe Cloud +46 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 69 | Crusoe Cloud +10 |\n| Agent ergonomics | 13% (16.2 this run) | 45 | 56 | Massed Compute +11 |\n| Security \u0026 auth | 14% (17.5 this run) | 74 | 61 | Crusoe Cloud +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 20 | Crusoe Cloud +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 76 | 51 | Crusoe Cloud +25 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 61 | Crusoe Cloud +16 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **63.4 · B** | **42.3 · E** | |\n\n## Facts side by side\n\n| Fact | Crusoe Cloud | Massed Compute |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Crusoe | Massed Compute |\n| Hosted endpoint | `https://api.cloud.crusoe.ai/v1` | `https://vm.massedcompute.com/api/v1` |\n| Transports | HTTP, stdio | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for gpu compute | not published | $5.43 per GPU-hour |\n| x402 | no | no |\n| Licence | Proprietary service under the Crusoe Cloud Platform Terms of Service. The Go client and the MCP server package are MIT. The CLI ships as binaries, and no licence file was found in the Terraform provider repository | Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT |\n| Tools exposed | 41 | 17 |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.Massed-Compute/mcp` |\n| Last release | 2026-10-08 | 2026-07-24 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | couldn't be read | 2026-07-22 |\n| Customer content may train models | couldn't be read | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | 7 npm/wk | 1 stars |\n\n## Verdicts\n\n**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.\n\n**Massed Compute.** The hosted MCP server and REST API accept OAuth grants or API tokens in read-only and full-access tiers, and all 17 tools carry typed schemas and safety annotations in a public server card. No status page, rate limit figures or API changelog were found, a launch has no idempotency key, and the governing terms could not be read.\n\n## Before you call either\n\n### Crusoe Cloud\n\n1. 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:\u003caccess_key_id\u003e:\u003csignature\u003e`.\n2. Use `https://api.cloud.crusoe.ai/v1`. Some docs pages and the MCP server still name `api.crusoecloud.com` and `/v1alpha5`.\n3. 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.\n4. 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.\n5. 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.\n\n### Massed Compute\n\n1. Use `https://vm.massedcompute.com/api/v1`. The older docs at api-docs.massedcompute.com describe a separate marketplace API on `api.massedcompute.com` whose keys come from support.\n2. Ask the owner for a read-only token unless the task must launch or terminate. Read-only credentials cannot call launch, restart, terminate or SSH key changes.\n3. Call `gpu_inventory_list` and `images_list` before `instances_launch`. Product names and image IDs are free values, and SXM-only images do not run on PCIe cards.\n4. Expect 402 on launch until the owner has added credit and set a recharge amount and threshold. List instances before retrying a launch.\n5. Terminate to end billing. Stopping keeps the full hourly charge, and termination deletes the instance data.\n\n## Questions\n\n### Which is better for AI agents, Crusoe Cloud or Massed Compute?\n\nCrusoe Cloud scores 63.4 (B) on agent readiness against Massed Compute's 42.3 (E), and leads in 6 of 7 scored categories. Massed Compute leads on agent ergonomics.\n\n### Do Crusoe Cloud and Massed Compute need an API key?\n\nCrusoe Cloud needs an API key. Massed Compute takes an API key or an OAuth sign-in.\n\n### Can an agent call Crusoe Cloud and Massed Compute without installing anything?\n\nYes. Crusoe Cloud has a hosted endpoint at https://api.cloud.crusoe.ai/v1 and Massed Compute at https://vm.massedcompute.com/api/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.json, and with the fewest tokens: https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"crusoe-cloud\", \"b\": \"massed-compute\"}`. From a terminal: `anchor compare crusoe-cloud massed-compute`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/crusoe-cloud.json and https://www.anchorterminal.com/api/v1/tools/massed-compute.json\n\n## Other comparisons with Crusoe Cloud or Massed Compute\n\n- [Baseten vs Crusoe Cloud](https://www.anchorterminal.com/compare/baseten-vs-crusoe-cloud.md)\n- [Baseten vs Massed Compute](https://www.anchorterminal.com/compare/baseten-vs-massed-compute.md)\n- [Beam vs Crusoe Cloud](https://www.anchorterminal.com/compare/beam-vs-crusoe-cloud.md)\n- [Beam vs Massed Compute](https://www.anchorterminal.com/compare/beam-vs-massed-compute.md)\n- [Cerebrium vs Crusoe Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-crusoe-cloud.md)\n- [Cerebrium vs Massed Compute](https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.md)\n- [CoreWeave vs Crusoe Cloud](https://www.anchorterminal.com/compare/coreweave-vs-crusoe-cloud.md)\n- [CoreWeave vs Massed Compute](https://www.anchorterminal.com/compare/coreweave-vs-massed-compute.md)\n- [Crusoe Cloud vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/crusoe-cloud-vs-hugging-face-inference-endpoints.md)\n- [Crusoe Cloud vs Hyperbolic](https://www.anchorterminal.com/compare/crusoe-cloud-vs-hyperbolic.md)\n- [Crusoe Cloud vs Koyeb](https://www.anchorterminal.com/compare/crusoe-cloud-vs-koyeb.md)\n- [Crusoe Cloud vs Lambda Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda.md)\n- [Crusoe Cloud vs Modal](https://www.anchorterminal.com/compare/crusoe-cloud-vs-modal.md)\n- [Crusoe Cloud vs Nebius AI Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-nebius-ai-cloud.md)\n- [Crusoe Cloud vs Northflank](https://www.anchorterminal.com/compare/crusoe-cloud-vs-northflank.md)\n- [Crusoe Cloud vs Replicate Deployments](https://www.anchorterminal.com/compare/crusoe-cloud-vs-replicate-deploy.md)\n- [Crusoe Cloud vs Runpod](https://www.anchorterminal.com/compare/crusoe-cloud-vs-runpod.md)\n- [Crusoe Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute.md)\n- [Crusoe Cloud vs Vast.ai](https://www.anchorterminal.com/compare/crusoe-cloud-vs-vast-ai.md)\n- [Crusoe Cloud vs Verda](https://www.anchorterminal.com/compare/crusoe-cloud-vs-verda.md)\n- [Hugging Face Inference Endpoints vs Massed Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute.md)\n- [Hyperbolic vs Massed Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute.md)\n- [Koyeb vs Massed Compute](https://www.anchorterminal.com/compare/koyeb-vs-massed-compute.md)\n- [Lambda Cloud vs Massed Compute](https://www.anchorterminal.com/compare/lambda-vs-massed-compute.md)\n- [Massed Compute vs Modal](https://www.anchorterminal.com/compare/massed-compute-vs-modal.md)\n- [Massed Compute vs Nebius AI Cloud](https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud.md)\n- [Massed Compute vs Northflank](https://www.anchorterminal.com/compare/massed-compute-vs-northflank.md)\n- [Massed Compute vs Replicate Deployments](https://www.anchorterminal.com/compare/massed-compute-vs-replicate-deploy.md)\n- [Massed Compute vs Runpod](https://www.anchorterminal.com/compare/massed-compute-vs-runpod.md)\n- [Massed Compute vs Thunder Compute](https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute.md)\n- [Massed Compute vs Vast.ai](https://www.anchorterminal.com/compare/massed-compute-vs-vast-ai.md)\n- [Massed Compute vs Verda](https://www.anchorterminal.com/compare/massed-compute-vs-verda.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Crusoe Cloud vs Massed Compute", "url": "" } ], "description": "Crusoe Cloud scores 63.4 (B) to Massed Compute's 42.3 (E) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Crusoe Cloud B 63.4", "Massed Compute E 42.3", "scores" ], "h1": "Crusoe Cloud vs Massed Compute", "image": "https://www.anchorterminal.com/assets/og/compare-crusoe-cloud-vs-massed-compute.png", "path": "/compare/crusoe-cloud-vs-massed-compute", "published": "2026-10-01", "section": "tools", "title": "Crusoe Cloud vs Massed Compute for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute" }, "tokens": { "markdown": 3000, "slim": 730 }, "version": 1 }