{ "data": { "a": { "slug": "cerebrium", "name": "Cerebrium", "vendor": "Cerebrium Inc.", "vendorUrl": "https://www.cerebrium.ai", "kind": "platform", "category": "gpu-compute", "summary": "Cerebrium is a serverless platform for running your own models and code on GPUs and CPUs. A CLI packages code into containers served as REST, streaming and WebSocket endpoints, managed through a REST API.", "url": "https://www.anchorterminal.com/tools/cerebrium", "markdownUrl": "https://www.anchorterminal.com/tools/cerebrium.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cerebrium.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cerebrium.json", "repo": "https://github.com/CerebriumAI/cerebrium", "license": "Proprietary service under Cerebrium's terms of service. The CLI is MIT", "transports": [ "http" ], "remoteUrl": "https://rest.cerebrium.ai", "packages": [ { "registry": "pypi", "name": "cerebrium" } ], "auth": "api-key", "authNotes": "Two credentials. A service account token, created in the dashboard or over the API with an expiry of up to one year and a list of granted projects, authenticates the CLI (`CEREBRIUM_SERVICE_ACCOUNT_TOKEN`) and the management API at rest.cerebrium.ai as `Authorization: Bearer`. A project API key (a JWT) authenticates calls to deployed endpoints, and only when `cerebrium.toml` sets `disable_auth = false`. Signup and `cerebrium login` are browser flows.", "pricing": "freemium", "pricingNotes": "Hobby plan is $0 a month plus compute, Standard $100 a month plus compute, Enterprise on request. GPU, CPU and memory bill per second, from T4 at $0.000164 a second ($0.59 an hour) to H100 at $0.000944 ($3.40) and B200 at $0.00167 ($6.01). CPU $0.00000655 a vCPU-second, memory $0.00000222 a GB-second, storage $0.05 a GB-month after 100 GB free. Listed rates are for the default interruptible tier, and `protected` compute costs twice as much. Cold-start time is free, builds and model initialisation are billed. An account can start on Hobby without a contract. The pricing page does not say whether a card is needed or state a free compute allowance (https://www.cerebrium.ai/pricing, https://cerebrium.ai/docs/calculating-cost).", "priceSummary": "$0.0236 / vCPU-hr", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI spec or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 920, "asOf": "2026-10-08" }, "docsUrl": "https://cerebrium.ai/docs", "llmsTxt": "https://cerebrium.ai/docs/llms.txt", "openapi": "https://s3.eu-west-1.amazonaws.com/www.cerebrium.ai/openapi_spec.json", "capabilities": [ "compute.gpu", "compute.serverless", "compute.endpoints", "compute.batch", "compute.containers" ], "tags": [ "hosted", "freemium", "serverless", "gpu", "cli", "openapi", "llms-txt", "python", "async-jobs", "multi-region", "status-page", "soc2", "hipaa" ], "lastRelease": "2026-09-16", "graded": true, "anchor": { "graded": true, "score": 55.3, "grade": "C", "agentReady": false, "rank": 660, "ranked": true, "rankOf": 950, "categoryRank": 13, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 49, "maintenance": 75, "payments": 30, "reliability": 48, "schema": 70, "security": 60, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Per-second GPU prices are public, a 94-operation OpenAPI spec covers the management API, and service account tokens expire and are limited to named projects. Deployed endpoints are callable without a token unless `disable_auth = false` is set, and no request rate limits, 429 handling or SLA were found in the reviewed documentation.", "bestFor": "Teams serving their own models as real-time endpoints (voice, LLM, image) who want per-second billing, multi-region placement and a scriptable management API.", "strengths": [ "Per-second prices for ten GPU types published without a login, from T4 at $0.59 an hour to B200 at $6.01", "Public OpenAPI 3.0 spec for the management API at rest.cerebrium.ai, with 94 operations, plus llms.txt and Markdown docs", "Service account tokens carry an expiry of up to one year and a list of 1 to 50 granted projects", "Audit log of 22 actions with actor, IP address and outcome, readable over the API on Standard and Enterprise", "Status page with 11 components and 90 days of incident history, and five CLI releases between 7 August and 16 September 2026" ], "weaknesses": [ "`disable_auth` defaults to true, so a deployed endpoint answers without a token unless the owner changes it", "No request rate limits, 429 guidance, idempotency keys or SLA found in the reviewed documentation", "Several multi-hour degradations of the Inference API between 15 July and 2 September 2026, and a 10-minute outage on 21 July", "No deprecation policy, platform changelog or public subprocessor list found", "The CLI stores tokens in plaintext in `~/.cerebrium/config.yaml` with mode 0644, per its own SECURITY.md" ], "agentNotes": [ "Set `disable_auth = false` in `cerebrium.toml` before deploying. The default leaves the endpoint callable by anyone with the URL", "Authenticate headless with `CEREBRIUM_SERVICE_ACCOUNT_TOKEN`. `cerebrium login` opens a browser", "Raise `response_grace_period` for long work. It defaults to 15 minutes and async runs stop at 12 hours", "Send `?async=true` to get a `run_id` with HTTP 202, and add `webhookEndpoint` because async calls return no result to the caller", "Check the plan before choosing hardware. A100, H100, H200, B200 and RTX PRO 6000 need Standard, and `protected` compute bills at twice the listed rate" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.3 } ], "editorialScores": { "ergonomics": 49, "maintenance": 75, "payments": 30, "reliability": 48, "schema": 70, "security": 60, "transparency": 45 }, "provenanceScore": 80 }, "connect": { "install": "pip install cerebrium \u0026\u0026 cerebrium login", "http": "curl --location --request POST 'https://api.cerebrium.ai/v4/p-xxxxxxxx/{app-name}/{function}' \\\n --header 'Authorization: Bearer \u003cJWT_TOKEN\u003e' \\\n --header 'Content-Type: application/json' \\\n --data '{\"function_param\": \"data\"}'" }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/cerebrium" }, "area": "models", "unitPrices": [ { "item": "B200 180 GB", "unit": "gpu-hour", "usd": 6.01, "note": "$0.00167 a second, interruptible tier" }, { "item": "H200 141 GB", "unit": "gpu-hour", "usd": 4.2, "note": "$0.001166 a second, interruptible tier" }, { "item": "H100 80 GB", "unit": "gpu-hour", "usd": 3.4, "note": "$0.000944 a second, interruptible tier" }, { "item": "RTX PRO 6000 96 GB", "unit": "gpu-hour", "usd": 2.5, "note": "$0.000694 a second, interruptible tier" }, { "item": "A100 80 GB", "unit": "gpu-hour", "usd": 2.1, "note": "$0.000583 a second, interruptible tier" }, { "item": "A100 40 GB", "unit": "gpu-hour", "usd": 2, "note": "$0.000555 a second, interruptible tier" }, { "item": "L40s 48 GB", "unit": "gpu-hour", "usd": 1.95, "note": "$0.000542 a second, interruptible tier" }, { "item": "A10 24 GB", "unit": "gpu-hour", "usd": 1.1, "note": "$0.000306 a second, interruptible tier" }, { "item": "L4 24 GB", "unit": "gpu-hour", "usd": 0.8, "note": "$0.000222 a second, interruptible tier" }, { "item": "T4 16 GB", "unit": "gpu-hour", "usd": 0.59, "note": "$0.000164 a second, interruptible tier" }, { "item": "CPU-only compute", "unit": "vcpu-hour", "usd": 0.0236, "note": "$0.00000655 a vCPU-second, memory extra at $0.00000222 a GB-second" }, { "item": "Persistent storage", "unit": "gb-month", "usd": 0.05, "note": "First 100 GB free" }, { "item": "Standard plan", "unit": "month", "usd": 100, "note": "Plus compute" } ], "provenance": { "legalEntity": "Cerebrium Inc.", "domain": "cerebrium.ai", "domainRegistered": "2021-06-11", "endpointOnVendorDomain": true, "terms": "https://www.cerebrium.ai/terms-of-service", "privacy": "https://www.cerebrium.ai/privacy", "statusPage": "https://status.cerebrium.ai", "changelog": "https://github.com/CerebriumAI/cerebrium/releases", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms of service name Cerebrium Inc and say they are governed by the laws of the United Kingdom. The privacy policy names Cerebrium Inc. as data controller at 251 Little Falls Drive, Wilmington, Delaware.", "The terms of service are the only terms Cerebrium publishes. They cover accounts, subscriptions and the Service, and the OpenAPI spec names them as the API's licence. Neither document states a date.", "Deployed endpoints answer at api.cerebrium.ai and the management API at rest.cerebrium.ai. The OpenAPI file is served from an AWS S3 bucket.", "cerebrium.ai/.well-known/security.txt and cerebrium.ai/security.txt returned 404 on 8 October 2026. The CLI repository's SECURITY.md and the docs give security@cerebrium.ai.", "The changelog link is the CLI's GitHub releases. No platform changelog was found. Domain registration date from RDAP." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cerebrium.json", "live": { "slug": "cerebrium", "probe": { "target": "https://rest.cerebrium.ai", "method": "get", "lastAt": "2026-10-10T02:07:04.744542549Z", "lastOk": true, "lastStatus": 403, "lastMs": 271, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 253, "p95ms24h": 312, "samples24h": 250, "samples30d": 342, "days": [ { "date": "2026-10-08", "probes": 70, "ok": 70 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 22, "ok": 22 } ] }, "vendorStatus": { "page": "https://status.cerebrium.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:12.234295154Z" }, "versions": [ { "registry": "github", "name": "CerebriumAI/cerebrium", "version": "v2.9.0", "released": "2026-09-16", "seenAt": "2026-10-09T16:44:43.647924716Z" }, { "registry": "pypi", "name": "cerebrium", "version": "2.9.0", "released": "2026-09-16", "seenAt": "2026-10-09T16:44:43.4152983Z" } ], "githubStars": 6, "pypiWeekly": 715, "securityTxt": { "url": "https://cerebrium.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:39:42.713281389Z" }, "llmsTxt": { "url": "https://cerebrium.ai/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:01:34.821130883Z" }, "pages": [ { "url": "https://www.cerebrium.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:48:57.464678886Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "be1ada48db42" }, { "url": "https://www.cerebrium.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:48:59.532332202Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "017a8d228768" }, { "url": "https://www.cerebrium.ai/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:49:01.872731878Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a99804810a11" } ], "updatedAt": "2026-10-10T02:07:04.744542549Z" } }, "answer": "Cerebrium scores 55.3 (C) on agent readiness against Massed Compute's 42.3 (E), and leads in 5 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-10T02:07:15.43079726Z", "lastOk": true, "lastStatus": 200, "lastMs": 559, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 563, "p95ms24h": 1577, "samples24h": 107, "samples30d": 107, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 22, "ok": 22 } ] }, "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-10T02:07:15.43079726Z" } }, "facts": [ { "a": "Model platform", "b": "HTTP API", "name": "Kind" }, { "a": "Cerebrium Inc.", "b": "Massed Compute", "name": "Vendor" }, { "a": "https://rest.cerebrium.ai", "b": "https://vm.massedcompute.com/api/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "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 Cerebrium's terms of service. The CLI is MIT", "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": "none", "b": "17", "name": "Tools exposed" }, { "a": "no", "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-09-16", "b": "2026-07-24", "name": "Last release" }, { "a": "no date given", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-07-22", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "920 PyPI/wk", "b": "1 stars", "name": "Popularity" } ], "faq": [ { "answer": "Cerebrium scores 55.3 (C) on agent readiness against Massed Compute's 42.3 (E), and leads in 5 of 7 scored categories. Massed Compute leads on agent ergonomics.", "question": "Which is better for AI agents, Cerebrium or Massed Compute?" }, { "answer": "Yes. Cerebrium has a hosted endpoint at https://rest.cerebrium.ai and Massed Compute at https://vm.massedcompute.com/api/v1.", "question": "Can an agent call Cerebrium and Massed Compute without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 48 against 20", "Payments \u0026 pricing, 30 against 20", "Maintenance \u0026 community, 75 against 51" ], "also": [ "No incidents deducted, where Massed Compute loses 5 points for them" ], "goodFor": "Teams serving their own models as real-time endpoints (voice, LLM, image) who want per-second billing, multi-region placement and a scriptable management API.", "slug": "cerebrium", "watchFor": "`disable_auth` defaults to true, so a deployed endpoint answers without a token unless the owner changes it" }, { "aheadOn": [ "Agent ergonomics, 56 against 49" ], "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-cerebrium.json", "title": "Baseten vs Cerebrium", "url": "https://www.anchorterminal.com/compare/baseten-vs-cerebrium" }, { "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-cerebrium.json", "title": "Beam vs Cerebrium", "url": "https://www.anchorterminal.com/compare/beam-vs-cerebrium" }, { "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-coreweave.json", "title": "Cerebrium vs CoreWeave", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-coreweave" }, { "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-hugging-face-inference-endpoints.json", "title": "Cerebrium vs Hugging Face Inference Endpoints", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-hugging-face-inference-endpoints" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-hyperbolic.json", "title": "Cerebrium vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-hyperbolic" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-koyeb.json", "title": "Cerebrium vs Koyeb", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-koyeb" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-lambda.json", "title": "Cerebrium vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-lambda" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-modal.json", "title": "Cerebrium vs Modal", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-modal" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-nebius-ai-cloud.json", "title": "Cerebrium vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-northflank.json", "title": "Cerebrium vs Northflank", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-replicate-deploy.json", "title": "Cerebrium vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-runpod.json", "title": "Cerebrium vs Runpod", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-runpod" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-thunder-compute.json", "title": "Cerebrium vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-vast-ai.json", "title": "Cerebrium vs Vast.ai", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-verda.json", "title": "Cerebrium vs Verda", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-verda" }, { "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-massed-compute.json", "title": "Crusoe Cloud vs Massed Compute", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute" }, { "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": 28, "cerebrium": 48, "edge": "cerebrium", "key": "reliability", "massed-compute": 20, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "cerebrium": 70, "edge": "cerebrium", "key": "schema", "massed-compute": 69, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 7, "cerebrium": 49, "edge": "massed-compute", "key": "ergonomics", "massed-compute": 56, "name": "Agent ergonomics", "weight": 13 }, { "by": 1, "cerebrium": 60, "edge": "massed-compute", "key": "security", "massed-compute": 61, "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "cerebrium": 30, "edge": "cerebrium", "key": "payments", "massed-compute": 20, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 24, "cerebrium": 75, "edge": "cerebrium", "key": "maintenance", "massed-compute": 51, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 2, "cerebrium": 63, "edge": "cerebrium", "key": "transparency", "massed-compute": 61, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Cerebrium scores 55.3 (C) on agent readiness against Massed Compute's 42.3 (E), and leads in 5 of 7 scored categories. Massed Compute leads on agent ergonomics. Both do gpu compute.", "verdicts": { "cerebrium": "Per-second GPU prices are public, a 94-operation OpenAPI spec covers the management API, and service account tokens expire and are limited to named projects. Deployed endpoints are callable without a token unless `disable_auth = false` is set, and no request rate limits, 429 handling or SLA were found in the reviewed documentation.", "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/cerebrium-vs-massed-compute", "json": "https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.md", "slim": "https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.min.md" }, "markdown": "Cerebrium scores 55.3 (C) on agent readiness against Massed Compute's 42.3 (E), and leads in 5 of 7 scored categories. Massed Compute leads on agent ergonomics. Both do gpu compute.\n\n- Cerebrium: grade C, 55.3/100, rank #660 of 950. Markdown https://www.anchorterminal.com/tools/cerebrium.md · JSON https://www.anchorterminal.com/api/v1/tools/cerebrium.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### Cerebrium (C)\n\nGood for: Teams serving their own models as real-time endpoints (voice, LLM, image) who want per-second billing, multi-region placement and a scriptable management API.\n\nAhead on:\n- Reliability, 48 against 20\n- Payments \u0026 pricing, 30 against 20\n- Maintenance \u0026 community, 75 against 51\n\nAlso in its favour:\n- No incidents deducted, where Massed Compute loses 5 points for them\n\nWatch for: `disable_auth` defaults to true, so a deployed endpoint answers without a token unless the owner changes it\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 49\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 | Cerebrium | Massed Compute | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 48 | 20 | Cerebrium +28 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 69 | Cerebrium +1 |\n| Agent ergonomics | 13% (16.2 this run) | 49 | 56 | Massed Compute +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 61 | Massed Compute +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 20 | Cerebrium +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 51 | Cerebrium +24 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 61 | Cerebrium +2 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **55.3 · C** | **42.3 · E** | |\n\n## Facts side by side\n\n| Fact | Cerebrium | Massed Compute |\n| --- | --- | --- |\n| Kind | Model platform | HTTP API |\n| Vendor | Cerebrium Inc. | Massed Compute |\n| Hosted endpoint | `https://rest.cerebrium.ai` | `https://vm.massedcompute.com/api/v1` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| Price for gpu compute | not published | $5.43 per GPU-hour |\n| x402 | no | no |\n| Licence | Proprietary service under Cerebrium's terms of service. The CLI is MIT | 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 | none | 17 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.Massed-Compute/mcp` |\n| Last release | 2026-09-16 | 2026-07-24 |\n| Terms last updated | no date given | couldn't be read |\n| Privacy policy last updated | no date given | 2026-07-22 |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | yes | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | yes | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | 920 PyPI/wk | 1 stars |\n\n## Verdicts\n\n**Cerebrium.** Per-second GPU prices are public, a 94-operation OpenAPI spec covers the management API, and service account tokens expire and are limited to named projects. Deployed endpoints are callable without a token unless `disable_auth = false` is set, and no request rate limits, 429 handling or SLA were found in the reviewed documentation.\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### Cerebrium\n\n1. Set `disable_auth = false` in `cerebrium.toml` before deploying. The default leaves the endpoint callable by anyone with the URL\n2. Authenticate headless with `CEREBRIUM_SERVICE_ACCOUNT_TOKEN`. `cerebrium login` opens a browser\n3. Raise `response_grace_period` for long work. It defaults to 15 minutes and async runs stop at 12 hours\n4. Send `?async=true` to get a `run_id` with HTTP 202, and add `webhookEndpoint` because async calls return no result to the caller\n5. Check the plan before choosing hardware. A100, H100, H200, B200 and RTX PRO 6000 need Standard, and `protected` compute bills at twice the listed rate\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, Cerebrium or Massed Compute?\n\nCerebrium scores 55.3 (C) on agent readiness against Massed Compute's 42.3 (E), and leads in 5 of 7 scored categories. Massed Compute leads on agent ergonomics.\n\n### Can an agent call Cerebrium and Massed Compute without installing anything?\n\nYes. Cerebrium has a hosted endpoint at https://rest.cerebrium.ai 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/cerebrium-vs-massed-compute.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"cerebrium\", \"b\": \"massed-compute\"}`. From a terminal: `anchor compare cerebrium massed-compute`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cerebrium.json and https://www.anchorterminal.com/api/v1/tools/massed-compute.json\n\n## Other comparisons with Cerebrium or Massed Compute\n\n- [Baseten vs Cerebrium](https://www.anchorterminal.com/compare/baseten-vs-cerebrium.md)\n- [Baseten vs Massed Compute](https://www.anchorterminal.com/compare/baseten-vs-massed-compute.md)\n- [Beam vs Cerebrium](https://www.anchorterminal.com/compare/beam-vs-cerebrium.md)\n- [Beam vs Massed Compute](https://www.anchorterminal.com/compare/beam-vs-massed-compute.md)\n- [Cerebrium vs CoreWeave](https://www.anchorterminal.com/compare/cerebrium-vs-coreweave.md)\n- [Cerebrium vs Crusoe Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-crusoe-cloud.md)\n- [Cerebrium vs Hugging Face Inference Endpoints](https://www.anchorterminal.com/compare/cerebrium-vs-hugging-face-inference-endpoints.md)\n- [Cerebrium vs Hyperbolic](https://www.anchorterminal.com/compare/cerebrium-vs-hyperbolic.md)\n- [Cerebrium vs Koyeb](https://www.anchorterminal.com/compare/cerebrium-vs-koyeb.md)\n- [Cerebrium vs Lambda Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-lambda.md)\n- [Cerebrium vs Modal](https://www.anchorterminal.com/compare/cerebrium-vs-modal.md)\n- [Cerebrium vs Nebius AI Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-nebius-ai-cloud.md)\n- [Cerebrium vs Northflank](https://www.anchorterminal.com/compare/cerebrium-vs-northflank.md)\n- [Cerebrium vs Replicate Deployments](https://www.anchorterminal.com/compare/cerebrium-vs-replicate-deploy.md)\n- [Cerebrium vs Runpod](https://www.anchorterminal.com/compare/cerebrium-vs-runpod.md)\n- [Cerebrium vs Thunder Compute](https://www.anchorterminal.com/compare/cerebrium-vs-thunder-compute.md)\n- [Cerebrium vs Vast.ai](https://www.anchorterminal.com/compare/cerebrium-vs-vast-ai.md)\n- [Cerebrium vs Verda](https://www.anchorterminal.com/compare/cerebrium-vs-verda.md)\n- [CoreWeave vs Massed Compute](https://www.anchorterminal.com/compare/coreweave-vs-massed-compute.md)\n- [Crusoe Cloud vs Massed Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.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": "Cerebrium vs Massed Compute", "url": "" } ], "description": "Cerebrium scores 55.3 (C) to Massed Compute's 42.3 (E) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Cerebrium C 55.3", "Massed Compute E 42.3", "scores" ], "h1": "Cerebrium vs Massed Compute", "image": "https://www.anchorterminal.com/assets/og/compare-cerebrium-vs-massed-compute.png", "path": "/compare/cerebrium-vs-massed-compute", "published": "2026-10-01", "section": "tools", "title": "Cerebrium vs Massed Compute for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute" }, "tokens": { "markdown": 2750, "slim": 780 }, "version": 1 }