{ "data": { "a": { "slug": "nebius-ai-cloud", "name": "Nebius AI Cloud", "vendor": "Nebius", "vendorUrl": "https://nebius.com", "kind": "http-api", "category": "gpu-compute", "summary": "Nebius AI Cloud rents NVIDIA GPU virtual machines and InfiniBand clusters, with managed Kubernetes, Slurm and Serverless AI jobs and endpoints for containers. Resources are managed through REST and gRPC APIs, a CLI, a Terraform provider and SDKs.", "url": "https://www.anchorterminal.com/tools/nebius-ai-cloud", "markdownUrl": "https://www.anchorterminal.com/tools/nebius-ai-cloud.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nebius-ai-cloud.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nebius-ai-cloud.json", "dns": "nebius-ai-cloud.grade.anchorterminal.com", "repo": "https://github.com/nebius/api", "license": "Proprietary service under the Nebius Services Agreement. The API definitions, the Go, Python and JavaScript SDKs and the MCP server on GitHub are MIT", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.nebius.cloud", "packages": [ { "registry": "pypi", "name": "nebius" }, { "registry": "npm", "name": "@nebius/js-sdk" }, { "registry": "go", "name": "github.com/nebius/gosdk" } ], "auth": "mixed", "authNotes": "Self-serve. A person signs up in the web console with a Google, GitHub or Microsoft account. Every API call takes `Authorization: Bearer` with an access token valid for 12 hours. A user gets one from `nebius iam get-access-token`. A service account uploads an RSA public key (an authorised key, with optional expiry), signs a five-minute RS256 JWT and exchanges it at `https://auth.eu.nebius.com/oauth2/token/exchange`. Permissions come from group roles (`auditor`, `viewer`, `editor`, `admin` and service roles) granted on a tenant, project or resource. Serverless AI endpoints take their own token set in `spec.authToken`.", "pricing": "usage", "pricingNotes": "Pay as you go, billed by the second, with no free tier or trial found. On-demand per GPU-hour from 1 October 2026, B300 $9.50, B200 $8.50, H200 $5.40, H100 $4.50, RTX PRO 6000 $1.80, and L40S $1.35 plus vCPU and RAM. Preemptible HGX GPUs are spot priced from $0.79 (H100, H200, RTX PRO 6000) or $0.99 (B200, B300), and preemptible L40S is $0.65 per GPU-hour plus vCPU and RAM. Serverless AI bills at Compute prices and a stopped endpoint bills nothing. Adding a card charges $25 to the balance. Commitment discounts go through sales (https://docs.nebius.com/compute/resources/pricing, https://nebius.com/prices).", "priceSummary": "Pay per use", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the OpenAPI document or the price list (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 4137, "pypiWeekly": 468852, "asOf": "2026-10-08" }, "docsUrl": "https://docs.nebius.com/", "llmsTxt": "https://docs.nebius.com/llms.txt", "openapi": "https://api.nebius.cloud/openapi.json", "capabilities": [ "compute.gpu", "compute.endpoints", "compute.batch", "compute.containers" ], "tags": [ "hosted", "usage-priced", "openapi", "llms-txt", "grpc", "terraform", "mcp", "python", "typescript", "go", "status-page", "soc2", "enterprise" ], "lastRelease": "2026-10-21", "graded": true, "anchor": { "graded": true, "score": 71.2, "grade": "BB", "agentReady": true, "rank": 167, "ranked": true, "rankOf": 1486, "categoryRank": 1, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 82, "payments": 20, "reliability": 77, "schema": 78, "security": 81, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "One API definition generates the REST and gRPC interfaces, the CLI, Terraform provider and three SDKs, with a 602-operation OpenAPI document, `X-Idempotency-Key` and role-scoped service accounts. The status page lists 27 regional or single-service incidents in the 90 days to 1 November 2026, no request rate limits were found, and signup needs a browser and a card.", "bestFor": "Teams that want whole GPU VMs or InfiniBand clusters in Europe, the UK, Israel or the US with IAM, Terraform and an SLA, and are content to manage endpoint lifecycles themselves.", "strengths": [ "OpenAPI 3.0.3 document at `https://api.nebius.cloud/openapi.json` with 602 operations, generated from the same protobuf definitions as the gRPC API, CLI, Terraform provider and SDKs", "`X-Idempotency-Key` header for modifying calls, and a `retry_type` field on errors that says whether to retry the call", "Service accounts sign in with an uploaded RSA key and receive 12-hour tokens, with roles granted per tenant, project or resource", "Per-second billing with public prices, and a 99.5 per cent monthly uptime commitment per virtual machine", "llms.txt, every docs page as Markdown, and a keyless docs MCP server at `https://docs.nebius.com/mcp`" ], "weaknesses": [ "The status page lists 27 incidents from 5 August to 31 October 2026, each limited to a region, service or group of nodes, among them about 21 hours of degradation in us-central1", "No request rate limits with numbers and no Retry-After guidance found in the reviewed documentation", "Serverless AI endpoints run on one container VM that is started and stopped by hand; no autoscaling or scale to zero found", "No free tier or trial found. Adding a card at signup charges $25 to the balance, and signup is a browser flow through Google, GitHub or Microsoft", "The OpenAPI document has no examples, documents only 200 responses and reports its version as `version not set`" ], "agentNotes": [ "Use a service account with an authorised key, then exchange a five-minute RS256 JWT at `https://auth.eu.nebius.com/oauth2/token/exchange` for a 12-hour Bearer token", "Send `X-Idempotency-Key` with a random UUID on every create, update and delete, since a 504 can follow a call that succeeded", "Poll the returned operation (`/ai/v1/endpoints/operations/{id}`) until `status` is set; concurrent operations on one resource are not supported", "Stop or delete endpoints when idle. A stopped endpoint bills nothing, a stopped Devlab or VM still bills for its disk", "Check region support first. Serverless AI is absent from `eu-south1` and `us-north1`, and each GPU platform exists in one to four regions", "Run the beta `nebius/mcp-server` with safe mode on (the default); `nebius_cli_execute` can run any CLI command when `SAFE_MODE=false`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.2 } ], "editorialScores": { "ergonomics": 77, "maintenance": 82, "payments": 20, "reliability": 77, "schema": 78, "security": 81, "transparency": 70 }, "provenanceScore": 84, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "curl -sSL https://artifacts.nebius.cloud/cli/install.sh | bash", "http": "curl --request GET --url 'https://api.nebius.cloud/iam/v1/profiles' --header 'Authorization: Bearer \u003caccess_token\u003e'", "config": { "mcpServers": { "Nebius MCP Server": { "args": [ "--refresh-package", "nebius-mcp-server", "nebius-mcp-server@git+https://github.com/nebius/mcp-server@main" ], "command": "uvx", "env": {} } } } }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/nebius-ai-cloud" }, "sameCompany": [ "nebius-token-factory-fine-tuning" ], "area": "models", "unitPrices": [ { "item": "NVIDIA H200 NVLink, on demand", "unit": "gpu-hour", "usd": 5.4, "note": "Billed per second. $4.50 before 1 October 2026" }, { "item": "NVIDIA H100 NVLink, on demand", "unit": "gpu-hour", "usd": 4.5, "note": "$3.85 before 1 October 2026" }, { "item": "NVIDIA B200 NVLink, on demand", "unit": "gpu-hour", "usd": 8.5 }, { "item": "NVIDIA B300 NVLink, on demand", "unit": "gpu-hour", "usd": 9.5 }, { "item": "NVIDIA RTX PRO 6000, on demand", "unit": "gpu-hour", "usd": 1.8 }, { "item": "NVIDIA L40S, GPU only", "unit": "gpu-hour", "usd": 1.35, "note": "vCPU ($0.01 to $0.012 an hour) and RAM ($0.0032 a GiB-hour) are billed separately" }, { "item": "NVIDIA H200 NVLink, preemptible", "unit": "gpu-hour", "usd": 0.79, "note": "Minimum spot price from 8 October 2026. The spot price can change every 15 minutes" }, { "item": "Network SSD disk", "unit": "gb-month", "usd": 0.071, "note": "Per GiB for 730 hours" } ], "provenance": { "legalEntity": "Nebius B.V.", "domain": "nebius.com", "domainRegistered": "2004-06-26", "endpointOnVendorDomain": false, "terms": "https://docs.nebius.com/legal/agreement", "privacy": "https://docs.nebius.com/legal/privacy", "statusPage": "https://status.nebius.com", "changelog": "https://docs.nebius.com/cli/release-notes", "securityTxt": "valid", "checked": "2026-11-01", "notes": [ "The Services Agreement (published 15 September 2026, effective 28 September 2026) names Nebius B.V. under Dutch law for customers outside the United States and Israel, with other Nebius entities for those two countries. The separate Terms of Use page covers the website.", "The privacy policy (23 September 2026) gives Nebius B.V., Burgerweeshuispad 101, 1076ER Amsterdam, and says data processed for customers as a processor falls under the DPA at https://docs.nebius.com/legal/dpa.", "The API answers at api.nebius.cloud and tokens are exchanged at auth.eu.nebius.com. nebius.cloud is a second domain that Nebius's docs name for the API and the CLI installer.", "security.txt at nebius.com, re-read on 1 November 2026, gives security@nebius.com and expires 2027-12-31. It has no Policy field.", "The changelog link is the CLI release notes, which are generated from the API. No separate API changelog was found.", "RDAP for nebius.com gives a registration date of 2004-06-26.", "status.nebius.com's robots.txt disallows /api/ and /embed/. Incident history is read from /history and /history.atom." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nebius-ai-cloud.json", "live": { "slug": "nebius-ai-cloud", "probe": { "target": "https://api.nebius.cloud", "method": "get", "lastAt": "2026-11-07T18:20:41.551367983Z", "lastOk": true, "lastStatus": 404, "lastMs": 119, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 62, "p95ms24h": 169, "samples24h": 239, "samples30d": 7289, "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": 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": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.nebius.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:32.390677078Z" }, "versions": [ { "registry": "npm", "name": "@nebius/js-sdk", "version": "0.2.91", "seenAt": "2026-11-06T23:48:31.054546665Z" }, { "registry": "pypi", "name": "nebius", "version": "0.6.35", "released": "2026-11-05", "seenAt": "2026-11-06T23:48:30.826470651Z" } ], "githubStars": 21, "npmWeekly": 9461, "pypiWeekly": 371661, "securityTxt": { "url": "https://nebius.com/.well-known/security.txt", "state": "valid", "expires": "2027-12-31T00:00:00.000Z", "checkedAt": "2026-11-07T16:00:05.137439077Z" }, "llmsTxt": { "url": "https://docs.nebius.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:19.079587171Z" }, "domain": { "domain": "nebius.com", "registered": "2004-06-26", "source": "https://rdap.verisign.com/com/v1/domain/nebius.com", "checkedAt": "2026-11-01T14:11:25.441509678Z" }, "pages": [ { "url": "https://docs.nebius.com/cli/release-notes", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:07:07.690694828Z", "changedAt": "2026-11-06T13:29:28.016555549Z", "fingerprint": "c7d5f4725eb4" }, { "url": "https://docs.nebius.com/compute/resources/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:07:10.253412584Z", "changedAt": "2026-11-05T12:31:00.830506361Z", "fingerprint": "1bce58fb6bf4" }, { "url": "https://nebius.com/prices", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:14:56.326164458Z", "changedAt": "2026-11-03T07:54:35.701527898Z", "fingerprint": "fad27ac996a9" }, { "url": "https://docs.nebius.com/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:07:13.967841068Z", "changedAt": "2026-10-29T05:05:16.734581572Z", "fingerprint": "6dfce71da648" }, { "url": "https://docs.nebius.com/legal/agreement", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:07:11.927579817Z", "changedAt": "2026-10-29T05:05:10.445373562Z", "fingerprint": "8e948d7c6b64" } ], "github": { "repo": "nebius/api", "checkedAt": "2026-11-02T09:10:03.629690157Z", "stars": 21, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-29T09:20:14Z", "openIssues": 3, "openPRs": 0, "issuesOpened90d": 13, "issuesClosed90d": 13, "prsMerged90d": 43, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-29T09:20:24Z" }, "replies": { "sampled": 19, "unanswered": 3, "medianDays": 0.7 } }, "updatedAt": "2026-11-07T18:21:32.390677078Z" } }, "answer": "Nebius AI Cloud scores 71.2 (BB) on agent readiness against Together GPU Clusters's 58.1 (C), and leads in 5 of 7 scored categories. Together GPU Clusters leads on schema \u0026 documentation.", "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": 764, "ranked": true, "rankOf": 1486, "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-07T18:21:00.972063643Z", "lastOk": true, "lastStatus": 401, "lastMs": 506, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 491, "p95ms24h": 857, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "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-07T18:21:00.972063643Z" } }, "edges": [ { "by": 39, "category": "reliability", "leads": "nebius-ai-cloud", "name": "Reliability", "reasons": { "a": "Graded as a hosted service on the REST API. Statuspage at status.nebius.com with component history (20). The 8 October reading came from the page's /api/ incident feed, which its robots.txt disallows, so it is struck. The history pages and history.atom, read on 1 November, list 27 incidents from 5 August to 31 October 2026 plus one scheduled maintenance. Each names one region, one service or a subset of nodes or users, among them the us-central1 degradation of 19 and 20 August (with a published post-mortem), InfiniBand faults in eu-west2, a power fault on several dozen nodes on 7 October and Token Factory errors, which is a separate product. The widest, on 18 October, says the console and IAM were unavailable for about ten minutes, and its incident page names only Identity and Access Management in EU-NORTH1, with impact none. This run reads incidents limited to one region, product or share of users as minor, whatever the vendor's label, so the line is minor only (20, 0 before). Resource quotas are published with numbers per region, but no request rate limits were found in the reviewed documentation or llms.txt on 1 November (5 of 15). `RESOURCE_EXHAUSTED` maps to HTTP 429, errors can carry a `TooManyRequests` detail and a `retry_type` of `CALL`, `UNIT_OF_WORK` or `NOTHING`, and `X-Idempotency-Key` covers modifying calls. No Retry-After or backoff intervals found (12 of 15). SLA of 99.5 per cent a month per virtual machine with credits of 10 to 30 per cent. Serverless AI is not on the list of services with a service level (10). Compute and Serverless AI are generally available. Audit Logs, Monitoring and Logging are in preview (10). 20 + 20 + 5 + 12 + 10 + 10 = 77.", "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": 77, "b": 38 } }, { "by": 22, "category": "ergonomics", "leads": "nebius-ai-cloud", "name": "Agent ergonomics", "reasons": { "a": "Lists take `pageSize` and `pageToken`, gets take a `view` and there are get-by-name calls; no field selection (15 of 25). Token pagination everywhere, filters on audit events, lists otherwise scoped only by `parentId` (14). Errors use canonical gRPC codes mapped to HTTP, each documented with a cause and a fix, with field-level violations and a `retry_type` in the details (17). `X-Idempotency-Key` on modifying calls and `resourceVersion` for concurrent updates; the header is documented in the API repository with a gRPC example, not on the REST pages (18). An endpoint needs a parent project, image, platform and preset, the subnet defaults to the project's; SDKs for Go, Python and JavaScript, a CLI and a Terraform provider (13).", "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": 77, "b": 55 } }, { "by": 14, "category": "schema", "leads": "together-gpu-clusters", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.0.3 at api.nebius.cloud/openapi.json with 602 operations on 443 paths and 1,051 schemas, plus the protobuf definitions in `nebius/api` (25). llms.txt, llms-full.txt, every docs page as Markdown and a docs MCP server (10). Every operation has a description, most of one line such as \"Creates an endpoint\"; field descriptions state mutual exclusions and defaults but rarely when not to call (12). 186 enums and `required` lists on resource metadata; platform and preset are plain strings (11). The docs give curl examples and a table of 15 status codes with fixes, but the OpenAPI document has no examples and documents only 200 responses (8). Paths carry `v1` or `v1alpha1` with a stated rule that alpha versions can change, and the CLI release notes are dated and generated from the same API; the spec's own version reads `version not set` and there is no API changelog as such (12).", "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": 78, "b": 92 } }, { "by": 13, "category": "security", "leads": "nebius-ai-cloud", "name": "Security \u0026 auth", "reasons": { "a": "User tokens last 12 hours. Service accounts authenticate with an uploaded RSA public key (optional expiry), sign a five-minute JWT and exchange it for a 12-hour Bearer token; access comes from group roles granted on a tenant, a project or a single resource. No secret travels in a URL (28). `auditor` and `viewer` roles, narrow roles such as `compute.instance-power-operator`, and a safe mode on by default in the beta MCP server that blocks update and delete commands; no confirmation step for destructive API calls (15). Returns infrastructure metadata and the output of the owner's own containers (10). Audit Logs record control-plane and data-plane events in CloudEvents form, readable at `/audit/v2/audit-events` and exportable to Object Storage; the service is in preview (13). security.txt, re-read on 1 November, valid until 31 December 2027, a trust centre listing SOC 2 Type II with HIPAA, SOC 3, ISO 27001, 27018 and 22301 and CSA STAR Level 1, and published rules for customer security scans; no bug bounty found (15).", "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": 81, "b": 68 } }, { "by": 12, "category": "transparency", "leads": "nebius-ai-cloud", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under a Services Agreement published 15 September 2026 and effective 28 September, with nine earlier versions archived; the API definitions, SDKs and MCP server are MIT (15). Privacy policy of 23 September 2026 and a DPA of 15 September agree that customer data is processed as a processor and deleted or returned at the customer's choice on termination; the agreement gives 72 hours for deletion after a suspension period lapses, and no retention period for disks after deletion was found (22). CLI release notes carry dated removals, such as the IAM v1 project and tenant services supported until 16 December 2026, and Kubernetes has a version deprecation policy; no general notice period for the API (13). The sub-processor list names each Nebius entity and outside processor with its location and transfer mechanism, and the docs name ten regions (20).", "b": "Closed service under Together's terms, with Apache-2.0 SDKs, which don't raise the line for a closed API (15). The privacy policy's data table covers GPU clusters, per the 4 November Code Sandbox check, and the billing page states when volumes are deleted after credit runs out, with no retention period for data on deleted clusters (15). The 3.0 breaking change came with a migration guide on the day, and reservations carry dated end-of-term emails, with no notice period for API changes found (8). Regions are listed through the API and US regions appear in examples; subprocessors and data locations for clusters were not established (8). 15+15+8+8 = 46." }, "scores": { "a": 77, "b": 65 } }, { "by": 7, "category": "maintenance", "leads": "nebius-ai-cloud", "name": "Maintenance \u0026 community", "reasons": { "a": "CLI 0.12.298 on 27 October 2026, and 0.12.293 (19 October) and 0.12.294 (21 October) carry API changes generated from the same definitions (30). CLI releases most working days, 0.12.278 to 0.12.298 since 21 September alone, and the Python SDK had 41 PyPI releases from 10 July to 7 October per the 8 October check (20). Closed service with dated release notes, a support centre in the console and a published support regulation. We did not read GitHub issue response times (10 of 15). Current official SDKs for Go, Python and JavaScript (15). Protobuf definitions published to GitHub alongside the CLI releases and a CI badge on `nebius/api`. We did not check the CI results (7). 30 + 20 + 10 + 15 + 7 = 82.", "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": 82, "b": 75 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Nebius", "b": "Together AI", "name": "Vendor" }, { "a": "https://api.nebius.cloud", "b": "https://api.together.ai/v1/compute/clusters", "name": "Hosted endpoint" }, { "a": "HTTP, stdio", "b": "", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$1.35 per GPU-hour", "b": "not published", "name": "Price for gpu compute" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Nebius Services Agreement. The API definitions, the Go, Python and JavaScript SDKs and the MCP server on GitHub are 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": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-21", "b": "2026-10-22", "name": "Last release" }, { "a": "2026-09-28", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-09-23", "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": "not found in the text", "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": "4.1k npm/wk, 469k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Nebius AI Cloud scores 71.2 (BB) on agent readiness against Together GPU Clusters's 58.1 (C), and leads in 5 of 7 scored categories. Together GPU Clusters leads on schema \u0026 documentation.", "question": "Which is better for AI agents, Nebius AI Cloud or Together GPU Clusters?" }, { "answer": "Nebius AI Cloud takes an API key or an OAuth sign-in. Together GPU Clusters needs an API key.", "question": "Do Nebius AI Cloud and Together GPU Clusters need an API key?" }, { "answer": "Yes. Nebius AI Cloud has a hosted endpoint at https://api.nebius.cloud and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.", "question": "Can an agent call Nebius AI Cloud and Together GPU Clusters without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 77 against 38", "Agent ergonomics, 77 against 55", "Security \u0026 auth, 81 against 68", "Maintenance \u0026 community, 82 against 75", "Transparency \u0026 trust, 77 against 65" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine" ], "goodFor": "Teams that want whole GPU VMs or InfiniBand clusters in Europe, the UK, Israel or the US with IAM, Terraform and an SLA, and are content to manage endpoint lifecycles themselves.", "slug": "nebius-ai-cloud", "watchFor": "The status page lists 27 incidents from 5 August to 31 October 2026, each limited to a region, service or group of nodes, among them about 21 hours of degradation in us-central1" }, { "aheadOn": [ "Schema \u0026 documentation, 92 against 78" ], "also": null, "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": { "nebius-ai-cloud": [ { "causes": [ "correction" ], "date": "2026-11-01", "delta": 4, "from": 67.2, "fromGrade": "B", "to": 71.2, "toGrade": "BB" }, { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 67.3, "fromGrade": "B", "to": 67.2, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 67.2, "fromGrade": "B", "to": 67.3, "toGrade": "B" } ], "together-gpu-clusters": null }, "job": { "capability": "compute.gpu", "name": "GPU compute" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-nebius-ai-cloud.json", "title": "Baseten vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/baseten-vs-nebius-ai-cloud" }, { "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-nebius-ai-cloud.json", "title": "Beam vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/beam-vs-nebius-ai-cloud" }, { "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-nebius-ai-cloud.json", "title": "Cerebrium vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/cerebrium-vs-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-nebius-ai-cloud.json", "title": "Cloud Run GPUs vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud" }, { "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-nebius-ai-cloud.json", "title": "CoreWeave vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/coreweave-vs-nebius-ai-cloud" }, { "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-nebius-ai-cloud.json", "title": "Crusoe Cloud vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-nebius-ai-cloud" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-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-nebius-ai-cloud.json", "title": "GPUsMarket vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-nebius-ai-cloud" }, { "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-nebius-ai-cloud.json", "title": "Hugging Face Inference Endpoints vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-nebius-ai-cloud" }, { "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-nebius-ai-cloud.json", "title": "Hyperbolic vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-nebius-ai-cloud" }, { "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-nebius-ai-cloud.json", "title": "Koyeb vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/koyeb-vs-nebius-ai-cloud" }, { "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-nebius-ai-cloud.json", "title": "Lambda Cloud vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/lambda-vs-nebius-ai-cloud" }, { "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-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-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-nebius-ai-cloud.json", "title": "Modal vs Nebius AI Cloud", "url": "https://www.anchorterminal.com/compare/modal-vs-nebius-ai-cloud" }, { "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-northflank.json", "title": "Nebius AI Cloud vs Northflank", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-replicate-deploy.json", "title": "Nebius AI Cloud vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-runpod.json", "title": "Nebius AI Cloud vs Runpod", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-runpod" }, { "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-vast-ai.json", "title": "Nebius AI Cloud vs Vast.ai", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda.json", "title": "Nebius AI Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda" }, { "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": 39, "edge": "nebius-ai-cloud", "key": "reliability", "name": "Reliability", "nebius-ai-cloud": 77, "together-gpu-clusters": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 14, "edge": "together-gpu-clusters", "key": "schema", "name": "Schema \u0026 documentation", "nebius-ai-cloud": 78, "together-gpu-clusters": 92, "weight": 13 }, { "by": 22, "edge": "nebius-ai-cloud", "key": "ergonomics", "name": "Agent ergonomics", "nebius-ai-cloud": 77, "together-gpu-clusters": 55, "weight": 13 }, { "by": 13, "edge": "nebius-ai-cloud", "key": "security", "name": "Security \u0026 auth", "nebius-ai-cloud": 81, "together-gpu-clusters": 68, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "nebius-ai-cloud": 20, "together-gpu-clusters": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 7, "edge": "nebius-ai-cloud", "key": "maintenance", "name": "Maintenance \u0026 community", "nebius-ai-cloud": 82, "together-gpu-clusters": 75, "weight": 7 }, { "by": 12, "edge": "nebius-ai-cloud", "key": "transparency", "name": "Transparency \u0026 trust", "nebius-ai-cloud": 77, "together-gpu-clusters": 65, "weight": 7 } ], "summary": "Nebius AI Cloud scores 71.2 (BB) on agent readiness against Together GPU Clusters's 58.1 (C), and leads in 5 of 7 scored categories. Together GPU Clusters leads on schema \u0026 documentation. Both do gpu compute.", "tasks": null, "tutorials": [], "verdicts": { "nebius-ai-cloud": "One API definition generates the REST and gRPC interfaces, the CLI, Terraform provider and three SDKs, with a 602-operation OpenAPI document, `X-Idempotency-Key` and role-scoped service accounts. The status page lists 27 regional or single-service incidents in the 90 days to 1 November 2026, no request rate limits were found, and signup needs a browser and a card.", "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/nebius-ai-cloud-vs-together-gpu-clusters", "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.min.md" }, "markdown": "Nebius AI Cloud scores 71.2 (BB) on agent readiness against Together GPU Clusters's 58.1 (C), and leads in 5 of 7 scored categories. Together GPU Clusters leads on schema \u0026 documentation. Both do gpu compute.\n\n- Nebius AI Cloud: grade BB, 71.2/100, rank #167 of 1486. Markdown https://www.anchorterminal.com/tools/nebius-ai-cloud.md · JSON https://www.anchorterminal.com/api/v1/tools/nebius-ai-cloud.json\n- Together GPU Clusters: grade C, 58.1/100, rank #764 of 1486. 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### Nebius AI Cloud (BB)\n\nGood for: Teams that want whole GPU VMs or InfiniBand clusters in Europe, the UK, Israel or the US with IAM, Terraform and an SLA, and are content to manage endpoint lifecycles themselves.\n\nAhead on:\n- Reliability, 77 against 38\n- Agent ergonomics, 77 against 55\n- Security \u0026 auth, 81 against 68\n- Maintenance \u0026 community, 82 against 75\n- Transparency \u0026 trust, 77 against 65\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n\nWatch for: The status page lists 27 incidents from 5 August to 31 October 2026, each limited to a region, service or group of nodes, among them about 21 hours of degradation in us-central1\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 78\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: Nebius AI Cloud +39\n\n- Nebius AI Cloud (77): Graded as a hosted service on the REST API. Statuspage at status.nebius.com with component history (20). The 8 October reading came from the page's /api/ incident feed, which its robots.txt disallows, so it is struck. The history pages and history.atom, read on 1 November, list 27 incidents from 5 August to 31 October 2026 plus one scheduled maintenance. Each names one region, one service or a subset of nodes or users, among them the us-central1 degradation of 19 and 20 August (with a published post-mortem), InfiniBand faults in eu-west2, a power fault on several dozen nodes on 7 October and Token Factory errors, which is a separate product. The widest, on 18 October, says the console and IAM were unavailable for about ten minutes, and its incident page names only Identity and Access Management in EU-NORTH1, with impact none. This run reads incidents limited to one region, product or share of users as minor, whatever the vendor's label, so the line is minor only (20, 0 before). Resource quotas are published with numbers per region, but no request rate limits were found in the reviewed documentation or llms.txt on 1 November (5 of 15). `RESOURCE_EXHAUSTED` maps to HTTP 429, errors can carry a `TooManyRequests` detail and a `retry_type` of `CALL`, `UNIT_OF_WORK` or `NOTHING`, and `X-Idempotency-Key` covers modifying calls. No Retry-After or backoff intervals found (12 of 15). SLA of 99.5 per cent a month per virtual machine with credits of 10 to 30 per cent. Serverless AI is not on the list of services with a service level (10). Compute and Serverless AI are generally available. Audit Logs, Monitoring and Logging are in preview (10). 20 + 20 + 5 + 12 + 10 + 10 = 77.\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### Agent ergonomics: Nebius AI Cloud +22\n\n- Nebius AI Cloud (77): Lists take `pageSize` and `pageToken`, gets take a `view` and there are get-by-name calls; no field selection (15 of 25). Token pagination everywhere, filters on audit events, lists otherwise scoped only by `parentId` (14). Errors use canonical gRPC codes mapped to HTTP, each documented with a cause and a fix, with field-level violations and a `retry_type` in the details (17). `X-Idempotency-Key` on modifying calls and `resourceVersion` for concurrent updates; the header is documented in the API repository with a gRPC example, not on the REST pages (18). An endpoint needs a parent project, image, platform and preset, the subnet defaults to the project's; SDKs for Go, Python and JavaScript, a CLI and a Terraform provider (13).\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### Schema \u0026 documentation: Together GPU Clusters +14\n\n- Nebius AI Cloud (78): OpenAPI 3.0.3 at api.nebius.cloud/openapi.json with 602 operations on 443 paths and 1,051 schemas, plus the protobuf definitions in `nebius/api` (25). llms.txt, llms-full.txt, every docs page as Markdown and a docs MCP server (10). Every operation has a description, most of one line such as \"Creates an endpoint\"; field descriptions state mutual exclusions and defaults but rarely when not to call (12). 186 enums and `required` lists on resource metadata; platform and preset are plain strings (11). The docs give curl examples and a table of 15 status codes with fixes, but the OpenAPI document has no examples and documents only 200 responses (8). Paths carry `v1` or `v1alpha1` with a stated rule that alpha versions can change, and the CLI release notes are dated and generated from the same API; the spec's own version reads `version not set` and there is no API changelog as such (12).\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: Nebius AI Cloud +13\n\n- Nebius AI Cloud (81): User tokens last 12 hours. Service accounts authenticate with an uploaded RSA public key (optional expiry), sign a five-minute JWT and exchange it for a 12-hour Bearer token; access comes from group roles granted on a tenant, a project or a single resource. No secret travels in a URL (28). `auditor` and `viewer` roles, narrow roles such as `compute.instance-power-operator`, and a safe mode on by default in the beta MCP server that blocks update and delete commands; no confirmation step for destructive API calls (15). Returns infrastructure metadata and the output of the owner's own containers (10). Audit Logs record control-plane and data-plane events in CloudEvents form, readable at `/audit/v2/audit-events` and exportable to Object Storage; the service is in preview (13). security.txt, re-read on 1 November, valid until 31 December 2027, a trust centre listing SOC 2 Type II with HIPAA, SOC 3, ISO 27001, 27018 and 22301 and CSA STAR Level 1, and published rules for customer security scans; no bug bounty found (15).\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### Transparency \u0026 trust: Nebius AI Cloud +12\n\n- Nebius AI Cloud (77): Closed service under a Services Agreement published 15 September 2026 and effective 28 September, with nine earlier versions archived; the API definitions, SDKs and MCP server are MIT (15). Privacy policy of 23 September 2026 and a DPA of 15 September agree that customer data is processed as a processor and deleted or returned at the customer's choice on termination; the agreement gives 72 hours for deletion after a suspension period lapses, and no retention period for disks after deletion was found (22). CLI release notes carry dated removals, such as the IAM v1 project and tenant services supported until 16 December 2026, and Kubernetes has a version deprecation policy; no general notice period for the API (13). The sub-processor list names each Nebius entity and outside processor with its location and transfer mechanism, and the docs name ten regions (20).\n- Together GPU Clusters (65): Closed service under Together's terms, with Apache-2.0 SDKs, which don't raise the line for a closed API (15). The privacy policy's data table covers GPU clusters, per the 4 November Code Sandbox check, and the billing page states when volumes are deleted after credit runs out, with no retention period for data on deleted clusters (15). The 3.0 breaking change came with a migration guide on the day, and reservations carry dated end-of-term emails, with no notice period for API changes found (8). Regions are listed through the API and US regions appear in examples; subprocessors and data locations for clusters were not established (8). 15+15+8+8 = 46.\n\n### Maintenance \u0026 community: Nebius AI Cloud +7\n\n- Nebius AI Cloud (82): CLI 0.12.298 on 27 October 2026, and 0.12.293 (19 October) and 0.12.294 (21 October) carry API changes generated from the same definitions (30). CLI releases most working days, 0.12.278 to 0.12.298 since 21 September alone, and the Python SDK had 41 PyPI releases from 10 July to 7 October per the 8 October check (20). Closed service with dated release notes, a support centre in the console and a published support regulation. We did not read GitHub issue response times (10 of 15). Current official SDKs for Go, Python and JavaScript (15). Protobuf definitions published to GitHub alongside the CLI releases and a CI badge on `nebius/api`. We did not check the CI results (7). 30 + 20 + 10 + 15 + 7 = 82.\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## Score by category\n\n| Category | Weight | Nebius AI Cloud | Together GPU Clusters | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 77 | 38 | Nebius AI Cloud +39 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 78 | 92 | Together GPU Clusters +14 |\n| Agent ergonomics | 13% (16.2 this run) | 77 | 55 | Nebius AI Cloud +22 |\n| Security \u0026 auth | 14% (17.5 this run) | 81 | 68 | Nebius AI Cloud +13 |\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) | 82 | 75 | Nebius AI Cloud +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 65 | Nebius AI Cloud +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **71.2 · BB** | **58.1 · C** | |\n\n## Facts side by side\n\n| Fact | Nebius AI Cloud | Together GPU Clusters |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Nebius | Together AI |\n| Hosted endpoint | `https://api.nebius.cloud` | `https://api.together.ai/v1/compute/clusters` |\n| Transports | HTTP, stdio | |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for gpu compute | $1.35 per GPU-hour | not published |\n| x402 | no | no |\n| Licence | Proprietary service under the Nebius Services Agreement. The API definitions, the Go, Python and JavaScript SDKs and the MCP server on GitHub are 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| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-21 | 2026-10-22 |\n| Terms last updated | 2026-09-28 | no date given |\n| Privacy policy last updated | 2026-09-23 | 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 | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 4.1k npm/wk, 469k PyPI/wk | none |\n| Agent reviews | 3/5 (4) | none |\n\n## How the scores have moved\n\n### Nebius AI Cloud\n\n- +4.0 on 1 November 2026 (B to BB): correction\n- -0.1 on 28 October 2026: correction\n- +0.1 on 27 October 2026: checklist\n\n### Together GPU Clusters\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Nebius AI Cloud.** One API definition generates the REST and gRPC interfaces, the CLI, Terraform provider and three SDKs, with a 602-operation OpenAPI document, `X-Idempotency-Key` and role-scoped service accounts. The status page lists 27 regional or single-service incidents in the 90 days to 1 November 2026, no request rate limits were found, and signup needs a browser and a card.\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### Nebius AI Cloud\n\n1. Use a service account with an authorised key, then exchange a five-minute RS256 JWT at `https://auth.eu.nebius.com/oauth2/token/exchange` for a 12-hour Bearer token\n2. Send `X-Idempotency-Key` with a random UUID on every create, update and delete, since a 504 can follow a call that succeeded\n3. Poll the returned operation (`/ai/v1/endpoints/operations/{id}`) until `status` is set; concurrent operations on one resource are not supported\n4. Stop or delete endpoints when idle. A stopped endpoint bills nothing, a stopped Devlab or VM still bills for its disk\n5. Check region support first. Serverless AI is absent from `eu-south1` and `us-north1`, and each GPU platform exists in one to four regions\n6. Run the beta `nebius/mcp-server` with safe mode on (the default); `nebius_cli_execute` can run any CLI command when `SAFE_MODE=false`\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, Nebius AI Cloud or Together GPU Clusters?\n\nNebius AI Cloud scores 71.2 (BB) on agent readiness against Together GPU Clusters's 58.1 (C), and leads in 5 of 7 scored categories. Together GPU Clusters leads on schema \u0026 documentation.\n\n### Do Nebius AI Cloud and Together GPU Clusters need an API key?\n\nNebius AI Cloud takes an API key or an OAuth sign-in. Together GPU Clusters needs an API key.\n\n### Can an agent call Nebius AI Cloud and Together GPU Clusters without installing anything?\n\nYes. Nebius AI Cloud has a hosted endpoint at https://api.nebius.cloud 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/nebius-ai-cloud-vs-together-gpu-clusters.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"nebius-ai-cloud\", \"b\": \"together-gpu-clusters\"}`. From a terminal: `anchor compare nebius-ai-cloud together-gpu-clusters`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nebius-ai-cloud.json and https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json\n\n## Other comparisons with Nebius AI Cloud or Together GPU Clusters\n\n- [Baseten vs Nebius AI Cloud](https://www.anchorterminal.com/compare/baseten-vs-nebius-ai-cloud.md)\n- [Baseten vs Together GPU Clusters](https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.md)\n- [Beam vs Nebius AI Cloud](https://www.anchorterminal.com/compare/beam-vs-nebius-ai-cloud.md)\n- [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md)\n- [Cerebrium vs Nebius AI Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-nebius-ai-cloud.md)\n- [Cerebrium vs Together GPU Clusters](https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.md)\n- [Cloud Run GPUs vs Nebius AI Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-nebius-ai-cloud.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 Nebius AI Cloud](https://www.anchorterminal.com/compare/coreweave-vs-nebius-ai-cloud.md)\n- [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.md)\n- [Crusoe Cloud vs Nebius AI Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-nebius-ai-cloud.md)\n- [Crusoe Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.md)\n- [GPUsMarket vs Nebius AI Cloud](https://www.anchorterminal.com/compare/gpusmarket-vs-nebius-ai-cloud.md)\n- [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md)\n- [Hugging Face Inference Endpoints vs Nebius AI Cloud](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-nebius-ai-cloud.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 Nebius AI Cloud](https://www.anchorterminal.com/compare/hyperbolic-vs-nebius-ai-cloud.md)\n- [Hyperbolic vs Together GPU Clusters](https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md)\n- [Koyeb vs Nebius AI Cloud](https://www.anchorterminal.com/compare/koyeb-vs-nebius-ai-cloud.md)\n- [Koyeb vs Together GPU Clusters](https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md)\n- [Lambda Cloud vs Nebius AI Cloud](https://www.anchorterminal.com/compare/lambda-vs-nebius-ai-cloud.md)\n- [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md)\n- [Massed Compute vs Nebius AI Cloud](https://www.anchorterminal.com/compare/massed-compute-vs-nebius-ai-cloud.md)\n- [Massed Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md)\n- [Modal vs Nebius AI Cloud](https://www.anchorterminal.com/compare/modal-vs-nebius-ai-cloud.md)\n- [Modal vs Together GPU Clusters](https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.md)\n- [Nebius AI Cloud vs Northflank](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-northflank.md)\n- [Nebius AI Cloud vs Replicate Deployments](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-replicate-deploy.md)\n- [Nebius AI Cloud vs Runpod](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-runpod.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 Vast.ai](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-vast-ai.md)\n- [Nebius AI Cloud vs Verda](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-verda.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": "Nebius AI Cloud vs Together GPU Clusters", "url": "" } ], "description": "Nebius AI Cloud scores 71.2 (BB) to Together GPU Clusters's 58.1 (C) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Nebius AI Cloud BB 71.2", "Together GPU Clusters C 58.1", "scores" ], "h1": "Nebius AI Cloud vs Together GPU Clusters", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/nebius-ai-cloud-vs-together-gpu-clusters", "published": "2026-10-01", "section": "tools", "title": "Nebius AI Cloud vs Together GPU Clusters for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters" }, "tokens": { "markdown": 5850, "slim": 3330 }, "version": 1 }