{ "data": { "a": { "slug": "thunder-compute", "name": "Thunder Compute", "vendor": "Thunder Compute", "vendorUrl": "https://www.thundercompute.com", "kind": "http-api", "category": "gpu-compute", "summary": "Thunder Compute is a US GPU cloud renting RTX A6000, L40, A100 and H100 instances by the minute and GPU sandboxes by the second. Agents use its REST API, a hosted MCP server with OAuth, or the `tnr` CLI.", "url": "https://www.anchorterminal.com/tools/thunder-compute", "markdownUrl": "https://www.anchorterminal.com/tools/thunder-compute.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/thunder-compute.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/thunder-compute.json", "dns": "thunder-compute.grade.anchorterminal.com", "repo": "https://github.com/Thunder-Compute/thunder-cli", "license": "Proprietary service under Thunder Compute's Terms and Conditions. The `tnr` CLI on GitHub is MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.thundercompute.com:8443/v1", "packages": [ { "registry": "go", "name": "github.com/Thunder-Compute/thunder-cli" }, { "registry": "pypi", "name": "thunder-sandbox" } ], "auth": "mixed", "authNotes": "Self-serve. The hosted MCP server uses OAuth 2.0 with discovery. The first connection opens a browser to sign in and approve, tokens refresh, and the scopes are `instances:read`, `instances:write`, `snapshots:read`, `snapshots:write`, `sandboxes:read`, `sandboxes:write`, `billing:read` and `org:read`. The REST API takes a named API token as a Bearer header. Tokens are created and revoked one at a time in the console, or with the MCP `create_token` tool, and no token scopes were found. The CLI and the sandbox SDK read `TNR_API_TOKEN` for headless use. Price, specification, availability and template endpoints need no token.", "pricing": "usage", "pricingNotes": "No general free tier. Instances are billed by the minute while they run, paid by saved card or preloaded credit that is non-refundable. Per GPU an hour on 9 October 2026, RTX A6000 is $0.35, L40 $0.79, A100 80 GB $1.09 and H100 $3.20. Sandboxes are billed by the second and need access enabled by the vendor. Students with a US university email get $20 of credit for A6000 and L40 GPUs. Reserved capacity is by quote (https://www.thundercompute.com/pricing).", "priceSummary": "$0.04 / vCPU-hr", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs corpus, the OpenAPI document or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": 28, "popularity": { "githubStars": 34, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.thundercompute.com/docs", "llmsTxt": "https://www.thundercompute.com/docs/llms.txt", "openapi": "https://api.thundercompute.com:8443/openapi.json", "registryName": "io.github.Thunder-Compute/thunder-compute", "capabilities": [ "compute.gpu", "compute.containers" ], "tags": [ "hosted", "usage-priced", "openapi", "llms-txt", "mcp", "cli", "oauth", "api-key", "python", "go", "status-page", "card-required", "closed-source" ], "lastRelease": "2026-10-27", "graded": true, "anchor": { "graded": true, "score": 51.3, "grade": "D", "agentReady": false, "rank": 1032, "ranked": true, "rankOf": 1510, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 48, "maintenance": 79, "payments": 20, "reliability": 65, "schema": 70, "security": 51, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -5, "negativeNotes": [ "-3, released fixes of described flaws with no advisory. The CLI's v2.1.0 (16 September 2026) changelog has a Security section that stops \"copying the local CLI authentication credential onto instances during connect\" and stops configuration and API URL overrides \"sending browser login credentials to a different API origin\". v2.0.71 (30 July) made the updater require verified checksums. OSV holds no record for thunder-cli (https://github.com/Thunder-Compute/thunder-cli/blob/main/CHANGELOG.md).", "-2, undisclosed default telemetry. Released CLI builds inject a Sentry DSN at build time, so error reports go to Sentry by default with a user ID derived from a hash of the API token, the machine's HOSTNAME as `instance_id`, OS, architecture and Go version, and tracing is enabled at a 10 per cent sample with request breadcrumbs. No opt-out was found in the CLI, its README or, per the 9 October check, the docs. The v2.2.0 changelog mentions \"released CLI error reports\" without describing them, and Sentry isn't on the sub-processor list (https://github.com/Thunder-Compute/thunder-cli/blob/main/main.go)." ], "verdict": "The hosted MCP server signs in with OAuth and separate read and write scopes, and the REST API has a public OpenAPI 3.1 document. No rate limits, SLA or API changelog were found, instance creation has no idempotency key, and the CLI sends error reports to Sentry by default with no documented opt-out.", "bestFor": "Agents in coding tools that rent a single persistent GPU machine for development, fine-tuning or a model server, at low hourly prices and over MCP.", "strengths": [ "Hosted MCP server at `https://www.thundercompute.com/mcp` with OAuth and ten scopes that separate read from write for instances, snapshots and sandboxes", "Public OpenAPI 3.1 document with 41 operations, plus `llms.txt`, `llms-full.txt` and a Markdown copy of every docs page", "Per-GPU-hour, per-vCPU-hour and storage prices are public on the pricing page", "Section 28 of the terms, dated 28 September 2026, permits access by AI agents, scripts and SDKs through the account holder's own credentials", "The `tnr` CLI had three code releases between 15 September and 27 October 2026, with a dated changelog" ], "weaknesses": [ "No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability", "`POST /instances/create` has no idempotency key, so a retried launch can start a second billed instance", "Instances cannot be stopped. Pausing means taking a snapshot, deleting the instance and restoring later", "No security.txt or disclosure policy was found, and the SOC 2 Type II claim in `llms.txt` has no report or trust page linked", "The CLI sends error reports to Sentry by default with a hashed token ID, and no opt-out was found", "Credential-handling fixes in CLI v2.1.0 (16 September 2026) shipped with no advisory" ], "agentNotes": [ "Call `GET /v2/status` or the `get_availability` tool before creating an instance. Availability can change before launch, and creation fails when a type is sold out.", "List instances before retrying a failed create, because the call has no idempotency key.", "Pass `public_key` on create. If omitted, the response carries a generated private key that is returned once.", "To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.", "For headless use set `TNR_API_TOKEN` to a token from the console, and upgrade the CLI to v2.1.0 or later, which stops copying that credential onto instances." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 51.3 } ], "editorialScores": { "ergonomics": 48, "maintenance": 79, "payments": 20, "reliability": 65, "schema": 70, "security": 51, "transparency": 51 }, "provenanceScore": 80, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "curl -fsSL https://raw.githubusercontent.com/Thunder-Compute/thunder-cli/main/scripts/install.sh | bash", "http": "curl https://api.thundercompute.com:8443/v2/pricing", "claudeCode": "claude mcp add --transport http thunder-compute https://www.thundercompute.com/mcp", "config": { "mcpServers": { "thunder-compute": { "url": "https://www.thundercompute.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/thunder-compute" }, "area": "models", "unitPrices": [ { "item": "RTX A6000 48 GB instance", "unit": "gpu-hour", "usd": 0.35, "note": "Billed per minute. One GPU per instance" }, { "item": "L40 48 GB instance", "unit": "gpu-hour", "usd": 0.79, "note": "Billed per minute" }, { "item": "A100 80 GB instance", "unit": "gpu-hour", "usd": 1.09, "note": "Billed per minute. 4 and 8 GPU shapes cost $1.49 a GPU per the price endpoint" }, { "item": "H100 80 GB instance", "unit": "gpu-hour", "usd": 3.2, "note": "Billed per minute" }, { "item": "H100 80 GB sandbox", "unit": "gpu-hour", "usd": 2.95, "note": "Billed per second, plus vCPU and memory. Access on request" }, { "item": "A100 80 GB sandbox", "unit": "gpu-hour", "usd": 1.95, "note": "Billed per second, plus vCPU and memory. Access on request" }, { "item": "Extra instance vCPU", "unit": "vcpu-hour", "usd": 0.04, "note": "Above the vCPUs included with each GPU" }, { "item": "Sandbox vCPU", "unit": "vcpu-hour", "usd": 0.051, "note": "Memory is $0.016 per GiB an hour" }, { "item": "Instance disk above 100 GB per GPU", "unit": "gb-month", "usd": 0.219, "note": "Billed only while the instance runs" }, { "item": "Snapshot storage", "unit": "gb-month", "usd": 0.05, "note": "Kept until deleted" } ], "provenance": { "legalEntity": "Thunder GPU, Inc.", "domain": "thundercompute.com", "domainRegistered": "2024-02-29", "endpointOnVendorDomain": true, "terms": "https://www.thundercompute.com/terms-and-conditions", "privacy": "https://www.thundercompute.com/privacy-policy", "statusPage": "https://status.thundercompute.com", "changelog": "https://github.com/Thunder-Compute/thunder-cli/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms and Conditions, last updated 28 September 2026, name Thunder GPU, Inc., doing business as Thunder Compute, a Delaware company, and apply Delaware law. They cover the site and the services, with sections on automated access, usage billing and instance data deletion.", "The privacy policy, last updated 28 September 2026, covers the website and the GPU platform, including access by AI agents.", "The API answers at api.thundercompute.com on port 8443, and the MCP server at www.thundercompute.com/mcp, both on the vendor domain.", "/.well-known/security.txt answers 404.", "RDAP for thundercompute.com gives a registration date of 2024-02-29.", "The changelog linked is the CLI's. No API changelog was found.", "A Data Processing Addendum is published in the docs and a sub-processor list on the site, last updated 27 August 2025." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/thunder-compute.json", "live": { "slug": "thunder-compute", "probe": { "target": "https://api.thundercompute.com:8443/v1", "method": "get", "lastAt": "2026-11-07T19:22:39.718670643Z", "lastOk": true, "lastStatus": 404, "lastMs": 238, "authRequired": false, "uptime24h": 100, "uptime30d": 99.89, "p50ms24h": 610, "p95ms24h": 715, "samples24h": 238, "samples30d": 7299, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "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": 252 }, { "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": 244 }, { "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": 247 }, { "date": "2026-10-28", "probes": 250, "ok": 249 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "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 } ] }, "vendorStatus": { "page": "https://status.thundercompute.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:23:50.038587335Z" }, "versions": [ { "registry": "github", "name": "Thunder-Compute/thunder-cli", "version": "v2.3.0", "released": "2026-11-05", "seenAt": "2026-11-07T00:11:24.374859251Z" }, { "registry": "mcp-registry", "name": "io.github.Thunder-Compute/thunder-compute", "version": "1.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "pypi", "name": "thunder-sandbox", "version": "0.7.11", "released": "2026-11-04", "seenAt": "2026-11-07T00:11:24.191658707Z" } ], "githubStars": 34, "pypiWeekly": 7292, "securityTxt": { "url": "https://thundercompute.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:02:02.689166619Z" }, "llmsTxt": { "url": "https://www.thundercompute.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:08.029305428Z" }, "domain": { "domain": "thundercompute.com", "registered": "2024-02-29", "source": "https://rdap.verisign.com/com/v1/domain/thundercompute.com", "checkedAt": "2026-11-01T14:19:55.118917218Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/Thunder-Compute/thunder-cli/main/CHANGELOG.md", "kind": "changelog", "status": 304, "checkedAt": "2026-11-07T14:19:37.649850655Z", "changedAt": "2026-11-05T13:04:01.9071579Z", "fingerprint": "e59bfd9db845" }, { "url": "https://www.thundercompute.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:35:36.789186909Z", "changedAt": "2026-11-07T14:35:36.789186909Z", "fingerprint": "adbd67a657df" }, { "url": "https://www.thundercompute.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:35:39.012108629Z", "changedAt": "2026-10-23T02:07:42.099244407Z", "fingerprint": "15f556e42b20" }, { "url": "https://www.thundercompute.com/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:35:41.000439019Z", "changedAt": "2026-10-23T02:07:44.212693674Z", "fingerprint": "bcc6d526ecf3" } ], "mcpTools": { "url": "https://www.thundercompute.com/mcp", "checkedAt": "2026-11-07T01:48:36.126087407Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:48:36.126087407Z" }, "github": { "repo": "thunder-compute/thunder-cli", "checkedAt": "2026-11-02T09:31:35.915022229Z", "stars": 34, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-27T23:09:19Z", "openIssues": 0, "openPRs": 2, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "replies": { "sampled": 12, "unanswered": 0, "medianDays": 2.3 } }, "updatedAt": "2026-11-07T19:23:50.038587335Z" } }, "answer": "Together GPU Clusters scores 58.1 (C) on agent readiness against Thunder Compute's 51.3 (D), and leads in 3 of 7 scored categories. Thunder Compute leads on reliability.", "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": 27, "category": "reliability", "leads": "thunder-compute", "name": "Reliability", "reasons": { "a": "Graded on the hosted lines for the REST API and the hosted MCP server. Thunder Compute's terms bar robots, scrapers and data-gathering tools on the Services, so its site, status page and API host weren't requested on 4 November and the readings below are per the 9 October check, not re-read on 4 November. Status page on incident.io at status.thundercompute.com with Website, API and Instances components and monthly history (20). No incidents listed for July to 9 October 2026. The rest of the window is unread and not credited, so the line keeps its recorded award (30). No rate limits with numbers were found in the docs or the OpenAPI document (0). No 429 or retry guidance in the docs. The CLI source reads a `Retry-After` header on errors, adding a duplicate SSH key is a no-op and port updates are atomic, but instance creation has no idempotency key (5 of 15, a partial value kept and flagged). No SLA found, and the terms say availability is not guaranteed (0). The API and MCP server carry no beta label (10). 20+30+0+5+0+10 = 65.", "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": 65, "b": 38 } }, { "by": 22, "category": "schema", "leads": "together-gpu-clusters", "name": "Schema \u0026 documentation", "reasons": { "a": "Public OpenAPI 3.1 document at api.thundercompute.com:8443/openapi.json with 41 operations and 72 schemas (25). `llms.txt`, `llms-full.txt` and a Markdown copy of every docs page (10). 28 of 41 operations have a description. Instance operations state side effects such as the private key being returned once, while most sandbox operations have a summary only (12 of 20). Required fields are marked, but the document has six enums, `gpu_type` and `template` are free strings and the instance list is a map keyed by ID (8 of 15). 12 examples and one error schema with `code`, `error` and `message`. Most operations document 400, 401 and 500, and none documents 429 (9 of 15). `/v1` and `/v2` paths, with legacy endpoints and the `mode` field marked as retained or deprecated. No API changelog was found. The CLI has a dated one (6 of 15). No published copy of the MCP tool definitions was found, so they were not read. All of this is per the 9 October check, not re-read on 4 November. 25+10+12+8+9+6 = 70.", "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": 70, "b": 92 } }, { "by": 17, "category": "security", "leads": "together-gpu-clusters", "name": "Security \u0026 auth", "reasons": { "a": "The MCP server uses OAuth 2.0 with discovery, refresh tokens and ten scopes that separate read from write for instances, snapshots and sandboxes. The REST API uses named API tokens that are created and revoked one at a time, with no scopes found. No secret travels in a URL (25 of 30). Read scopes exist, and the CLI requires `--yes` to delete without a prompt. No confirmation step for `delete_instance` or `delete_snapshot` was found in the MCP docs, and both are described as irreversible (8 of 20). Responses are infrastructure metadata, except `run_command` output and sandbox logs, with no guidance found on untrusted output (8 of 15). `GET /tokens` returns creation and last-used times and sandbox logs are listed by API. No audit log was found (4 of 15). No security.txt, disclosure policy or bug bounty was found. `llms.txt` states SOC 2 Type II and GDPR compliance with no report or trust page linked, and the DPA promises an audit summary on written request and incident notice within 72 hours (6 of 20). The site readings are per the 9 October check, not re-read on 4 November. 25+8+8+4+6 = 51.", "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": 51, "b": 68 } }, { "by": 7, "category": "ergonomics", "leads": "together-gpu-clusters", "name": "Agent ergonomics", "reasons": { "a": "No field selection, and `GET /instances/list` returns every instance in one map. The MCP server has 28 tools in one set, with no toolsets found (12 of 25). `limit` up to 100, `page_token` and a status filter on sandboxes and sandbox logs. No pagination on instances, snapshots or keys (8 of 20). Errors carry a numeric `code`, a string `error` such as `invalid_request` and a `message`, documented per operation (14 of 20). Duplicate SSH keys are a no-op and port changes are deduplicated in one transaction, but create calls have no idempotency key. MCP tool annotations were not read (7 of 20). A create call needs five fields. The official Python SDK covers sandboxes only, and the Go CLI covers instances (7 of 15). All of this is per the 9 October check, not re-read on 4 November. 12+8+14+7+7 = 48.", "b": "Cluster objects are compact, and `--json` gives machine-readable output, but list calls take no field selection (15). No pagination or filters on the clusters list (8). 402 and 403 with readable messages such as \"Insufficient credits for cluster creation\", and troubleshooting for common failures (12). Status polling until Ready is documented and deletes run non-interactively, but there is no idempotency key on creation and a duplicate create bills a second cluster (8). Official Python and TypeScript SDKs and a CLI, though a create takes GPU type, region, driver and CUDA versions, cluster type and billing type (12). 15+8+12+8+12 = 55." }, "scores": { "a": 48, "b": 55 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Thunder Compute", "b": "Together AI", "name": "Vendor" }, { "a": "https://api.thundercompute.com:8443/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": "$0.219 per GB per month", "b": "not published", "name": "Price for gpu compute" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Thunder Compute's Terms and Conditions. The `tnr` CLI 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": "28", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.Thunder-Compute/thunder-compute", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-27", "b": "2026-10-22", "name": "Last release" }, { "a": "2026-09-28", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-09-28", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "34 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Together GPU Clusters scores 58.1 (C) on agent readiness against Thunder Compute's 51.3 (D), and leads in 3 of 7 scored categories. Thunder Compute leads on reliability.", "question": "Which is better for AI agents, Thunder Compute or Together GPU Clusters?" }, { "answer": "Thunder Compute takes an API key or an OAuth sign-in. Together GPU Clusters needs an API key.", "question": "Do Thunder Compute and Together GPU Clusters need an API key?" }, { "answer": "Yes. Thunder Compute has a hosted endpoint at https://api.thundercompute.com:8443/v1 and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.", "question": "Can an agent call Thunder Compute and Together GPU Clusters without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 65 against 38" ], "also": null, "goodFor": "Agents in coding tools that rent a single persistent GPU machine for development, fine-tuning or a model server, at low hourly prices and over MCP.", "slug": "thunder-compute", "watchFor": "No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability" }, { "aheadOn": [ "Schema \u0026 documentation, 92 against 70", "Agent ergonomics, 55 against 48", "Security \u0026 auth, 68 against 51" ], "also": [ "No incidents deducted, where Thunder 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": { "thunder-compute": [ { "causes": [ "event" ], "date": "2026-11-04", "delta": -5, "from": 56.3, "fromGrade": "C", "to": 51.3, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 56.1, "fromGrade": "C", "to": 56.3, "toGrade": "C" } ], "together-gpu-clusters": null }, "job": { "capability": "compute.gpu", "name": "GPU compute" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-thunder-compute.json", "title": "Baseten vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/baseten-vs-thunder-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-thunder-compute.json", "title": "Beam vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/beam-vs-thunder-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-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-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-thunder-compute.json", "title": "Cloud Run GPUs vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-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-thunder-compute.json", "title": "CoreWeave vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/coreweave-vs-thunder-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-thunder-compute.json", "title": "Crusoe Cloud vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-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-thunder-compute.json", "title": "GPUsMarket vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-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-thunder-compute.json", "title": "Hugging Face Inference Endpoints vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-thunder-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-thunder-compute.json", "title": "Hyperbolic vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-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-thunder-compute.json", "title": "Koyeb vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/koyeb-vs-thunder-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-thunder-compute.json", "title": "Lambda Cloud vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/lambda-vs-thunder-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-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-together-gpu-clusters.json", "title": "Massed Compute vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/modal-vs-thunder-compute.json", "title": "Modal vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/modal-vs-thunder-compute" }, { "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-thunder-compute.json", "title": "Nebius AI Cloud vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-thunder-compute" }, { "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-thunder-compute.json", "title": "Northflank vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/northflank-vs-thunder-compute" }, { "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-thunder-compute.json", "title": "Replicate Deployments vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute" }, { "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-thunder-compute.json", "title": "Runpod vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/runpod-vs-thunder-compute" }, { "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-vast-ai.json", "title": "Thunder Compute vs Vast.ai", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda.json", "title": "Thunder Compute vs Verda", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-verda" }, { "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": 27, "edge": "thunder-compute", "key": "reliability", "name": "Reliability", "thunder-compute": 65, "together-gpu-clusters": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 22, "edge": "together-gpu-clusters", "key": "schema", "name": "Schema \u0026 documentation", "thunder-compute": 70, "together-gpu-clusters": 92, "weight": 13 }, { "by": 7, "edge": "together-gpu-clusters", "key": "ergonomics", "name": "Agent ergonomics", "thunder-compute": 48, "together-gpu-clusters": 55, "weight": 13 }, { "by": 17, "edge": "together-gpu-clusters", "key": "security", "name": "Security \u0026 auth", "thunder-compute": 51, "together-gpu-clusters": 68, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "thunder-compute": 20, "together-gpu-clusters": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "edge": "thunder-compute", "key": "maintenance", "name": "Maintenance \u0026 community", "thunder-compute": 79, "together-gpu-clusters": 75, "weight": 7 }, { "by": 1, "edge": "thunder-compute", "key": "transparency", "name": "Transparency \u0026 trust", "thunder-compute": 66, "together-gpu-clusters": 65, "weight": 7 } ], "summary": "Together GPU Clusters scores 58.1 (C) on agent readiness against Thunder Compute's 51.3 (D), and leads in 3 of 7 scored categories. Thunder Compute leads on reliability. Both do gpu compute.", "tasks": null, "tutorials": [], "verdicts": { "thunder-compute": "The hosted MCP server signs in with OAuth and separate read and write scopes, and the REST API has a public OpenAPI 3.1 document. No rate limits, SLA or API changelog were found, instance creation has no idempotency key, and the CLI sends error reports to Sentry by default with no documented opt-out.", "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/thunder-compute-vs-together-gpu-clusters", "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.min.md" }, "markdown": "Together GPU Clusters scores 58.1 (C) on agent readiness against Thunder Compute's 51.3 (D), and leads in 3 of 7 scored categories. Thunder Compute leads on reliability. Both do gpu compute.\n\n- Thunder Compute: grade D, 51.3/100, rank #1032 of 1510. Markdown https://www.anchorterminal.com/tools/thunder-compute.md · JSON https://www.anchorterminal.com/api/v1/tools/thunder-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### Thunder Compute (D)\n\nGood for: Agents in coding tools that rent a single persistent GPU machine for development, fine-tuning or a model server, at low hourly prices and over MCP.\n\nAhead on:\n- Reliability, 65 against 38\n\nWatch for: No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability\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- Schema \u0026 documentation, 92 against 70\n- Agent ergonomics, 55 against 48\n- Security \u0026 auth, 68 against 51\n\nAlso in its favour:\n- No incidents deducted, where Thunder 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### Reliability: Thunder Compute +27\n\n- Thunder Compute (65): Graded on the hosted lines for the REST API and the hosted MCP server. Thunder Compute's terms bar robots, scrapers and data-gathering tools on the Services, so its site, status page and API host weren't requested on 4 November and the readings below are per the 9 October check, not re-read on 4 November. Status page on incident.io at status.thundercompute.com with Website, API and Instances components and monthly history (20). No incidents listed for July to 9 October 2026. The rest of the window is unread and not credited, so the line keeps its recorded award (30). No rate limits with numbers were found in the docs or the OpenAPI document (0). No 429 or retry guidance in the docs. The CLI source reads a `Retry-After` header on errors, adding a duplicate SSH key is a no-op and port updates are atomic, but instance creation has no idempotency key (5 of 15, a partial value kept and flagged). No SLA found, and the terms say availability is not guaranteed (0). The API and MCP server carry no beta label (10). 20+30+0+5+0+10 = 65.\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### Schema \u0026 documentation: Together GPU Clusters +22\n\n- Thunder Compute (70): Public OpenAPI 3.1 document at api.thundercompute.com:8443/openapi.json with 41 operations and 72 schemas (25). `llms.txt`, `llms-full.txt` and a Markdown copy of every docs page (10). 28 of 41 operations have a description. Instance operations state side effects such as the private key being returned once, while most sandbox operations have a summary only (12 of 20). Required fields are marked, but the document has six enums, `gpu_type` and `template` are free strings and the instance list is a map keyed by ID (8 of 15). 12 examples and one error schema with `code`, `error` and `message`. Most operations document 400, 401 and 500, and none documents 429 (9 of 15). `/v1` and `/v2` paths, with legacy endpoints and the `mode` field marked as retained or deprecated. No API changelog was found. The CLI has a dated one (6 of 15). No published copy of the MCP tool definitions was found, so they were not read. All of this is per the 9 October check, not re-read on 4 November. 25+10+12+8+9+6 = 70.\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### Security \u0026 auth: Together GPU Clusters +17\n\n- Thunder Compute (51): The MCP server uses OAuth 2.0 with discovery, refresh tokens and ten scopes that separate read from write for instances, snapshots and sandboxes. The REST API uses named API tokens that are created and revoked one at a time, with no scopes found. No secret travels in a URL (25 of 30). Read scopes exist, and the CLI requires `--yes` to delete without a prompt. No confirmation step for `delete_instance` or `delete_snapshot` was found in the MCP docs, and both are described as irreversible (8 of 20). Responses are infrastructure metadata, except `run_command` output and sandbox logs, with no guidance found on untrusted output (8 of 15). `GET /tokens` returns creation and last-used times and sandbox logs are listed by API. No audit log was found (4 of 15). No security.txt, disclosure policy or bug bounty was found. `llms.txt` states SOC 2 Type II and GDPR compliance with no report or trust page linked, and the DPA promises an audit summary on written request and incident notice within 72 hours (6 of 20). The site readings are per the 9 October check, not re-read on 4 November. 25+8+8+4+6 = 51.\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### Agent ergonomics: Together GPU Clusters +7\n\n- Thunder Compute (48): No field selection, and `GET /instances/list` returns every instance in one map. The MCP server has 28 tools in one set, with no toolsets found (12 of 25). `limit` up to 100, `page_token` and a status filter on sandboxes and sandbox logs. No pagination on instances, snapshots or keys (8 of 20). Errors carry a numeric `code`, a string `error` such as `invalid_request` and a `message`, documented per operation (14 of 20). Duplicate SSH keys are a no-op and port changes are deduplicated in one transaction, but create calls have no idempotency key. MCP tool annotations were not read (7 of 20). A create call needs five fields. The official Python SDK covers sandboxes only, and the Go CLI covers instances (7 of 15). All of this is per the 9 October check, not re-read on 4 November. 12+8+14+7+7 = 48.\n- Together GPU Clusters (55): Cluster objects are compact, and `--json` gives machine-readable output, but list calls take no field selection (15). No pagination or filters on the clusters list (8). 402 and 403 with readable messages such as \"Insufficient credits for cluster creation\", and troubleshooting for common failures (12). Status polling until Ready is documented and deletes run non-interactively, but there is no idempotency key on creation and a duplicate create bills a second cluster (8). Official Python and TypeScript SDKs and a CLI, though a create takes GPU type, region, driver and CUDA versions, cluster type and billing type (12). 15+8+12+8+12 = 55.\n\n## Score by category\n\n| Category | Weight | Thunder Compute | Together GPU Clusters | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 38 | Thunder Compute +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 92 | Together GPU Clusters +22 |\n| Agent ergonomics | 13% (16.2 this run) | 48 | 55 | Together GPU Clusters +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 68 | Together GPU Clusters +17 |\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) | 79 | 75 | Thunder Compute +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 65 | Thunder Compute +1 |\n| Negative events | ≤15 | -5 | 0 | |\n| **Total** | | **51.3 · D** | **58.1 · C** | |\n\n## Facts side by side\n\n| Fact | Thunder Compute | Together GPU Clusters |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Thunder Compute | Together AI |\n| Hosted endpoint | `https://api.thundercompute.com:8443/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 | $0.219 per GB per month | not published |\n| x402 | no | no |\n| Licence | Proprietary service under Thunder Compute's Terms and Conditions. The `tnr` CLI 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 | 28 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.Thunder-Compute/thunder-compute` | not listed |\n| Last release | 2026-10-27 | 2026-10-22 |\n| Terms last updated | 2026-09-28 | no date given |\n| Privacy policy last updated | 2026-09-28 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 34 stars | none |\n\n## How the scores have moved\n\n### Thunder Compute\n\n- -5.0 on 4 November 2026 (C to D): negative event\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**Thunder Compute.** The hosted MCP server signs in with OAuth and separate read and write scopes, and the REST API has a public OpenAPI 3.1 document. No rate limits, SLA or API changelog were found, instance creation has no idempotency key, and the CLI sends error reports to Sentry by default with no documented opt-out.\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### Thunder Compute\n\n1. Call `GET /v2/status` or the `get_availability` tool before creating an instance. Availability can change before launch, and creation fails when a type is sold out.\n2. List instances before retrying a failed create, because the call has no idempotency key.\n3. Pass `public_key` on create. If omitted, the response carries a generated private key that is returned once.\n4. To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.\n5. For headless use set `TNR_API_TOKEN` to a token from the console, and upgrade the CLI to v2.1.0 or later, which stops copying that credential onto instances.\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, Thunder Compute or Together GPU Clusters?\n\nTogether GPU Clusters scores 58.1 (C) on agent readiness against Thunder Compute's 51.3 (D), and leads in 3 of 7 scored categories. Thunder Compute leads on reliability.\n\n### Do Thunder Compute and Together GPU Clusters need an API key?\n\nThunder Compute takes an API key or an OAuth sign-in. Together GPU Clusters needs an API key.\n\n### Can an agent call Thunder Compute and Together GPU Clusters without installing anything?\n\nYes. Thunder Compute has a hosted endpoint at https://api.thundercompute.com:8443/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/thunder-compute-vs-together-gpu-clusters.json, and with the fewest tokens: https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"thunder-compute\", \"b\": \"together-gpu-clusters\"}`. From a terminal: `anchor compare thunder-compute together-gpu-clusters`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/thunder-compute.json and https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json\n\n## Other comparisons with Thunder Compute or Together GPU Clusters\n\n- [Baseten vs Thunder Compute](https://www.anchorterminal.com/compare/baseten-vs-thunder-compute.md)\n- [Baseten vs Together GPU Clusters](https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.md)\n- [Beam vs Thunder Compute](https://www.anchorterminal.com/compare/beam-vs-thunder-compute.md)\n- [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md)\n- [Cerebrium vs Thunder Compute](https://www.anchorterminal.com/compare/cerebrium-vs-thunder-compute.md)\n- [Cerebrium vs Together GPU Clusters](https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.md)\n- [Cloud Run GPUs vs Thunder Compute](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-thunder-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 Thunder Compute](https://www.anchorterminal.com/compare/coreweave-vs-thunder-compute.md)\n- [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.md)\n- [Crusoe Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/crusoe-cloud-vs-thunder-compute.md)\n- [Crusoe Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.md)\n- [GPUsMarket vs Thunder Compute](https://www.anchorterminal.com/compare/gpusmarket-vs-thunder-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 Thunder Compute](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-thunder-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 Thunder Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute.md)\n- [Hyperbolic vs Together GPU Clusters](https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md)\n- [Koyeb vs Thunder Compute](https://www.anchorterminal.com/compare/koyeb-vs-thunder-compute.md)\n- [Koyeb vs Together GPU Clusters](https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md)\n- [Lambda Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/lambda-vs-thunder-compute.md)\n- [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md)\n- [Massed Compute vs Thunder Compute](https://www.anchorterminal.com/compare/massed-compute-vs-thunder-compute.md)\n- [Massed Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md)\n- [Modal vs Thunder Compute](https://www.anchorterminal.com/compare/modal-vs-thunder-compute.md)\n- [Modal vs Together GPU Clusters](https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.md)\n- [Nebius AI Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-thunder-compute.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 Thunder Compute](https://www.anchorterminal.com/compare/northflank-vs-thunder-compute.md)\n- [Northflank vs Together GPU Clusters](https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.md)\n- [Replicate Deployments vs Thunder Compute](https://www.anchorterminal.com/compare/replicate-deploy-vs-thunder-compute.md)\n- [Replicate Deployments vs Together GPU Clusters](https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters.md)\n- [Runpod vs Thunder Compute](https://www.anchorterminal.com/compare/runpod-vs-thunder-compute.md)\n- [Runpod vs Together GPU Clusters](https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters.md)\n- [Thunder Compute vs Vast.ai](https://www.anchorterminal.com/compare/thunder-compute-vs-vast-ai.md)\n- [Thunder Compute vs Verda](https://www.anchorterminal.com/compare/thunder-compute-vs-verda.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": "Thunder Compute vs Together GPU Clusters", "url": "" } ], "description": "Together GPU Clusters scores 58.1 (C) to Thunder Compute's 51.3 (D) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Thunder Compute D 51.3", "Together GPU Clusters C 58.1", "scores" ], "h1": "Thunder Compute vs Together GPU Clusters", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/thunder-compute-vs-together-gpu-clusters", "published": "2026-10-01", "section": "tools", "title": "Thunder Compute vs Together GPU Clusters for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters" }, "tokens": { "markdown": 4950, "slim": 2530 }, "version": 1 }