{ "data": { "a": { "slug": "lambda", "name": "Lambda Cloud", "vendor": "Lambda", "vendorUrl": "https://lambda.ai", "kind": "http-api", "category": "gpu-compute", "summary": "On-demand GPU virtual machines and clusters, with an API for provisioning compute and persistent storage.", "url": "https://www.anchorterminal.com/tools/lambda", "markdownUrl": "https://www.anchorterminal.com/tools/lambda.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lambda.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lambda.json", "dns": "lambda.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://cloud.lambda.ai/api/v1", "packages": [], "auth": "api-key", "authNotes": "API key created at cloud.lambda.ai/api-keys and sent as `Authorization: Bearer`. HTTP Basic with the key as the username (`curl -u 'KEY:'`) still works as a legacy option. SSH keys registered in the account are injected into launched instances.", "pricing": "usage", "pricingNotes": "On-demand, per GPU an hour, Tesla V100 16 GB $0.79, A100 40 GB $1.99, A100 80 GB $2.79, H100 SXM 80 GB $3.99, B200 180 GB $6.69. 1-Click Clusters of HGX B200 are quoted per GPU-hour at $9.86 for 16 GPUs, $9.36 for 64 and $8.87 for 256 or more on two-week to one-year commitments. Instances bill in one-minute increments from the moment they pass health checks until you terminate them, invoiced weekly. Filesystems bill per GB used a month in one-hour increments. No free tier (https://lambda.ai/pricing, https://docs.lambda.ai/public-cloud/billing/).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.lambda.com/public-cloud/on-demand/", "openapi": "https://docs.lambda.com/api/cloud/spec.json", "capabilities": [ "compute.gpu", "compute.containers" ], "tags": [ "hosted", "usage-priced", "openapi", "enterprise" ], "graded": true, "anchor": { "graded": true, "score": 52.9, "grade": "D", "agentReady": false, "rank": 963, "ranked": true, "rankOf": 1486, "categoryRank": 16, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 5, "payments": 20, "reliability": 55, "schema": 69, "security": 70, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "H100 SXM at $3.99 and B200 at $6.69 an hour with per-minute billing. No scale to zero, autoscaling or endpoints; an idle VM bills until terminated.", "bestFor": "Agents or pipelines that need a whole GPU machine with SSH for hours, such as training or batch jobs, and will manage the lifecycle themselves.", "strengths": [ "H100 SXM at $3.99 and B200 at $6.69 an hour with per-minute billing", "OpenAPI 3.1 spec with documented error codes, a `suggestion` field and cursor pagination", "Audit events endpoint filterable by time and resource type", "Published rate limits, one request a second and one launch every 12 seconds, with Retry-After on a 429", "Role-based access with service identities and a read-only role, and a trust portal with SOC 2 Type 2 and four ISO certifications" ], "weaknesses": [ "No scale to zero, autoscaling or endpoints; an idle VM bills until terminated", "Seven readable status incidents since August 2026, among them a two-day outage in one region", "No changelog, no llms.txt and no official SDK", "Launch has no idempotency key, and API keys have no documented rotation or expiry", "security.txt expired on 1 June 2026 and no free tier" ], "agentNotes": [ "Call `GET /instance-types` first and read `regions_with_capacity_available` before trying to launch", "Space launch calls 12 seconds apart; a sixth in a minute returns 429 with `global/rate-limited`, so wait for the Retry-After interval", "Branch on the error `code`, not the `message` or `suggestion`, which Lambda says may change", "List instances before retrying a failed launch, since there's no idempotency key and a retry can start a second machine", "Terminate the instance in a `finally` block; billing runs by the minute until you do", "Run under a service identity with only the workspace roles it needs, such as Instance Reader for monitoring" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 52.9 } ], "editorialScores": { "ergonomics": 63, "maintenance": 5, "payments": 20, "reliability": 55, "schema": 69, "security": 70, "transparency": 48 }, "provenanceScore": 71, "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": { "http": "curl \"https://cloud.lambda.ai/api/v1/instance-types\" -H \"Authorization: Bearer $LAMBDA_API_KEY\"" }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/lambda" }, "area": "models", "unitPrices": [ { "item": "H100 SXM 80 GB", "unit": "gpu-hour", "usd": 3.99, "note": "Billed per minute" }, { "item": "B200 180 GB", "unit": "gpu-hour", "usd": 6.69 }, { "item": "A100 SXM 80 GB", "unit": "gpu-hour", "usd": 2.79 }, { "item": "A100 SXM 40 GB", "unit": "gpu-hour", "usd": 1.99 }, { "item": "Tesla V100 16 GB", "unit": "gpu-hour", "usd": 0.79 }, { "item": "HGX B200 1-Click Cluster, 16 GPUs", "unit": "gpu-hour", "usd": 9.86, "note": "Two-week to one-year commitment; $8.87 at 256 GPUs or more" } ], "provenance": { "legalEntity": "Lambda, Inc.", "domain": "lambda.ai", "domainRegistered": "", "domainNote": "Lambda moved from lambdalabs.com, registered 2008-05-29, to lambda.ai. The .ai registry's RDAP server rate-limited our lookup of the new domain.", "endpointOnVendorDomain": true, "terms": "https://lambda.ai/legal/terms-of-service", "privacy": "https://lambda.ai/legal/privacy-policy", "statusPage": "https://status.lambda.ai", "changelog": "", "securityTxt": "expired", "checked": "2026-11-04", "notes": [ "Terms dated August 2025 and the privacy policy of 1 January 2026 name Lambda, Inc., 2510 Zanker Road, San Jose, California (privacy policy per the 1 October 2026 check).", "The API runs on cloud.lambda.ai, a subdomain of the vendor domain. The docs moved from docs.lambda.ai to docs.lambda.com, which docs.lambda.ai now redirects to.", "security.txt expired 2026-06-01 and has no Policy field (read 4 November 2026).", "No public changelog found for the cloud. The OpenAPI spec reports version 1.10.0." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lambda.json", "live": { "slug": "lambda", "probe": { "target": "https://cloud.lambda.ai/api/v1", "method": "get", "lastAt": "2026-11-07T18:20:34.210342176Z", "lastOk": true, "lastStatus": 403, "lastMs": 1104, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.8, "p50ms24h": 750, "p95ms24h": 1112, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 271 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "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": 236 }, { "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 } ], "outages": [ { "start": "2026-10-31T04:40:34.538053708Z", "end": "2026-10-31T05:43:37.088836787Z", "note": "EOF" } ] }, "vendorStatus": { "page": "https://status.lambda.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:19.765696346Z" }, "securityTxt": { "url": "https://lambda.ai/.well-known/security.txt", "state": "expired", "expires": "2026-06-01T16:00:00Z", "checkedAt": "2026-11-07T16:01:42.94704571Z" }, "domain": { "domain": "lambda.ai", "registered": "2017-12-16", "source": "https://rdap.identitydigital.services/rdap/domain/lambda.ai", "checkedAt": "2026-11-01T14:13:00.056712497Z" }, "pages": [ { "url": "https://lambda.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:12:19.409114908Z", "changedAt": "2026-11-07T14:12:19.409114908Z", "fingerprint": "43d2243dd65b" }, { "url": "https://lambda.ai/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:12:14.343180344Z", "changedAt": "2026-11-07T14:12:14.343180344Z", "fingerprint": "d0e1f9cb081a" }, { "url": "https://lambda.ai/legal/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:12:16.798534055Z", "changedAt": "2026-11-07T14:12:16.798534055Z", "fingerprint": "2d5b17c47588" } ], "updatedAt": "2026-11-07T18:21:19.765696346Z" } }, "answer": "Together GPU Clusters scores 58.1 (C) on agent readiness against Lambda Cloud's 52.9 (D), and leads in 3 of 7 scored categories. Lambda Cloud leads on reliability and agent ergonomics.", "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": 70, "category": "maintenance", "leads": "together-gpu-clusters", "name": "Maintenance \u0026 community", "reasons": { "a": "No changelog or release notes found, and the docs pages carry no dates, so we couldn't date the last API change. The spec still reads 1.10.0 although it gained identity, group, role and workspace paths since 1 October (0). No dated changes in the last 90 days found (0). Closed service with a status page that posts updates and a support-ticket API, but no changelog (5 of 15). No official SDK (0). No packages to assess (0). 0 + 0 + 5 + 0 + 0 = 5.", "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": 5, "b": 75 } }, { "by": 23, "category": "schema", "leads": "together-gpu-clusters", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 spec, version 1.10.0, linked from the API reference as a download, now 48 paths including identities, groups, roles and workspaces (25). No llms.txt (docs.lambda.com/llms.txt returns 404) and no Markdown twins (0). Operations are described with preconditions, for example a filesystem must be unmounted before deletion, but few say when not to call them (14). Required fields are marked; instance type names and statuses are plain strings rather than enums (10). Examples on requests and responses, and 400, 401, 403, 404, 409, 429 and 503 documented with a `code`, `message` and `suggestion` (15). The spec is versioned and flags `/file-systems` as deprecated, but there's no public changelog or release notes, and the identity and role paths arrived without a version change (5). 25 + 0 + 14 + 10 + 15 + 5 = 69.", "b": "Public OpenAPI 3.1 for /v1/compute/clusters and shared volumes, MIT, embedded in every reference page (25). llms.txt and a Markdown twin of every page (10). The docs say when to choose Kubernetes or Slurm and each capacity type, and the management page carries instructions for agents on reporting live availability and prices (18). Enums for cluster type, billing type, GPU type and status, required fields marked (13). CLI, Python, TypeScript and console steps on each task, with 402 and 403 cases documented, though no error catalogue for the clusters API (11). Versioned SDKs and a dated changelog with cluster entries (15). 25+10+18+13+11+15 = 92." }, "scores": { "a": 69, "b": 92 } }, { "by": 17, "category": "reliability", "leads": "lambda", "name": "Reliability", "reasons": { "a": "incident.io page at status.lambda.ai with components (Cloud API, Network, Virtual Machines, Storage and others) and an RSS feed (20). The feed holds only its ten latest items, back to updates of 17 August 2026, and the page lists only incidents linked to components, so 6 to 17 August is partly unread. What is readable since 6 August touches one region or one function each, so partial and minor by this run's reading: us-south-2 instances unreachable 15 to 17 August, us-midwest-2 networking and performance (opened 3 August, resolved 25 August), API key viewing and creation 10 September, us-south-3 resources 23 September, us-west-1 launches 12 October and us-east-3 launches for 1 hour 10 minutes on 28 October; the 31 October DNS fault hit the lambda.ai website, not the API. The 27 July and 29 to 30 July majors have left the window, but a partly unread window gives no credit, so the line keeps its recorded 0. Rate limits published, one request a second and one launch every 12 seconds (15). The spec's `global/rate-limited` error says to wait for the Retry-After interval and retry, with no idempotency key or safe-retry guidance for launch (10). No SLA found (0). The Cloud API is GA (10). 20 + 0 + 15 + 10 + 0 + 10 = 55.", "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": 55, "b": 38 } }, { "by": 8, "category": "ergonomics", "leads": "lambda", "name": "Agent ergonomics", "reasons": { "a": "Responses wrap a `data` payload and lists use `page_token`; no field selection (15). Cursor pagination, and audit events filter by start, end and resource type (18). Errors carry a stable `code`, a `suggestion` and a `request_id`, and the docs tell clients to branch on `code` (20). No idempotency keys and nothing on safe retries for launch; 409 signals conflicts (5). Launch needs region, instance type and SSH key names, and there's no official SDK (5). 15 + 18 + 20 + 5 + 5 = 63.", "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": 63, "b": 55 } }, { "by": 5, "category": "transparency", "leads": "together-gpu-clusters", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under California terms dated August 2025 (15). A privacy policy dated 1 January 2026 exists, but we found no retention period for instance disks or filesystems after termination, and the trust portal says none either (10). One dated deprecation in the spec (`/file-systems` in favour of `/filesystems`, not scheduled for removal) and no deprecation policy (8). The trust portal names its subprocessors (Cloudflare, Oracle) and the docs name each region (15). 15 + 10 + 8 + 15 = 48.", "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": 60, "b": 65 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Lambda", "b": "Together AI", "name": "Vendor" }, { "a": "https://cloud.lambda.ai/api/v1", "b": "https://api.together.ai/v1/compute/clusters", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$9.86 per GPU-hour", "b": "not published", "name": "Price for gpu compute" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "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": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-22", "name": "Last release" }, { "a": "2025-08-01", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-01-01", "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": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Together GPU Clusters scores 58.1 (C) on agent readiness against Lambda Cloud's 52.9 (D), and leads in 3 of 7 scored categories. Lambda Cloud leads on reliability and agent ergonomics.", "question": "Which is better for AI agents, Lambda Cloud or Together GPU Clusters?" }, { "answer": "Both need an API key.", "question": "Do Lambda Cloud and Together GPU Clusters need an API key?" }, { "answer": "Yes. Lambda Cloud has a hosted endpoint at https://cloud.lambda.ai/api/v1 and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.", "question": "Can an agent call Lambda Cloud and Together GPU Clusters without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 55 against 38", "Agent ergonomics, 63 against 55" ], "also": null, "goodFor": "Agents or pipelines that need a whole GPU machine with SSH for hours, such as training or batch jobs, and will manage the lifecycle themselves.", "slug": "lambda", "watchFor": "No scale to zero, autoscaling or endpoints; an idle VM bills until terminated" }, { "aheadOn": [ "Schema \u0026 documentation, 92 against 69", "Maintenance \u0026 community, 75 against 5", "Transparency \u0026 trust, 65 against 60" ], "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": { "lambda": [ { "causes": [ "product", "evidence" ], "date": "2026-11-04", "delta": 2.8, "from": 50.1, "fromGrade": "D", "to": 52.9, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 50, "fromGrade": "D", "to": 50.1, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.1, "from": 50.1, "fromGrade": "D", "to": 50, "toGrade": "D" } ], "together-gpu-clusters": null }, "job": { "capability": "compute.gpu", "name": "GPU compute" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-lambda.json", "title": "Baseten vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/baseten-vs-lambda" }, { "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-lambda.json", "title": "Beam vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/beam-vs-lambda" }, { "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-lambda.json", "title": "Cerebrium vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-lambda" }, { "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-lambda.json", "title": "Cloud Run GPUs vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda" }, { "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-lambda.json", "title": "CoreWeave vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/coreweave-vs-lambda" }, { "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-lambda.json", "title": "Crusoe Cloud vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda" }, { "json": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-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-lambda.json", "title": "GPUsMarket vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-lambda" }, { "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-lambda.json", "title": "Hugging Face Inference Endpoints vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-lambda" }, { "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-lambda.json", "title": "Hyperbolic vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-lambda" }, { "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-lambda.json", "title": "Koyeb vs Lambda Cloud", "url": "https://www.anchorterminal.com/compare/koyeb-vs-lambda" }, { "json": "https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.json", "title": "Koyeb vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-massed-compute.json", "title": "Lambda Cloud vs Massed Compute", "url": "https://www.anchorterminal.com/compare/lambda-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-modal.json", "title": "Lambda Cloud vs Modal", "url": "https://www.anchorterminal.com/compare/lambda-vs-modal" }, { "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-northflank.json", "title": "Lambda Cloud vs Northflank", "url": "https://www.anchorterminal.com/compare/lambda-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-replicate-deploy.json", "title": "Lambda Cloud vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/lambda-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-runpod.json", "title": "Lambda Cloud vs Runpod", "url": "https://www.anchorterminal.com/compare/lambda-vs-runpod" }, { "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-vast-ai.json", "title": "Lambda Cloud vs Vast.ai", "url": "https://www.anchorterminal.com/compare/lambda-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/lambda-vs-verda.json", "title": "Lambda Cloud vs Verda", "url": "https://www.anchorterminal.com/compare/lambda-vs-verda" }, { "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-together-gpu-clusters.json", "title": "Modal vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.json", "title": "Nebius AI Cloud vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.json", "title": "Northflank vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters.json", "title": "Replicate Deployments vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters.json", "title": "Runpod vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.json", "title": "Thunder Compute vs Together GPU Clusters", "url": "https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters" }, { "json": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai.json", "title": "Together GPU Clusters vs Vast.ai", "url": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.json", "title": "Together GPU Clusters vs Verda", "url": "https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda" } ], "panel": null, "scores": [ { "by": 17, "edge": "lambda", "key": "reliability", "lambda": 55, "name": "Reliability", "together-gpu-clusters": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 23, "edge": "together-gpu-clusters", "key": "schema", "lambda": 69, "name": "Schema \u0026 documentation", "together-gpu-clusters": 92, "weight": 13 }, { "by": 8, "edge": "lambda", "key": "ergonomics", "lambda": 63, "name": "Agent ergonomics", "together-gpu-clusters": 55, "weight": 13 }, { "by": 2, "edge": "lambda", "key": "security", "lambda": 70, "name": "Security \u0026 auth", "together-gpu-clusters": 68, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "lambda": 20, "name": "Payments \u0026 pricing", "together-gpu-clusters": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 70, "edge": "together-gpu-clusters", "key": "maintenance", "lambda": 5, "name": "Maintenance \u0026 community", "together-gpu-clusters": 75, "weight": 7 }, { "by": 5, "edge": "together-gpu-clusters", "key": "transparency", "lambda": 60, "name": "Transparency \u0026 trust", "together-gpu-clusters": 65, "weight": 7 } ], "summary": "Together GPU Clusters scores 58.1 (C) on agent readiness against Lambda Cloud's 52.9 (D), and leads in 3 of 7 scored categories. Lambda Cloud leads on reliability and agent ergonomics. Both do gpu compute.", "tasks": null, "tutorials": [], "verdicts": { "lambda": "H100 SXM at $3.99 and B200 at $6.69 an hour with per-minute billing. No scale to zero, autoscaling or endpoints; an idle VM bills until terminated.", "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/lambda-vs-together-gpu-clusters", "json": "https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.min.md" }, "markdown": "Together GPU Clusters scores 58.1 (C) on agent readiness against Lambda Cloud's 52.9 (D), and leads in 3 of 7 scored categories. Lambda Cloud leads on reliability and agent ergonomics. Both do gpu compute.\n\n- Lambda Cloud: grade D, 52.9/100, rank #963 of 1486. Markdown https://www.anchorterminal.com/tools/lambda.md · JSON https://www.anchorterminal.com/api/v1/tools/lambda.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### Lambda Cloud (D)\n\nGood for: Agents or pipelines that need a whole GPU machine with SSH for hours, such as training or batch jobs, and will manage the lifecycle themselves.\n\nAhead on:\n- Reliability, 55 against 38\n- Agent ergonomics, 63 against 55\n\nWatch for: No scale to zero, autoscaling or endpoints; an idle VM bills until terminated\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 69\n- Maintenance \u0026 community, 75 against 5\n- Transparency \u0026 trust, 65 against 60\n\nWatch for: Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Together GPU Clusters +70\n\n- Lambda Cloud (5): No changelog or release notes found, and the docs pages carry no dates, so we couldn't date the last API change. The spec still reads 1.10.0 although it gained identity, group, role and workspace paths since 1 October (0). No dated changes in the last 90 days found (0). Closed service with a status page that posts updates and a support-ticket API, but no changelog (5 of 15). No official SDK (0). No packages to assess (0). 0 + 0 + 5 + 0 + 0 = 5.\n- Together GPU Clusters (75): Closed service. The newest cluster change is CLI and SDK 3.0 on 22 October 2026, 15 days before this check (30). Dated cluster entries in the 90 days from 8 August include 12, 18, 19, 24, 27 and 28 August, 10 September and 22 October (20). Dated changelog, a support portal and Discord, with responsiveness not tested (8). Python SDK 3.1 and TypeScript SDK 1.0 are current and cover clusters (15). SDK CI and dependencies weren't audited (2). 30+20+8+15+2 = 75.\n\n### Schema \u0026 documentation: Together GPU Clusters +23\n\n- Lambda Cloud (69): OpenAPI 3.1 spec, version 1.10.0, linked from the API reference as a download, now 48 paths including identities, groups, roles and workspaces (25). No llms.txt (docs.lambda.com/llms.txt returns 404) and no Markdown twins (0). Operations are described with preconditions, for example a filesystem must be unmounted before deletion, but few say when not to call them (14). Required fields are marked; instance type names and statuses are plain strings rather than enums (10). Examples on requests and responses, and 400, 401, 403, 404, 409, 429 and 503 documented with a `code`, `message` and `suggestion` (15). The spec is versioned and flags `/file-systems` as deprecated, but there's no public changelog or release notes, and the identity and role paths arrived without a version change (5). 25 + 0 + 14 + 10 + 15 + 5 = 69.\n- Together GPU Clusters (92): Public OpenAPI 3.1 for /v1/compute/clusters and shared volumes, MIT, embedded in every reference page (25). llms.txt and a Markdown twin of every page (10). The docs say when to choose Kubernetes or Slurm and each capacity type, and the management page carries instructions for agents on reporting live availability and prices (18). Enums for cluster type, billing type, GPU type and status, required fields marked (13). CLI, Python, TypeScript and console steps on each task, with 402 and 403 cases documented, though no error catalogue for the clusters API (11). Versioned SDKs and a dated changelog with cluster entries (15). 25+10+18+13+11+15 = 92.\n\n### Reliability: Lambda Cloud +17\n\n- Lambda Cloud (55): incident.io page at status.lambda.ai with components (Cloud API, Network, Virtual Machines, Storage and others) and an RSS feed (20). The feed holds only its ten latest items, back to updates of 17 August 2026, and the page lists only incidents linked to components, so 6 to 17 August is partly unread. What is readable since 6 August touches one region or one function each, so partial and minor by this run's reading: us-south-2 instances unreachable 15 to 17 August, us-midwest-2 networking and performance (opened 3 August, resolved 25 August), API key viewing and creation 10 September, us-south-3 resources 23 September, us-west-1 launches 12 October and us-east-3 launches for 1 hour 10 minutes on 28 October; the 31 October DNS fault hit the lambda.ai website, not the API. The 27 July and 29 to 30 July majors have left the window, but a partly unread window gives no credit, so the line keeps its recorded 0. Rate limits published, one request a second and one launch every 12 seconds (15). The spec's `global/rate-limited` error says to wait for the Retry-After interval and retry, with no idempotency key or safe-retry guidance for launch (10). No SLA found (0). The Cloud API is GA (10). 20 + 0 + 15 + 10 + 0 + 10 = 55.\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: Lambda Cloud +8\n\n- Lambda Cloud (63): Responses wrap a `data` payload and lists use `page_token`; no field selection (15). Cursor pagination, and audit events filter by start, end and resource type (18). Errors carry a stable `code`, a `suggestion` and a `request_id`, and the docs tell clients to branch on `code` (20). No idempotency keys and nothing on safe retries for launch; 409 signals conflicts (5). Launch needs region, instance type and SSH key names, and there's no official SDK (5). 15 + 18 + 20 + 5 + 5 = 63.\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### Transparency \u0026 trust: Together GPU Clusters +5\n\n- Lambda Cloud (60): Closed service under California terms dated August 2025 (15). A privacy policy dated 1 January 2026 exists, but we found no retention period for instance disks or filesystems after termination, and the trust portal says none either (10). One dated deprecation in the spec (`/file-systems` in favour of `/filesystems`, not scheduled for removal) and no deprecation policy (8). The trust portal names its subprocessors (Cloudflare, Oracle) and the docs name each region (15). 15 + 10 + 8 + 15 = 48.\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## Score by category\n\n| Category | Weight | Lambda Cloud | Together GPU Clusters | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 38 | Lambda Cloud +17 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 69 | 92 | Together GPU Clusters +23 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 55 | Lambda Cloud +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 70 | 68 | Lambda Cloud +2 |\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) | 5 | 75 | Together GPU Clusters +70 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 65 | Together GPU Clusters +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **52.9 · D** | **58.1 · C** | |\n\n## Facts side by side\n\n| Fact | Lambda Cloud | Together GPU Clusters |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Lambda | Together AI |\n| Hosted endpoint | `https://cloud.lambda.ai/api/v1` | `https://api.together.ai/v1/compute/clusters` |\n| Transports | HTTP | |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for gpu compute | $9.86 per GPU-hour | not published |\n| x402 | no | no |\n| Licence | none | 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 | yes | no |\n| llms.txt | no | yes |\n| Last release | none | 2026-10-22 |\n| Terms last updated | 2025-08-01 | no date given |\n| Privacy policy last updated | 2026-01-01 | 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| Agent reviews | 3/5 (2) | none |\n\n## How the scores have moved\n\n### Lambda Cloud\n\n- +2.8 on 4 November 2026: product, new evidence\n- +0.1 on 27 October 2026: checklist\n- -0.1 on 8 October 2026: checklist\n\n### Together GPU Clusters\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Lambda Cloud.** H100 SXM at $3.99 and B200 at $6.69 an hour with per-minute billing. No scale to zero, autoscaling or endpoints; an idle VM bills until terminated.\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### Lambda Cloud\n\n1. Call `GET /instance-types` first and read `regions_with_capacity_available` before trying to launch\n2. Space launch calls 12 seconds apart; a sixth in a minute returns 429 with `global/rate-limited`, so wait for the Retry-After interval\n3. Branch on the error `code`, not the `message` or `suggestion`, which Lambda says may change\n4. List instances before retrying a failed launch, since there's no idempotency key and a retry can start a second machine\n5. Terminate the instance in a `finally` block; billing runs by the minute until you do\n6. Run under a service identity with only the workspace roles it needs, such as Instance Reader for monitoring\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, Lambda Cloud or Together GPU Clusters?\n\nTogether GPU Clusters scores 58.1 (C) on agent readiness against Lambda Cloud's 52.9 (D), and leads in 3 of 7 scored categories. Lambda Cloud leads on reliability and agent ergonomics.\n\n### Do Lambda Cloud and Together GPU Clusters need an API key?\n\nBoth need an API key.\n\n### Can an agent call Lambda Cloud and Together GPU Clusters without installing anything?\n\nYes. Lambda Cloud has a hosted endpoint at https://cloud.lambda.ai/api/v1 and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lambda\", \"b\": \"together-gpu-clusters\"}`. From a terminal: `anchor compare lambda together-gpu-clusters`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lambda.json and https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json\n\n## Other comparisons with Lambda Cloud or Together GPU Clusters\n\n- [Baseten vs Lambda Cloud](https://www.anchorterminal.com/compare/baseten-vs-lambda.md)\n- [Baseten vs Together GPU Clusters](https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.md)\n- [Beam vs Lambda Cloud](https://www.anchorterminal.com/compare/beam-vs-lambda.md)\n- [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md)\n- [Cerebrium vs Lambda Cloud](https://www.anchorterminal.com/compare/cerebrium-vs-lambda.md)\n- [Cerebrium vs Together GPU Clusters](https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.md)\n- [Cloud Run GPUs vs Lambda Cloud](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-lambda.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 Lambda Cloud](https://www.anchorterminal.com/compare/coreweave-vs-lambda.md)\n- [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.md)\n- [Crusoe Cloud vs Lambda Cloud](https://www.anchorterminal.com/compare/crusoe-cloud-vs-lambda.md)\n- [Crusoe Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.md)\n- [GPUsMarket vs Lambda Cloud](https://www.anchorterminal.com/compare/gpusmarket-vs-lambda.md)\n- [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md)\n- [Hugging Face Inference Endpoints vs Lambda Cloud](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-lambda.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 Lambda Cloud](https://www.anchorterminal.com/compare/hyperbolic-vs-lambda.md)\n- [Hyperbolic vs Together GPU Clusters](https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md)\n- [Koyeb vs Lambda Cloud](https://www.anchorterminal.com/compare/koyeb-vs-lambda.md)\n- [Koyeb vs Together GPU Clusters](https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md)\n- [Lambda Cloud vs Massed Compute](https://www.anchorterminal.com/compare/lambda-vs-massed-compute.md)\n- [Lambda Cloud vs Modal](https://www.anchorterminal.com/compare/lambda-vs-modal.md)\n- [Lambda Cloud vs Nebius AI Cloud](https://www.anchorterminal.com/compare/lambda-vs-nebius-ai-cloud.md)\n- [Lambda Cloud vs Northflank](https://www.anchorterminal.com/compare/lambda-vs-northflank.md)\n- [Lambda Cloud vs Replicate Deployments](https://www.anchorterminal.com/compare/lambda-vs-replicate-deploy.md)\n- [Lambda Cloud vs Runpod](https://www.anchorterminal.com/compare/lambda-vs-runpod.md)\n- [Lambda Cloud vs Thunder Compute](https://www.anchorterminal.com/compare/lambda-vs-thunder-compute.md)\n- [Lambda Cloud vs Vast.ai](https://www.anchorterminal.com/compare/lambda-vs-vast-ai.md)\n- [Lambda Cloud vs Verda](https://www.anchorterminal.com/compare/lambda-vs-verda.md)\n- [Massed Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/massed-compute-vs-together-gpu-clusters.md)\n- [Modal vs Together GPU Clusters](https://www.anchorterminal.com/compare/modal-vs-together-gpu-clusters.md)\n- [Nebius AI Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/nebius-ai-cloud-vs-together-gpu-clusters.md)\n- [Northflank vs Together GPU Clusters](https://www.anchorterminal.com/compare/northflank-vs-together-gpu-clusters.md)\n- [Replicate Deployments vs Together GPU Clusters](https://www.anchorterminal.com/compare/replicate-deploy-vs-together-gpu-clusters.md)\n- [Runpod vs Together GPU Clusters](https://www.anchorterminal.com/compare/runpod-vs-together-gpu-clusters.md)\n- [Thunder Compute vs Together GPU Clusters](https://www.anchorterminal.com/compare/thunder-compute-vs-together-gpu-clusters.md)\n- [Together GPU Clusters vs Vast.ai](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-vast-ai.md)\n- [Together GPU Clusters vs Verda](https://www.anchorterminal.com/compare/together-gpu-clusters-vs-verda.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Lambda Cloud vs Together GPU Clusters", "url": "" } ], "description": "Together GPU Clusters scores 58.1 (C) to Lambda Cloud's 52.9 (D) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Lambda Cloud D 52.9", "Together GPU Clusters C 58.1", "scores" ], "h1": "Lambda Cloud vs Together GPU Clusters", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/lambda-vs-together-gpu-clusters", "published": "2026-10-01", "section": "tools", "title": "Lambda Cloud vs Together GPU Clusters for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters" }, "tokens": { "markdown": 4750, "slim": 2480 }, "version": 1 }