{ "data": { "a": { "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", "dns": "massed-compute.grade.anchorterminal.com", "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.6, "grade": "E", "agentReady": false, "rank": 1274, "ranked": true, "rankOf": 1510, "categoryRank": 20, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 51, "payments": 20, "reliability": 20, "schema": 69, "security": 61, "transparency": 64 }, "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": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.6 } ], "editorialScores": { "ergonomics": 56, "maintenance": 51, "payments": 20, "reliability": 20, "schema": 69, "security": 61, "transparency": 53 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-10-09", "maintenance": "2026-10-09", "payments": "2026-10-09", "reliability": "2026-10-09", "schema": "2026-10-09", "security": "2026-10-09", "transparency": "2026-10-09" }, "last": "2026-10-09", "lastMoved": "2026-10-29", "oldest": "2026-10-09", "stale": false, "staleAfterDays": 90 } }, "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": 74 }, "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-11-07T19:22:18.574728018Z", "lastOk": true, "lastStatus": 200, "lastMs": 630, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 549, "p95ms24h": 669, "samples24h": 238, "samples30d": 7215, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "versions": [ { "registry": "github", "name": "Massed-Compute/massed-compute-mcp", "version": "v1.1.0", "released": "2026-07-24", "seenAt": "2026-11-06T23:42:49.311362696Z" }, { "registry": "mcp-registry", "name": "io.github.Massed-Compute/mcp", "version": "1.1.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "massed-compute-mcp", "version": "1.1.0", "seenAt": "2026-11-06T23:42:48.859518899Z" }, { "registry": "pypi", "name": "massed-compute-mcp", "version": "1.1.0", "released": "2026-07-24", "seenAt": "2026-11-06T23:42:49.071933841Z" } ], "githubStars": 1, "npmWeekly": 77, "pypiWeekly": 17, "securityTxt": { "url": "https://massedcompute.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:02.274162876Z" }, "llmsTxt": { "url": "https://massedcompute.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:57.417060512Z" }, "domain": { "domain": "massedcompute.com", "registered": "2021-10-28", "source": "https://rdap.verisign.com/com/v1/domain/massedcompute.com", "checkedAt": "2026-11-01T14:25:32.867199278Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/Massed-Compute/massed-compute-mcp/main/CHANGELOG.md", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:18:41.214002665Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7fa22cb79429" }, { "url": "https://vm.massedcompute.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:23:27.644351764Z", "changedAt": "2026-10-12T20:00:14.517270313Z", "fingerprint": "5bfc6abb017e" }, { "url": "https://massedcompute.com/legal/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:13:53.053062677Z", "changedAt": "2026-10-15T21:30:11.503135109Z", "fingerprint": "d9918bcc127e" }, { "url": "https://massedcompute.com/legal/terms-conditions/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:13:55.216473938Z", "changedAt": "2026-10-15T21:30:13.683160873Z", "fingerprint": "096bd30def3c" } ], "mcpTools": { "url": "https://vm.massedcompute.com/api/mcp", "checkedAt": "2026-11-07T01:46:11.470870377Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:11.470870377Z" }, "github": { "repo": "massed-compute/massed-compute-mcp", "checkedAt": "2026-11-02T09:03:50.994775734Z", "stars": 1, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-29T22:15:30Z", "openIssues": 0, "openPRs": 11, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 2, "ci": { "branch": "main", "runs": 10, "success": 9, "failure": 1, "other": 0, "latest": "success", "latestAt": "2026-08-18T15:31:37Z" } }, "updatedAt": "2026-11-07T19:22:18.574728018Z" } }, "answer": "Together GPU Clusters scores 58.1 (C) on agent readiness against Massed Compute's 42.6 (E), and leads in 5 of 7 scored categories.", "b": { "slug": "together-gpu-clusters", "name": "Together GPU Clusters", "vendor": "Together AI", "vendorUrl": "https://www.together.ai", "kind": "http-api", "category": "gpu-compute", "summary": "Together GPU Clusters rents multi-node NVIDIA H100, H200, B200 and B300 clusters with InfiniBand and shared storage, run as Kubernetes or Slurm, by the GPU-hour. Clusters are created and scaled from the console, the tg CLI, SDKs or REST API.", "url": "https://www.anchorterminal.com/tools/together-gpu-clusters", "markdownUrl": "https://www.anchorterminal.com/tools/together-gpu-clusters.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/together-gpu-clusters.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json", "dns": "together-gpu-clusters.grade.anchorterminal.com", "repo": "https://github.com/togethercomputer/together-py", "license": "Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT", "transports": [], "remoteUrl": "https://api.together.ai/v1/compute/clusters", "packages": [ { "registry": "pypi", "name": "together" }, { "registry": "npm", "name": "together-ai" } ], "auth": "api-key", "authNotes": "Bearer `TOGETHER_API_KEY`, scoped to a project, revocable and optionally expiring, the same keys as Together's other APIs. Only a project admin's key returns the cluster's admin kubeconfig. Team members can reach the Kubernetes API through OIDC with their own identity provider, and SSH uses OIDC or uploaded keys.", "pricing": "usage", "pricingNotes": "On-demand from $3.99 per GPU-hour (H100) to $9.99 (B300); reserved 3 to 180 days from $3.19 to $7.99; preemptible (preview) from $1.99. Storage per GiB-month. No ingress or egress fees. Reservations are prepaid and non-refundable, and creation needs enough credit to cover them.", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the GPU clusters docs, billing pages or OpenAPI document (checked 2026-11-06). An exhausted balance returns 402 to scale requests with no payment requirements.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.together.ai/docs/gpu-clusters-overview", "llmsTxt": "https://docs.together.ai/llms.txt", "openapi": "https://github.com/togethercomputer/openapi", "capabilities": [ "compute.gpu", "compute.containers", "compute.batch" ], "tags": [ "hosted", "official", "usage", "prepaid", "openapi", "llms-txt", "kubernetes", "slurm", "python", "typescript", "cli", "h100", "b200" ], "lastRelease": "2026-10-22", "graded": true, "anchor": { "graded": true, "score": 58.1, "grade": "C", "agentReady": false, "rank": 768, "ranked": true, "rankOf": 1510, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 55, "maintenance": 75, "payments": 20, "reliability": 38, "schema": 92, "security": 68, "transparency": 65 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Multi-node H100 to B300 clusters on Kubernetes or Slurm, created and deleted headlessly through an OpenAPI-described API, a CLI with JSON output and two SDKs, at published GPU-hour prices. Clusters take 10 minutes to an hour to provision, can't be paused, and have no status component, SLA or idempotent create.", "bestFor": "Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters.", "strengths": [ "Public OpenAPI 3.1, llms.txt and Markdown docs, with an automation guide for CI pipelines", "Published per GPU-hour prices for on-demand, reserved and preemptible capacity, with no egress fees", "Kubernetes or Slurm on the same hardware, with InfiniBand and a persistent shared volume", "Automatic health checks and node repair, approved by hand or run automatically", "Project-scoped keys, admin-only kubeconfig and OIDC access for team members" ], "weaknesses": [ "Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero", "No status page component, SLA or published rate limits for GPU clusters", "No idempotency key on creation, so a retried create can bill a second cluster", "No free trial; reservations are prepaid and non-refundable", "Volumes bill until deleted and outlive the clusters they were attached to" ], "agentNotes": [ "Use `tg clusters`, not `tg beta clusters`, which stopped working with CLI 3.0 on 22 October 2026", "Pass `--json` and `--non-interactive`, poll `tg clusters retrieve` until status is Ready, and delete the cluster in a cleanup step", "Check for an existing cluster by name before retrying a create, since creation has no idempotency key", "Read live availability from the regions API and prices from the pricing page; the regions response has no prices", "Use a project admin's key when the task needs the kubeconfig, since other roles get none" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.1 } ], "editorialScores": { "ergonomics": 55, "maintenance": 75, "payments": 20, "reliability": 38, "schema": 92, "security": 68, "transparency": 46 }, "provenanceScore": 83, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "uv tool install \"together[cli]\"", "http": "curl -H \"Authorization: Bearer $TOGETHER_API_KEY\" https://api.together.ai/v1/compute/clusters" }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/together-gpu-clusters" }, "sameCompany": [ "together-inference", "together-fine-tuning", "together-code-sandbox" ], "area": "models", "unitPrices": [ { "item": "H100 on-demand", "unit": "gpu-hour", "usd": 3.99, "note": "reserved $3.69 to $3.19, preemptible $1.99" }, { "item": "H200 on-demand", "unit": "gpu-hour", "usd": 5.99, "note": "reserved $4.99 to $3.99, preemptible $2.99" }, { "item": "B200 on-demand", "unit": "gpu-hour", "usd": 8.19, "note": "reserved $7.99 to $6.79, preemptible $4.09" }, { "item": "B300 on-demand", "unit": "gpu-hour", "usd": 9.99, "note": "preemptible $4.99, reserved by sales" } ], "provenance": { "legalEntity": "Together Computer, Inc.", "domain": "together.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.together.ai/terms-of-service", "privacy": "https://www.together.ai/privacy", "statusPage": "https://status.together.ai", "changelog": "https://docs.together.ai/docs/changelog", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "Legal entity, terms, privacy and security.txt as on the Together AI Inference listing, checked 1 November 2026, and not re-read for this listing.", "docs.together.ai/robots.txt disallows only /cdn-cgi/ and /_next/, with Content-Signal ai-train=yes, search=yes, ai-input=yes. www.together.ai/robots.txt allows all.", "status.together.ai has no component for GPU clusters on 6 November 2026." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/together-gpu-clusters.json", "live": { "slug": "together-gpu-clusters", "probe": { "target": "https://api.together.ai/v1/compute/clusters", "method": "get", "lastAt": "2026-11-07T19:22:40.660879578Z", "lastOk": true, "lastStatus": 401, "lastMs": 263, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 493, "p95ms24h": 857, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "versions": [ { "registry": "github", "name": "togethercomputer/together-py", "version": "v3.1.1", "released": "2026-11-04", "seenAt": "2026-11-07T00:12:15.100983119Z" }, { "registry": "npm", "name": "together-ai", "version": "1.0.0", "seenAt": "2026-11-07T00:12:15.067840103Z" }, { "registry": "pypi", "name": "together", "version": "3.1.1", "released": "2026-11-04", "seenAt": "2026-11-07T00:12:14.921893617Z" } ], "githubStars": 12, "npmWeekly": 99619, "pypiWeekly": 424792, "securityTxt": { "url": "https://together.ai/.well-known/security.txt", "state": "valid", "expires": "2028-09-30T00:00:00.000Z", "checkedAt": "2026-11-07T16:00:47.073630606Z" }, "llmsTxt": { "url": "https://docs.together.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:12.138384896Z" }, "updatedAt": "2026-11-07T19:22:40.660879578Z" } }, "edges": [ { "by": 24, "category": "maintenance", "leads": "together-gpu-clusters", "name": "Maintenance \u0026 community", "reasons": { "a": "The newest release of the MCP wrapper is v1.1.0 of 24 July 2026, 77 days before the check. The hosted server has changed since, with fields in the server card that the July definitions lack, but no dated API changelog records it (20 of 30). One release and one dated changelog entry in the last 90 days (0). A dated wrapper changelog and a Discord server named as the fastest support route. No API changelog, and the repository shows six open issues or pull requests whose answers we did not read (7 of 15). Listed in the official MCP registry as `io.github.Massed-Compute/mcp` at 1.1.0, published 31 July 2026, with current npm and PyPI packages (15). CI tests Node 20 and 22 and Python 3.10 to 3.13 on three operating systems, with Dependabot, static analysis and a nightly check of the hosted endpoint. The npm package has no runtime dependencies (9 of 10).", "b": "Closed service. The newest cluster change is CLI and SDK 3.0 on 22 October 2026, 15 days before this check (30). Dated cluster entries in the 90 days from 8 August include 12, 18, 19, 24, 27 and 28 August, 10 September and 22 October (20). Dated changelog, a support portal and Discord, with responsiveness not tested (8). Python SDK 3.1 and TypeScript SDK 1.0 are current and cover clusters (15). SDK CI and dependencies weren't audited (2). 30+20+8+15+2 = 75." }, "scores": { "a": 51, "b": 75 } }, { "by": 23, "category": "schema", "leads": "together-gpu-clusters", "name": "Schema \u0026 documentation", "reasons": { "a": "A public OpenAPI 3.0 file covers the 14 REST operations, and a public server card lists all 17 MCP tools with JSON Schema inputs (25). massedcompute.com has an `llms.txt` that indexes marketing pages, and the vendor publishes an agent catalogue, the server card and four Markdown skills files. The docs sites have no `llms.txt` or Markdown copies (6 of 10). Tool descriptions state the purpose, the cost of a launch, when to search recipes first and when to confirm with the user. REST descriptions are one line each (16 of 20). Required fields are marked and extra properties are refused, but there are no enums, `productName` and `regionName` are free strings, and the OpenAPI file's required lists name `image_id` and `couponCode` where the properties are `imageId` and `coupon` (8 of 15). Every REST operation has a response example. Only 200 and 202 are documented, and errors appear only in a troubleshooting table and a deployment errors page (7 of 15). The path is versioned as `/api/v1` and the MCP wrapper has a dated changelog. No API changelog was found (7 of 15).", "b": "Public OpenAPI 3.1 for /v1/compute/clusters and shared volumes, MIT, embedded in every reference page (25). llms.txt and a Markdown twin of every page (10). The docs say when to choose Kubernetes or Slurm and each capacity type, and the management page carries instructions for agents on reporting live availability and prices (18). Enums for cluster type, billing type, GPU type and status, required fields marked (13). CLI, Python, TypeScript and console steps on each task, with 402 and 403 cases documented, though no error catalogue for the clusters API (11). Versioned SDKs and a dated changelog with cluster entries (15). 25+10+18+13+11+15 = 92." }, "scores": { "a": 69, "b": 92 } }, { "by": 18, "category": "reliability", "leads": "together-gpu-clusters", "name": "Reliability", "reasons": { "a": "Graded on the hosted lines for the MCP server and the REST API. No status page was found on the site, the docs, the pricing page or the repository (0). No incident history to read (5). The troubleshooting page documents a 429 for request limits with no figures (0). The same page says to wait a minute and retry, and every tool carries an `idempotentHint`, but `instances_launch` has no idempotency key (5 of 15). The on-demand page says 99.999 per cent uptime is guaranteed. No SLA document was found, the End User Licence Agreement promises support only under an order form or SLA, and the Terms \u0026 Conditions could not be read (0). The API is `/api/v1`, the server card is version 1.0.0 and nothing is labelled beta (10).", "b": "Read with the hosted lines. status.together.ai lists the website, the playground and serverless models with no component for GPU clusters, and a vendor page with no component for the product takes 15 in this run, as for Together's Code Sandbox and fine-tuning listings (15). No incident history for clusters can be read (5). No rate limits for the clusters API found (0). Together's docs give 429 and 503 backoff guidance for its APIs, per the inference listing's 1 November check, and the CLI has `--non-interactive` and `--json` for scripted retries, but creation has no idempotency key (8). No SLA for clusters found; the published 99% commitment covers provisioned inference throughput only (0). Generally available since 9 September 2025 and out of the CLI's beta paths since 22 October 2026, with preemptible nodes in preview (10). 15+5+0+8+0+10 = 38." }, "scores": { "a": 20, "b": 38 } }, { "by": 7, "category": "security", "leads": "together-gpu-clusters", "name": "Security \u0026 auth", "reasons": { "a": "OAuth with discovery from a 401 challenge, or named API tokens shown once and revoked one at a time. Both come in two tiers, read-only and full access, with no finer scopes. Secrets travel only in a header (26 of 30). The read-only tier blocks launch, restart, terminate and SSH key changes. Destructive tool descriptions ask the model to confirm with the user, and a published skill adds a disclosure step. No server-side confirmation was found (13 of 20). The MCP server redacts VM passwords from tool results. Recipes are vendor-written Markdown that tools tell the model to follow step by step, and the docs give no guidance on untrusted content (9 of 15). Connected Apps lists OAuth grants. No audit log or per-call history was found (3 of 15). The wrapper's SECURITY.md gives a disclosure address, a two-business-day acknowledgement and a 30-day fix target, and its CI runs static analysis and dependency audits. The site claims SOC 2 Type II and HIPAA with no report or trust page, and there is no security.txt or bug bounty (10 of 20).", "b": "Project-scoped API keys, revocable with optional expiry, read as Together's other listings read the same key model (30). Admin and editor roles with no read-only role. Only admins get the admin kubeconfig, which has cluster-admin rights, and OIDC lets editors use kubectl under RBAC. Deletes run without confirmation when `--non-interactive` is passed (8). The API returns cluster state, not third-party content (10). Invoices itemise reserved, on-demand and storage charges, and no audit log for cluster operations was found (5). security.txt with a HackerOne route, per the 1 November check of the inference listing (15). 30+8+10+5+15 = 68." }, "scores": { "a": 61, "b": 68 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Massed Compute", "b": "Together AI", "name": "Vendor" }, { "a": "https://vm.massedcompute.com/api/v1", "b": "https://api.together.ai/v1/compute/clusters", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$5.43 per GPU-hour", "b": "not published", "name": "Price for gpu compute" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT", "b": "Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT", "name": "Licence" }, { "a": "17", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.Massed-Compute/mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-07-24", "b": "2026-10-22", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-07-22", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "1 stars", "b": "none", "name": "Popularity" }, { "a": "3.3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Together GPU Clusters scores 58.1 (C) on agent readiness against Massed Compute's 42.6 (E), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Massed Compute or Together GPU Clusters?" }, { "answer": "Massed Compute takes an API key or an OAuth sign-in. Together GPU Clusters needs an API key.", "question": "Do Massed Compute and Together GPU Clusters need an API key?" }, { "answer": "Yes. Massed Compute has a hosted endpoint at https://vm.massedcompute.com/api/v1 and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.", "question": "Can an agent call Massed Compute and Together GPU Clusters without installing anything?" } ], "goodFor": [ { "aheadOn": null, "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" }, { "aheadOn": [ "Reliability, 38 against 20", "Schema \u0026 documentation, 92 against 69", "Security \u0026 auth, 68 against 61", "Maintenance \u0026 community, 75 against 51" ], "also": [ "No incidents deducted, where Massed Compute loses 5 points for them" ], "goodFor": "Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters.", "slug": "together-gpu-clusters", "watchFor": "Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero" } ], "history": { "massed-compute": [ { "causes": [ "time" ], "date": "2026-10-29", "delta": 0.2, "from": 42.4, "fromGrade": "E", "to": 42.6, "toGrade": "E" }, { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 42.5, "fromGrade": "E", "to": 42.4, "toGrade": "E" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 42.3, "fromGrade": "E", "to": 42.5, "toGrade": "E" } ], "together-gpu-clusters": null }, "job": { "capability": "compute.gpu", "name": "GPU compute" }, "others": [ { "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/baseten-vs-together-gpu-clusters.json", "title": "Baseten vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters" }, { "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/beam-vs-together-gpu-clusters.json", "title": "Beam vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters" }, { "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/cerebrium-vs-together-gpu-clusters.json", "title": "Cerebrium vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.json", "title": "Cloud Run GPUs vs Massed Compute", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.json", "title": "Cloud Run GPUs vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters" }, { "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/coreweave-vs-together-gpu-clusters.json", "title": "CoreWeave vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters" }, { "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/crusoe-cloud-vs-together-gpu-clusters.json", "title": "Crusoe Cloud vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.json", "title": "GPUsMarket vs Massed Compute", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.json", "title": "GPUsMarket vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters" }, { "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/hugging-face-inference-endpoints-vs-together-gpu-clusters.json", "title": "Hugging Face Inference Endpoints vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-together-gpu-clusters" }, { "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/hyperbolic-vs-together-gpu-clusters.json", "title": "Hyperbolic vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters" }, { "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/koyeb-vs-together-gpu-clusters.json", "title": "Koyeb vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters" }, { "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/lambda-vs-together-gpu-clusters.json", "title": "Lambda Cloud vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.json", "title": "Modal vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.json", "title": "Nebius AI Cloud vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.json", "title": "Northflank vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters.json", "title": "Replicate Deployments vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters.json", "title": "Runpod vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.json", "title": "Thunder Compute vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai.json", "title": "Together GPU Clusters vs Vast.ai", "url": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.json", "title": "Together GPU Clusters vs Verda", "url": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda" } ], "panel": null, "scores": [ { "by": 18, "edge": "together-gpu-clusters", "key": "reliability", "massed-compute": 20, "name": "Reliability", "together-gpu-clusters": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 23, "edge": "together-gpu-clusters", "key": "schema", "massed-compute": 69, "name": "Schema \u0026 documentation", "together-gpu-clusters": 92, "weight": 13 }, { "by": 1, "edge": "massed-compute", "key": "ergonomics", "massed-compute": 56, "name": "Agent ergonomics", "together-gpu-clusters": 55, "weight": 13 }, { "by": 7, "edge": "together-gpu-clusters", "key": "security", "massed-compute": 61, "name": "Security \u0026 auth", "together-gpu-clusters": 68, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "massed-compute": 20, "name": "Payments \u0026 pricing", "together-gpu-clusters": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 24, "edge": "together-gpu-clusters", "key": "maintenance", "massed-compute": 51, "name": "Maintenance \u0026 community", "together-gpu-clusters": 75, "weight": 7 }, { "by": 1, "edge": "together-gpu-clusters", "key": "transparency", "massed-compute": 64, "name": "Transparency \u0026 trust", "together-gpu-clusters": 65, "weight": 7 } ], "summary": "Together GPU Clusters scores 58.1 (C) on agent readiness against Massed Compute's 42.6 (E), and leads in 5 of 7 scored categories. Both do gpu compute.", "tasks": null, "tutorials": [], "verdicts": { "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.", "together-gpu-clusters": "Multi-node H100 to B300 clusters on Kubernetes or Slurm, created and deleted headlessly through an OpenAPI-described API, a CLI with JSON output and two SDKs, at published GPU-hour prices. Clusters take 10 minutes to an hour to provision, can't be paused, and have no status component, SLA or idempotent create." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters", "json": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.min.md" }, "markdown": "Together GPU Clusters scores 58.1 (C) on agent readiness against Massed Compute's 42.6 (E), and leads in 5 of 7 scored categories. Both do gpu compute.\n\n- Massed Compute: grade E, 42.6/100, rank #1274 of 1510. Markdown https://www.anchorterminal.com/tools/massed-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/massed-compute.json\n- Together GPU Clusters: grade C, 58.1/100, rank #768 of 1510. Markdown https://www.anchorterminal.com/tools/together-gpu-clusters.md · JSON https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json\n- Best GPU and serverless compute for AI workloads: https://www.anchorterminal.com/best/gpu-compute/index.md\n- All 231 gpu compute comparisons: https://www.anchorterminal.com/compare/gpu-compute/index.md\n\n## Which one, for what\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\nWatch for: No status page, incident history or security.txt was found on any of the vendor's hosts\n\n### Together GPU Clusters (C)\n\nGood for: Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters.\n\nAhead on:\n- Reliability, 38 against 20\n- Schema \u0026 documentation, 92 against 69\n- Security \u0026 auth, 68 against 61\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: Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Together GPU Clusters +24\n\n- Massed Compute (51): The newest release of the MCP wrapper is v1.1.0 of 24 July 2026, 77 days before the check. The hosted server has changed since, with fields in the server card that the July definitions lack, but no dated API changelog records it (20 of 30). One release and one dated changelog entry in the last 90 days (0). A dated wrapper changelog and a Discord server named as the fastest support route. No API changelog, and the repository shows six open issues or pull requests whose answers we did not read (7 of 15). Listed in the official MCP registry as `io.github.Massed-Compute/mcp` at 1.1.0, published 31 July 2026, with current npm and PyPI packages (15). CI tests Node 20 and 22 and Python 3.10 to 3.13 on three operating systems, with Dependabot, static analysis and a nightly check of the hosted endpoint. The npm package has no runtime dependencies (9 of 10).\n- Together GPU Clusters (75): Closed service. The newest cluster change is CLI and SDK 3.0 on 22 October 2026, 15 days before this check (30). Dated cluster entries in the 90 days from 8 August include 12, 18, 19, 24, 27 and 28 August, 10 September and 22 October (20). Dated changelog, a support portal and Discord, with responsiveness not tested (8). Python SDK 3.1 and TypeScript SDK 1.0 are current and cover clusters (15). SDK CI and dependencies weren't audited (2). 30+20+8+15+2 = 75.\n\n### Schema \u0026 documentation: Together GPU Clusters +23\n\n- Massed Compute (69): A public OpenAPI 3.0 file covers the 14 REST operations, and a public server card lists all 17 MCP tools with JSON Schema inputs (25). massedcompute.com has an `llms.txt` that indexes marketing pages, and the vendor publishes an agent catalogue, the server card and four Markdown skills files. The docs sites have no `llms.txt` or Markdown copies (6 of 10). Tool descriptions state the purpose, the cost of a launch, when to search recipes first and when to confirm with the user. REST descriptions are one line each (16 of 20). Required fields are marked and extra properties are refused, but there are no enums, `productName` and `regionName` are free strings, and the OpenAPI file's required lists name `image_id` and `couponCode` where the properties are `imageId` and `coupon` (8 of 15). Every REST operation has a response example. Only 200 and 202 are documented, and errors appear only in a troubleshooting table and a deployment errors page (7 of 15). The path is versioned as `/api/v1` and the MCP wrapper has a dated changelog. No API changelog was found (7 of 15).\n- Together GPU Clusters (92): Public OpenAPI 3.1 for /v1/compute/clusters and shared volumes, MIT, embedded in every reference page (25). llms.txt and a Markdown twin of every page (10). The docs say when to choose Kubernetes or Slurm and each capacity type, and the management page carries instructions for agents on reporting live availability and prices (18). Enums for cluster type, billing type, GPU type and status, required fields marked (13). CLI, Python, TypeScript and console steps on each task, with 402 and 403 cases documented, though no error catalogue for the clusters API (11). Versioned SDKs and a dated changelog with cluster entries (15). 25+10+18+13+11+15 = 92.\n\n### Reliability: Together GPU Clusters +18\n\n- Massed Compute (20): Graded on the hosted lines for the MCP server and the REST API. No status page was found on the site, the docs, the pricing page or the repository (0). No incident history to read (5). The troubleshooting page documents a 429 for request limits with no figures (0). The same page says to wait a minute and retry, and every tool carries an `idempotentHint`, but `instances_launch` has no idempotency key (5 of 15). The on-demand page says 99.999 per cent uptime is guaranteed. No SLA document was found, the End User Licence Agreement promises support only under an order form or SLA, and the Terms \u0026 Conditions could not be read (0). The API is `/api/v1`, the server card is version 1.0.0 and nothing is labelled beta (10).\n- Together GPU Clusters (38): Read with the hosted lines. status.together.ai lists the website, the playground and serverless models with no component for GPU clusters, and a vendor page with no component for the product takes 15 in this run, as for Together's Code Sandbox and fine-tuning listings (15). No incident history for clusters can be read (5). No rate limits for the clusters API found (0). Together's docs give 429 and 503 backoff guidance for its APIs, per the inference listing's 1 November check, and the CLI has `--non-interactive` and `--json` for scripted retries, but creation has no idempotency key (8). No SLA for clusters found; the published 99% commitment covers provisioned inference throughput only (0). Generally available since 9 September 2025 and out of the CLI's beta paths since 22 October 2026, with preemptible nodes in preview (10). 15+5+0+8+0+10 = 38.\n\n### Security \u0026 auth: Together GPU Clusters +7\n\n- Massed Compute (61): OAuth with discovery from a 401 challenge, or named API tokens shown once and revoked one at a time. Both come in two tiers, read-only and full access, with no finer scopes. Secrets travel only in a header (26 of 30). The read-only tier blocks launch, restart, terminate and SSH key changes. Destructive tool descriptions ask the model to confirm with the user, and a published skill adds a disclosure step. No server-side confirmation was found (13 of 20). The MCP server redacts VM passwords from tool results. Recipes are vendor-written Markdown that tools tell the model to follow step by step, and the docs give no guidance on untrusted content (9 of 15). Connected Apps lists OAuth grants. No audit log or per-call history was found (3 of 15). The wrapper's SECURITY.md gives a disclosure address, a two-business-day acknowledgement and a 30-day fix target, and its CI runs static analysis and dependency audits. The site claims SOC 2 Type II and HIPAA with no report or trust page, and there is no security.txt or bug bounty (10 of 20).\n- Together GPU Clusters (68): Project-scoped API keys, revocable with optional expiry, read as Together's other listings read the same key model (30). Admin and editor roles with no read-only role. Only admins get the admin kubeconfig, which has cluster-admin rights, and OIDC lets editors use kubectl under RBAC. Deletes run without confirmation when `--non-interactive` is passed (8). The API returns cluster state, not third-party content (10). Invoices itemise reserved, on-demand and storage charges, and no audit log for cluster operations was found (5). security.txt with a HackerOne route, per the 1 November check of the inference listing (15). 30+8+10+5+15 = 68.\n\n## Score by category\n\n| Category | Weight | Massed Compute | Together GPU Clusters | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 20 | 38 | Together GPU Clusters +18 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 69 | 92 | Together GPU Clusters +23 |\n| Agent ergonomics | 13% (16.2 this run) | 56 | 55 | Massed Compute +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 61 | 68 | Together GPU Clusters +7 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 51 | 75 | Together GPU Clusters +24 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 65 | Together GPU Clusters +1 |\n| Negative events | ≤15 | -5 | 0 | |\n| **Total** | | **42.6 · E** | **58.1 · C** | |\n\n## Facts side by side\n\n| Fact | Massed Compute | Together GPU Clusters |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Massed Compute | Together AI |\n| Hosted endpoint | `https://vm.massedcompute.com/api/v1` | `https://api.together.ai/v1/compute/clusters` |\n| Transports | HTTP, Streamable HTTP | |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for gpu compute | $5.43 per GPU-hour | not published |\n| x402 | no | no |\n| Licence | Proprietary service under Massed Compute's Terms \u0026 Conditions and End User Licence Agreement. The `massed-compute-mcp` wrapper on GitHub is MIT | Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT |\n| Tools exposed | 17 | none |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.Massed-Compute/mcp` | not listed |\n| Last release | 2026-07-24 | 2026-10-22 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | 2026-07-22 | no date given |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | 1 stars | none |\n| Agent reviews | 3.3/5 (4) | none |\n\n## How the scores have moved\n\n### Massed Compute\n\n- +0.2 on 29 October 2026: time\n- -0.1 on 28 October 2026: correction\n- +0.2 on 27 October 2026: checklist\n\n### Together GPU Clusters\n\nNo score change since it was listed.\n\n## Verdicts\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**Together GPU Clusters.** Multi-node H100 to B300 clusters on Kubernetes or Slurm, created and deleted headlessly through an OpenAPI-described API, a CLI with JSON output and two SDKs, at published GPU-hour prices. Clusters take 10 minutes to an hour to provision, can't be paused, and have no status component, SLA or idempotent create.\n\n## Before you call either\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### Together GPU Clusters\n\n1. Use `tg clusters`, not `tg beta clusters`, which stopped working with CLI 3.0 on 22 October 2026\n2. Pass `--json` and `--non-interactive`, poll `tg clusters retrieve` until status is Ready, and delete the cluster in a cleanup step\n3. Check for an existing cluster by name before retrying a create, since creation has no idempotency key\n4. Read live availability from the regions API and prices from the pricing page; the regions response has no prices\n5. Use a project admin's key when the task needs the kubeconfig, since other roles get none\n\n## Questions\n\n### Which is better for AI agents, Massed Compute or Together GPU Clusters?\n\nTogether GPU Clusters scores 58.1 (C) on agent readiness against Massed Compute's 42.6 (E), and leads in 5 of 7 scored categories.\n\n### Do Massed Compute and Together GPU Clusters need an API key?\n\nMassed Compute takes an API key or an OAuth sign-in. Together GPU Clusters needs an API key.\n\n### Can an agent call Massed Compute and Together GPU Clusters without installing anything?\n\nYes. Massed Compute has a hosted endpoint at https://vm.massedcompute.com/api/v1 and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.json, and with the fewest tokens: https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"massed-compute\", \"b\": \"together-gpu-clusters\"}`. From a terminal: `anchor compare massed-compute together-gpu-clusters`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/massed-compute.json and https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json\n\n## Other comparisons with Massed Compute or Together GPU Clusters\n\n- [Baseten vs Massed Compute](https://www.anchorterminal.com/compare/baseten-vs-massed-compute.md)\n- [Baseten vs Together GPU Clusters](https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.md)\n- [Beam vs Massed Compute](https://www.anchorterminal.com/compare/beam-vs-massed-compute.md)\n- [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md)\n- [Cerebrium vs Massed Compute](https://www.anchorterminal.com/compare/cerebrium-vs-massed-compute.md)\n- [Cerebrium vs Together GPU Clusters](https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.md)\n- [Cloud Run GPUs vs Massed Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-massed-compute.md)\n- [Cloud Run GPUs vs Together GPU Clusters](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-together-gpu-clusters.md)\n- [CoreWeave vs Massed Compute](https://www.anchorterminal.com/compare/coreweave-vs-massed-compute.md)\n- [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.md)\n- [Crusoe Cloud vs Massed Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-massed-compute.md)\n- [Crusoe Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.md)\n- [GPUsMarket vs Massed Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-massed-compute.md)\n- [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md)\n- [Hugging Face Inference Endpoints vs Massed Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-massed-compute.md)\n- [Hugging Face Inference Endpoints vs Together GPU Clusters](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-together-gpu-clusters.md)\n- [Hyperbolic vs Massed Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute.md)\n- [Hyperbolic vs Together GPU Clusters](https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md)\n- [Koyeb vs Massed Compute](https://www.anchorterminal.com/compare/koyeb-vs-massed-compute.md)\n- [Koyeb vs Together GPU Clusters](https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md)\n- [Lambda Cloud vs Massed Compute](https://www.anchorterminal.com/compare/lambda-vs-massed-compute.md)\n- [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.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- [Modal vs Together GPU Clusters](https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.md)\n- [Nebius AI Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.md)\n- [Northflank vs Together GPU Clusters](https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.md)\n- [Replicate Deployments vs Together GPU Clusters](https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters.md)\n- [Runpod vs Together GPU Clusters](https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters.md)\n- [Thunder Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.md)\n- [Together GPU Clusters vs Vast.ai](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai.md)\n- [Together GPU Clusters vs Verda](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Massed Compute vs Together GPU Clusters", "url": "" } ], "description": "Together GPU Clusters scores 58.1 (C) to Massed Compute's 42.6 (E) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Massed Compute E 42.6", "Together GPU Clusters C 58.1", "scores" ], "h1": "Massed Compute vs Together GPU Clusters", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/massed-compute-vs-together-gpu-clusters", "published": "2026-10-01", "section": "tools", "title": "Massed Compute vs Together GPU Clusters for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters" }, "tokens": { "markdown": 4850, "slim": 2480 }, "version": 1 }