{ "data": { "a": { "slug": "hyperbolic", "name": "Hyperbolic", "vendor": "Hyperbolic Labs, Inc.", "vendorUrl": "https://www.hyperbolic.ai", "kind": "http-api", "category": "gpu-compute", "summary": "Hyperbolic is a GPU cloud from Hyperbolic Labs that rents H100, H200 and B200 virtual machines and bare-metal nodes by the hour, with reserved terms and private clusters. Agents use its REST API with an API key.", "url": "https://www.anchorterminal.com/tools/hyperbolic", "markdownUrl": "https://www.anchorterminal.com/tools/hyperbolic.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/hyperbolic.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/hyperbolic.json", "dns": "hyperbolic.grade.anchorterminal.com", "license": "Proprietary service under Hyperbolic's Terms of Service. The unmaintained hyperbolic-mcp repository on GitHub is MIT", "transports": [ "http" ], "remoteUrl": "https://api.hyperbolic.ai", "packages": [], "auth": "api-key", "authNotes": "Self-serve. A signed-in user creates an API key in the console's settings, and the secret is shown once. Requests send it as `Authorization: Bearer \u003capi-key\u003e`. An account can hold any number of keys and revoke any of them. Keys created inside an Organisation belong to it and are attributed to the member who made them. Members revoke their own keys and admins revoke any. No scopes, read-only keys or expiry were found in the reviewed documentation.", "pricing": "usage", "pricingNotes": "Prepaid credits, minimum purchase $5 through Stripe, 1 to 1 with dollars and with no expiry. A new account is on the free tier and cannot rent GPUs or storage until it has deposited $5 once. No trial was found, apart from credit codes handed out at events. On-demand rentals bill hourly from the moment an instance is ready, and the balance must cover one hour of all running instances. On 8 October 2026 the marketplace page gave a starting price of $3.19 a GPU-hour. Reserved terms of 7, 14 and 30 days take 1, 3 and 5 per cent off and are paid up front. Private Cloud is by contract (https://www.hyperbolic.ai/docs/on-demand/pricing).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs corpus or the OpenAPI document for the GPU API. The archived HyperbolicLabs/hyperbolic-x402 repository covered chat completions on a separate host, not GPU rentals (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://www.hyperbolic.ai/docs/overview/overview", "llmsTxt": "https://www.hyperbolic.ai/docs/llms.txt", "openapi": "https://api.hyperbolic.ai/v2/openapi.json", "capabilities": [ "compute.gpu" ], "tags": [ "hosted", "usage-priced", "openapi", "llms-txt", "api-key", "bare-metal", "status-page", "prepaid" ], "lastRelease": "2026-10-05", "graded": true, "anchor": { "graded": true, "score": 38.7, "grade": "E", "agentReady": false, "rank": 1335, "ranked": true, "rankOf": 1486, "categoryRank": 22, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 55, "maintenance": 39, "payments": 15, "reliability": 25, "schema": 52, "security": 48, "transparency": 64 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -3, "negativeNotes": [ "2026-10-05, removing the `roles` list from the `GET /v2/users/me` response and changing timestamps to RFC 3339 on the v2 API. Both are recorded in the changelog entry for the week they shipped, and no advance notice was found. Documented, so 3 points (https://www.hyperbolic.ai/docs/changelog)." ], "verdict": "Hyperbolic's docs carry llms.txt, Markdown pages and a dated 1 March 2027 end for legacy paths, and billing starts only once an instance is ready. API keys carry no scopes and can delete the account, rental creation has no idempotency key, no 429 guidance is documented, and renting needs a browser signup and a $5 deposit.", "bestFor": "Agents that rent whole H100, H200 or B200 machines or multi-node clusters for training and batch work and that have a funded account.", "strengths": [ "Deprecated paths answer with a `Sunset` header and a stated end date of 1 March 2027, and each names its replacement", "Docs index at `/docs/llms.txt`, every page as Markdown and the whole corpus in `llms-full.txt` (188 KB)", "Billing starts only when an instance is ready, and instances that fail to provision within about 3 hours are not charged, per the pricing docs", "The security page asks for vulnerability reports by email and states a 48-hour acknowledgement", "A rental needs only `rentalType` and `gpuCount`, with defaults for region, GPU type and SSH key" ], "weaknesses": [ "API keys carry no scopes or expiry in the reviewed documentation, and the same key can call `DELETE /v2/users/me`", "`POST /v2/on-demand/rentals` has no idempotency key, so a retried call can start a second billed rental", "No 429 response, `Retry-After` header or backoff guidance was found in the docs", "A free-tier account cannot rent GPUs or storage. Renting needs a one-time deposit of at least $5 through Stripe", "The Terms of Service describe a marketplace in which uptime is between buyer and supplier, while the docs state a 99.5 per cent uptime SLA", "No official SDK or CLI for the v2 API was found. The vendor's MCP repository last changed in May 2025 and calls the legacy v1 marketplace paths" ], "agentNotes": [ "Check current GPU configurations and hourly prices before renting. The docs point to the console for rates, and the marketplace page gave $3.19 a GPU-hour on 8 October 2026.", "Send `rentalType` and `gpuCount` to `POST /v2/on-demand/rentals`. Region defaults to `us-central-1` and GPU type to `h100`, so set both from the options list.", "List active rentals before retrying a failed create call. There is no idempotency key and every ready rental bills hourly.", "Save an SSH public key with `POST /v2/ssh-keys` before renting. Without `sshPublicKeyIds` the newest saved key is attached.", "Do not create reserved rentals unless asked. They are paid in full up front and cannot be terminated early." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 38.7 } ], "editorialScores": { "ergonomics": 55, "maintenance": 39, "payments": 15, "reliability": 25, "schema": 52, "security": 48, "transparency": 45 }, "provenanceScore": 82, "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 -X POST https://api.hyperbolic.ai/v2/ssh-keys -H \"Authorization: Bearer $HYPERBOLIC_API_KEY\" -H \"Content-Type: application/json\" -d \"{\\\"publicKey\\\": \\\"$(cat ~/.ssh/id_ed25519.pub)\\\", \\\"name\\\": \\\"Work laptop\\\"}\"" }, "letme": { "capability": "https://letme.dev/compute.gpu", "tool": "https://letme.dev/hyperbolic" }, "area": "models", "unitPrices": [ { "item": "H100 SXM5 80 GB virtual machine, on-demand", "unit": "gpu-hour", "usd": 3.19, "note": "Starting price on the marketplace page on 8 October 2026. Reserved terms take 1 to 5 per cent off" } ], "provenance": { "legalEntity": "Hyperbolic Labs, Inc.", "domain": "hyperbolic.ai", "domainRegistered": "2021-10-11", "endpointOnVendorDomain": true, "terms": "https://www.hyperbolic.ai/terms", "privacy": "https://www.hyperbolic.ai/privacy", "statusPage": "https://status.hyperbolic.ai", "changelog": "https://www.hyperbolic.ai/docs/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Terms of Service, last updated 24 March 2025, name Hyperbolic Labs, Inc. as owner and operator of the platform, apply California law and set AAA arbitration. They cover the website and all services, and no separate API or cloud agreement was found.", "The Privacy Policy is effective 3 June 2024 and names Hyperbolic Labs, Inc. One clause on business transfers names Babylon three times where the company's own name would be expected.", "The API answers at api.hyperbolic.ai, a subdomain of the vendor domain, and on the legacy host api.hyperbolic.xyz.", "https://www.hyperbolic.ai/.well-known/security.txt answered 404. The docs ask for vulnerability reports by email to support@hyperbolic.ai.", "RDAP for hyperbolic.ai gives a registration date of 2021-10-11." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/hyperbolic.json", "live": { "slug": "hyperbolic", "probe": { "target": "https://api.hyperbolic.ai", "method": "get", "lastAt": "2026-11-07T18:20:31.396131453Z", "lastOk": true, "lastStatus": 200, "lastMs": 606, "authRequired": false, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 548, "p95ms24h": 663, "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": 249 }, { "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.hyperbolic.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:55.787305505Z" }, "securityTxt": { "url": "https://hyperbolic.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:48.055957691Z" }, "llmsTxt": { "url": "https://www.hyperbolic.ai/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:43.902264652Z" }, "domain": { "domain": "hyperbolic.ai", "registered": "2021-10-11", "source": "https://rdap.identitydigital.services/rdap/domain/hyperbolic.ai", "checkedAt": "2026-11-01T14:21:49.876675266Z" }, "pages": [ { "url": "https://www.hyperbolic.ai/docs/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:29:58.147501999Z", "changedAt": "2026-11-06T13:50:40.528326876Z", "fingerprint": "1a10dd67c657" }, { "url": "https://www.hyperbolic.ai/docs/on-demand/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:30:00.509963551Z", "changedAt": "2026-11-06T13:50:42.957918679Z", "fingerprint": "42de0112476b" }, { "url": "https://www.hyperbolic.ai/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:30:02.429568985Z", "changedAt": "2026-11-06T13:50:44.72967179Z", "fingerprint": "c7a0abc04871" }, { "url": "https://www.hyperbolic.ai/terms", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:30:04.1682072Z", "changedAt": "2026-11-06T13:50:46.96264626Z", "fingerprint": "08db2ae53bbf" } ], "updatedAt": "2026-11-07T18:20:31.396131453Z" } }, "answer": "Together GPU Clusters scores 58.1 (C) on agent readiness against Hyperbolic's 38.7 (E), and leads in 6 of 7 scored categories.", "b": { "slug": "together-gpu-clusters", "name": "Together GPU Clusters", "vendor": "Together AI", "vendorUrl": "https://www.together.ai", "kind": "http-api", "category": "gpu-compute", "summary": "Together GPU Clusters rents multi-node NVIDIA H100, H200, B200 and B300 clusters with InfiniBand and shared storage, run as Kubernetes or Slurm, by the GPU-hour. Clusters are created and scaled from the console, the tg CLI, SDKs or REST API.", "url": "https://www.anchorterminal.com/tools/together-gpu-clusters", "markdownUrl": "https://www.anchorterminal.com/tools/together-gpu-clusters.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/together-gpu-clusters.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json", "dns": "together-gpu-clusters.grade.anchorterminal.com", "repo": "https://github.com/togethercomputer/together-py", "license": "Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT", "transports": [], "remoteUrl": "https://api.together.ai/v1/compute/clusters", "packages": [ { "registry": "pypi", "name": "together" }, { "registry": "npm", "name": "together-ai" } ], "auth": "api-key", "authNotes": "Bearer `TOGETHER_API_KEY`, scoped to a project, revocable and optionally expiring, the same keys as Together's other APIs. Only a project admin's key returns the cluster's admin kubeconfig. Team members can reach the Kubernetes API through OIDC with their own identity provider, and SSH uses OIDC or uploaded keys.", "pricing": "usage", "pricingNotes": "On-demand from $3.99 per GPU-hour (H100) to $9.99 (B300); reserved 3 to 180 days from $3.19 to $7.99; preemptible (preview) from $1.99. Storage per GiB-month. No ingress or egress fees. Reservations are prepaid and non-refundable, and creation needs enough credit to cover them.", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the GPU clusters docs, billing pages or OpenAPI document (checked 2026-11-06). An exhausted balance returns 402 to scale requests with no payment requirements.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.together.ai/docs/gpu-clusters-overview", "llmsTxt": "https://docs.together.ai/llms.txt", "openapi": "https://github.com/togethercomputer/openapi", "capabilities": [ "compute.gpu", "compute.containers", "compute.batch" ], "tags": [ "hosted", "official", "usage", "prepaid", "openapi", "llms-txt", "kubernetes", "slurm", "python", "typescript", "cli", "h100", "b200" ], "lastRelease": "2026-10-22", "graded": true, "anchor": { "graded": true, "score": 58.1, "grade": "C", "agentReady": false, "rank": 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": 40, "category": "schema", "leads": "together-gpu-clusters", "name": "Schema \u0026 documentation", "reasons": { "a": "Readings are per the 8 October check, not re-read on 4 November 2026. Contract line 25 to 0. The OpenAPI document was read from the API host (api.hyperbolic.ai/v2/openapi.json, the product's own endpoint) and from a copy under /docs/api-reference/ with no recorded docs page that shows or links it. The first reading is struck, and a contract on a now-paused host with no recorded visible link is struck too (jambonz, stable-audio). `llms.txt`, every docs page as Markdown and a 188 KB `llms-full.txt` (10). Of the 34 current operations, 17 have a description that only repeats the summary. The rest state behaviour, limits and named error cases, and every deprecated operation names its replacement (10 of 20). Required fields, 89 enums, numeric bounds and a `oneOf` for new or existing storage volumes, but rental IDs accept an integer or a string (12 of 15). Five error schemas with examples and 400, 401, 403 and 500 on every operation. No request body has an example and no 429 is listed (8 of 15). Versioned in the path with a dated changelog and RSS feed, which held one entry (12 of 15). 0 + 10 + 10 + 12 + 8 + 12 = 52.", "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": 52, "b": 92 } }, { "by": 36, "category": "maintenance", "leads": "together-gpu-clusters", "name": "Maintenance \u0026 community", "reasons": { "a": "Readings are per the 8 October check, not re-read on 4 November 2026. The newest changelog entry is for the week of 5 October 2026, 30 days before today (30); it drops to 20 after 4 November unless a newer entry appears. It was the only dated entry on the changelog and its RSS feed, so the three-entry test is not met (0 of 20). A public changelog with RSS, in-app chat and email support with stated hours of Monday to Friday, 06:00 to 17:00 Pacific Time (9 of 15). No current official SDK for the v2 API. The vendor's MCP repository still ends at its 21 May 2025 commit (clone, 4 November) and targets legacy v1 paths (0 of 15). Package health 3 to 0. The partial rested on the spec served by the API, a struck reading, and there is no client package to assess. 30 + 0 + 9 + 0 + 0 = 39.", "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": 39, "b": 75 } }, { "by": 20, "category": "security", "leads": "together-gpu-clusters", "name": "Security \u0026 auth", "reasons": { "a": "Readings are per the 8 October check, not re-read on 4 November 2026. Plain API keys sent as a Bearer header, shown once, revocable, any number per account, and attributed to their creator inside an Organisation. No scopes or expiry found, and no secret in a URL (20 of 30). No read-only key and no confirmation step. A key can rent and terminate machines and can call `DELETE /v2/users/me`. Organisation members cannot deposit funds or see billing history (4 of 20). Responses are infrastructure metadata (10). Key lists show each key's creator and revocation time, and rental and transaction histories exist. No audit log was found for self-serve accounts (4 of 15). Programme 9 to 10. The docs ask for vulnerability reports by email with a 48-hour acknowledgement and claim a completed SOC 2 Type I audit with Type II under way, reports under NDA. A disclosure route with a stated acknowledgement time is 10; no security.txt or bug bounty, and the trust centre is drawn by script. 20 + 4 + 10 + 4 + 10 = 48.", "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": 48, "b": 68 } }, { "by": 13, "category": "reliability", "leads": "together-gpu-clusters", "name": "Reliability", "reasons": { "a": "Graded on the hosted lines for the REST API. Hyperbolic's Terms of Service (24 March 2025) bar spiders, robots and scrapers from downloading data from any web page in the Services, which cover the website, so hyperbolic.ai pages and the status page keep their 8 October readings, not re-read on 4 November 2026. Status page at status.hyperbolic.ai on UptimeRobot. The page draws its monitors and history by script from `/api/`, a path its robots.txt closes, so no component was ever read, and a status-page line with no readable component scores 0, as for fonoa, n8n and windmill (was 20). The incident record was never read either (5, unreadable history). Rate limits appear as numbers only on the plan cards in the docs, 60 requests a minute on the free tier and 600 on the pro tier, and the terms let Hyperbolic change limits without notice (10 of 15). No 429 response, `Retry-After` or backoff guidance in the docs, and no idempotency key on rental creation (0). SLA 7 to 0. The docs state a 99.5 per cent uptime figure for On-Demand and Reserved with credits reviewed case by case, and the Terms of Service disclaim uptime and any duty to give credits. A figure with discretionary credits and no SLA document isn't an SLA (manatal). The v2 API is not marked beta (10). 0 + 5 + 10 + 0 + 0 + 10 = 25.", "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": 25, "b": 38 } }, { "by": 5, "category": "payments", "leads": "together-gpu-clusters", "name": "Payments \u0026 pricing", "reasons": { "a": "Readings are per the 8 October check, not re-read on 4 November 2026. No x402, MPP or L402 on the GPU API. The vendor's archived x402 repository covered chat completions on another host (0). The marketplace page states a starting price of $3.19 a GPU-hour. There is no public price table and the docs point to the console. The 8 October reading of hourly prices from an open API endpoint is struck (a product endpoint), so the line rests on the marketplace figure and keeps its partial value (15 of 20). A free-tier account cannot rent anything. Renting needs a $5 deposit through Stripe, and the only free credit found is from event codes (0). Signup, email verification, the deposit and key creation happen in a browser (0). 0 + 15 + 0 + 0 = 15.", "b": "No machine payment protocol (0). Per GPU-hour prices for each capacity type and per GiB-month storage published without a login (20). No free trial, and creation needs credit for the full reservation or a minimum on-demand period (0). Sign-up and credit purchase are browser steps (0). 0+20+0+0 = 20." }, "scores": { "a": 15, "b": 20 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Hyperbolic Labs, Inc.", "b": "Together AI", "name": "Vendor" }, { "a": "https://api.hyperbolic.ai", "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": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Hyperbolic's Terms of Service. The unmaintained hyperbolic-mcp repository on GitHub is MIT", "b": "Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-05", "b": "2026-10-22", "name": "Last release" }, { "a": "2025-03-24", "b": "no date given", "name": "Terms last updated" }, { "a": "no date given", "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": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Together GPU Clusters scores 58.1 (C) on agent readiness against Hyperbolic's 38.7 (E), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Hyperbolic or Together GPU Clusters?" }, { "answer": "Both need an API key.", "question": "Do Hyperbolic and Together GPU Clusters need an API key?" }, { "answer": "Yes. Hyperbolic has a hosted endpoint at https://api.hyperbolic.ai and Together GPU Clusters at https://api.together.ai/v1/compute/clusters.", "question": "Can an agent call Hyperbolic and Together GPU Clusters without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "Agents that rent whole H100, H200 or B200 machines or multi-node clusters for training and batch work and that have a funded account.", "slug": "hyperbolic", "watchFor": "API keys carry no scopes or expiry in the reviewed documentation, and the same key can call `DELETE /v2/users/me`" }, { "aheadOn": [ "Reliability, 38 against 25", "Schema \u0026 documentation, 92 against 52", "Security \u0026 auth, 68 against 48", "Payments \u0026 pricing, 20 against 15", "Maintenance \u0026 community, 75 against 39" ], "also": [ "No incidents deducted, where Hyperbolic loses 3 points for them" ], "goodFor": "Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters.", "slug": "together-gpu-clusters", "watchFor": "Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero" } ], "history": { "hyperbolic": [ { "causes": [ "correction" ], "date": "2026-11-04", "delta": -9.5, "from": 48.2, "fromGrade": "D", "to": 38.7, "toGrade": "E" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 48.1, "fromGrade": "D", "to": 48.2, "toGrade": "D" }, { "causes": [ "time" ], "date": "2026-10-12", "delta": 0.1, "from": 48, "fromGrade": "D", "to": 48.1, "toGrade": "D" } ], "together-gpu-clusters": null }, "job": { "capability": "compute.gpu", "name": "GPU compute" }, "others": [ { "json": "https://www.anchorterminal.com/compare/baseten-vs-hyperbolic.json", "title": "Baseten vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/baseten-vs-hyperbolic" }, { "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-hyperbolic.json", "title": "Beam vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/beam-vs-hyperbolic" }, { "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-hyperbolic.json", "title": "Cerebrium vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/cerebrium-vs-hyperbolic" }, { "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-hyperbolic.json", "title": "Cloud Run GPUs vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hyperbolic" }, { "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-hyperbolic.json", "title": "CoreWeave vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/coreweave-vs-hyperbolic" }, { "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-hyperbolic.json", "title": "Crusoe Cloud vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/crusoe-cloud-vs-hyperbolic" }, { "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-hyperbolic.json", "title": "GPUsMarket vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/gpusmarket-vs-hyperbolic" }, { "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-hyperbolic.json", "title": "Hugging Face Inference Endpoints vs Hyperbolic", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-hyperbolic" }, { "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-koyeb.json", "title": "Hyperbolic vs Koyeb", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-koyeb" }, { "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-massed-compute.json", "title": "Hyperbolic vs Massed Compute", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-modal.json", "title": "Hyperbolic vs Modal", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-modal" }, { "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-northflank.json", "title": "Hyperbolic vs Northflank", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-northflank" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-replicate-deploy.json", "title": "Hyperbolic vs Replicate Deployments", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-replicate-deploy" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-runpod.json", "title": "Hyperbolic vs Runpod", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-runpod" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute.json", "title": "Hyperbolic vs Thunder Compute", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-vast-ai.json", "title": "Hyperbolic vs Vast.ai", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-vast-ai" }, { "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-verda.json", "title": "Hyperbolic vs Verda", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-verda" }, { "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-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-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": 13, "edge": "together-gpu-clusters", "hyperbolic": 25, "key": "reliability", "name": "Reliability", "together-gpu-clusters": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 40, "edge": "together-gpu-clusters", "hyperbolic": 52, "key": "schema", "name": "Schema \u0026 documentation", "together-gpu-clusters": 92, "weight": 13 }, { "by": 0, "edge": "", "hyperbolic": 55, "key": "ergonomics", "name": "Agent ergonomics", "together-gpu-clusters": 55, "weight": 13 }, { "by": 20, "edge": "together-gpu-clusters", "hyperbolic": 48, "key": "security", "name": "Security \u0026 auth", "together-gpu-clusters": 68, "weight": 14 }, { "by": 5, "edge": "together-gpu-clusters", "hyperbolic": 15, "key": "payments", "name": "Payments \u0026 pricing", "together-gpu-clusters": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 36, "edge": "together-gpu-clusters", "hyperbolic": 39, "key": "maintenance", "name": "Maintenance \u0026 community", "together-gpu-clusters": 75, "weight": 7 }, { "by": 1, "edge": "together-gpu-clusters", "hyperbolic": 64, "key": "transparency", "name": "Transparency \u0026 trust", "together-gpu-clusters": 65, "weight": 7 } ], "summary": "Together GPU Clusters scores 58.1 (C) on agent readiness against Hyperbolic's 38.7 (E), and leads in 6 of 7 scored categories. Both do gpu compute.", "tasks": null, "tutorials": [], "verdicts": { "hyperbolic": "Hyperbolic's docs carry llms.txt, Markdown pages and a dated 1 March 2027 end for legacy paths, and billing starts only once an instance is ready. API keys carry no scopes and can delete the account, rental creation has no idempotency key, no 429 guidance is documented, and renting needs a browser signup and a $5 deposit.", "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/hyperbolic-vs-together-gpu-clusters", "json": "https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.min.md" }, "markdown": "Together GPU Clusters scores 58.1 (C) on agent readiness against Hyperbolic's 38.7 (E), and leads in 6 of 7 scored categories. Both do gpu compute.\n\n- Hyperbolic: grade E, 38.7/100, rank #1335 of 1486. Markdown https://www.anchorterminal.com/tools/hyperbolic.md · JSON https://www.anchorterminal.com/api/v1/tools/hyperbolic.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### Hyperbolic (E)\n\nGood for: Agents that rent whole H100, H200 or B200 machines or multi-node clusters for training and batch work and that have a funded account.\n\nWatch for: API keys carry no scopes or expiry in the reviewed documentation, and the same key can call `DELETE /v2/users/me`\n\n### Together GPU Clusters (C)\n\nGood for: Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters.\n\nAhead on:\n- Reliability, 38 against 25\n- Schema \u0026 documentation, 92 against 52\n- Security \u0026 auth, 68 against 48\n- Payments \u0026 pricing, 20 against 15\n- Maintenance \u0026 community, 75 against 39\n\nAlso in its favour:\n- No incidents deducted, where Hyperbolic loses 3 points for them\n\nWatch for: Provisioning takes 10 minutes to an hour, and a cluster can't be paused or scaled to zero\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Together GPU Clusters +40\n\n- Hyperbolic (52): Readings are per the 8 October check, not re-read on 4 November 2026. Contract line 25 to 0. The OpenAPI document was read from the API host (api.hyperbolic.ai/v2/openapi.json, the product's own endpoint) and from a copy under /docs/api-reference/ with no recorded docs page that shows or links it. The first reading is struck, and a contract on a now-paused host with no recorded visible link is struck too (jambonz, stable-audio). `llms.txt`, every docs page as Markdown and a 188 KB `llms-full.txt` (10). Of the 34 current operations, 17 have a description that only repeats the summary. The rest state behaviour, limits and named error cases, and every deprecated operation names its replacement (10 of 20). Required fields, 89 enums, numeric bounds and a `oneOf` for new or existing storage volumes, but rental IDs accept an integer or a string (12 of 15). Five error schemas with examples and 400, 401, 403 and 500 on every operation. No request body has an example and no 429 is listed (8 of 15). Versioned in the path with a dated changelog and RSS feed, which held one entry (12 of 15). 0 + 10 + 10 + 12 + 8 + 12 = 52.\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### Maintenance \u0026 community: Together GPU Clusters +36\n\n- Hyperbolic (39): Readings are per the 8 October check, not re-read on 4 November 2026. The newest changelog entry is for the week of 5 October 2026, 30 days before today (30); it drops to 20 after 4 November unless a newer entry appears. It was the only dated entry on the changelog and its RSS feed, so the three-entry test is not met (0 of 20). A public changelog with RSS, in-app chat and email support with stated hours of Monday to Friday, 06:00 to 17:00 Pacific Time (9 of 15). No current official SDK for the v2 API. The vendor's MCP repository still ends at its 21 May 2025 commit (clone, 4 November) and targets legacy v1 paths (0 of 15). Package health 3 to 0. The partial rested on the spec served by the API, a struck reading, and there is no client package to assess. 30 + 0 + 9 + 0 + 0 = 39.\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### Security \u0026 auth: Together GPU Clusters +20\n\n- Hyperbolic (48): Readings are per the 8 October check, not re-read on 4 November 2026. Plain API keys sent as a Bearer header, shown once, revocable, any number per account, and attributed to their creator inside an Organisation. No scopes or expiry found, and no secret in a URL (20 of 30). No read-only key and no confirmation step. A key can rent and terminate machines and can call `DELETE /v2/users/me`. Organisation members cannot deposit funds or see billing history (4 of 20). Responses are infrastructure metadata (10). Key lists show each key's creator and revocation time, and rental and transaction histories exist. No audit log was found for self-serve accounts (4 of 15). Programme 9 to 10. The docs ask for vulnerability reports by email with a 48-hour acknowledgement and claim a completed SOC 2 Type I audit with Type II under way, reports under NDA. A disclosure route with a stated acknowledgement time is 10; no security.txt or bug bounty, and the trust centre is drawn by script. 20 + 4 + 10 + 4 + 10 = 48.\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### Reliability: Together GPU Clusters +13\n\n- Hyperbolic (25): Graded on the hosted lines for the REST API. Hyperbolic's Terms of Service (24 March 2025) bar spiders, robots and scrapers from downloading data from any web page in the Services, which cover the website, so hyperbolic.ai pages and the status page keep their 8 October readings, not re-read on 4 November 2026. Status page at status.hyperbolic.ai on UptimeRobot. The page draws its monitors and history by script from `/api/`, a path its robots.txt closes, so no component was ever read, and a status-page line with no readable component scores 0, as for fonoa, n8n and windmill (was 20). The incident record was never read either (5, unreadable history). Rate limits appear as numbers only on the plan cards in the docs, 60 requests a minute on the free tier and 600 on the pro tier, and the terms let Hyperbolic change limits without notice (10 of 15). No 429 response, `Retry-After` or backoff guidance in the docs, and no idempotency key on rental creation (0). SLA 7 to 0. The docs state a 99.5 per cent uptime figure for On-Demand and Reserved with credits reviewed case by case, and the Terms of Service disclaim uptime and any duty to give credits. A figure with discretionary credits and no SLA document isn't an SLA (manatal). The v2 API is not marked beta (10). 0 + 5 + 10 + 0 + 0 + 10 = 25.\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### Payments \u0026 pricing: Together GPU Clusters +5\n\n- Hyperbolic (15): Readings are per the 8 October check, not re-read on 4 November 2026. No x402, MPP or L402 on the GPU API. The vendor's archived x402 repository covered chat completions on another host (0). The marketplace page states a starting price of $3.19 a GPU-hour. There is no public price table and the docs point to the console. The 8 October reading of hourly prices from an open API endpoint is struck (a product endpoint), so the line rests on the marketplace figure and keeps its partial value (15 of 20). A free-tier account cannot rent anything. Renting needs a $5 deposit through Stripe, and the only free credit found is from event codes (0). Signup, email verification, the deposit and key creation happen in a browser (0). 0 + 15 + 0 + 0 = 15.\n- Together GPU Clusters (20): No machine payment protocol (0). Per GPU-hour prices for each capacity type and per GiB-month storage published without a login (20). No free trial, and creation needs credit for the full reservation or a minimum on-demand period (0). Sign-up and credit purchase are browser steps (0). 0+20+0+0 = 20.\n\n## Score by category\n\n| Category | Weight | Hyperbolic | Together GPU Clusters | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 25 | 38 | Together GPU Clusters +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 52 | 92 | Together GPU Clusters +40 |\n| Agent ergonomics | 13% (16.2 this run) | 55 | 55 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 68 | Together GPU Clusters +20 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 20 | Together GPU Clusters +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 39 | 75 | Together GPU Clusters +36 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 65 | Together GPU Clusters +1 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **38.7 · E** | **58.1 · C** | |\n\n## Facts side by side\n\n| Fact | Hyperbolic | Together GPU Clusters |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Hyperbolic Labs, Inc. | Together AI |\n| Hosted endpoint | `https://api.hyperbolic.ai` | `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| x402 | no | no |\n| Licence | Proprietary service under Hyperbolic's Terms of Service. The unmaintained hyperbolic-mcp repository on GitHub is MIT | Proprietary service under Together's terms of service. The Python SDK and CLI are Apache-2.0 and the OpenAPI document is MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-05 | 2026-10-22 |\n| Terms last updated | 2025-03-24 | no date given |\n| Privacy policy last updated | no date given | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n\n## How the scores have moved\n\n### Hyperbolic\n\n- -9.5 on 4 November 2026 (D to E): correction\n- +0.1 on 27 October 2026: checklist\n- +0.1 on 12 October 2026: time\n\n### Together GPU Clusters\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Hyperbolic.** Hyperbolic's docs carry llms.txt, Markdown pages and a dated 1 March 2027 end for legacy paths, and billing starts only once an instance is ready. API keys carry no scopes and can delete the account, rental creation has no idempotency key, no 429 guidance is documented, and renting needs a browser signup and a $5 deposit.\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### Hyperbolic\n\n1. Check current GPU configurations and hourly prices before renting. The docs point to the console for rates, and the marketplace page gave $3.19 a GPU-hour on 8 October 2026.\n2. Send `rentalType` and `gpuCount` to `POST /v2/on-demand/rentals`. Region defaults to `us-central-1` and GPU type to `h100`, so set both from the options list.\n3. List active rentals before retrying a failed create call. There is no idempotency key and every ready rental bills hourly.\n4. Save an SSH public key with `POST /v2/ssh-keys` before renting. Without `sshPublicKeyIds` the newest saved key is attached.\n5. Do not create reserved rentals unless asked. They are paid in full up front and cannot be terminated early.\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, Hyperbolic or Together GPU Clusters?\n\nTogether GPU Clusters scores 58.1 (C) on agent readiness against Hyperbolic's 38.7 (E), and leads in 6 of 7 scored categories.\n\n### Do Hyperbolic and Together GPU Clusters need an API key?\n\nBoth need an API key.\n\n### Can an agent call Hyperbolic and Together GPU Clusters without installing anything?\n\nYes. Hyperbolic has a hosted endpoint at https://api.hyperbolic.ai 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/hyperbolic-vs-together-gpu-clusters.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"hyperbolic\", \"b\": \"together-gpu-clusters\"}`. From a terminal: `anchor compare hyperbolic together-gpu-clusters`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hyperbolic.json and https://www.anchorterminal.com/api/v1/tools/together-gpu-clusters.json\n\n## Other comparisons with Hyperbolic or Together GPU Clusters\n\n- [Baseten vs Hyperbolic](https://www.anchorterminal.com/compare/baseten-vs-hyperbolic.md)\n- [Baseten vs Together GPU Clusters](https://www.anchorterminal.com/compare/baseten-vs-together-gpu-clusters.md)\n- [Beam vs Hyperbolic](https://www.anchorterminal.com/compare/beam-vs-hyperbolic.md)\n- [Beam vs Together GPU Clusters](https://www.anchorterminal.com/compare/beam-vs-together-gpu-clusters.md)\n- [Cerebrium vs Hyperbolic](https://www.anchorterminal.com/compare/cerebrium-vs-hyperbolic.md)\n- [Cerebrium vs Together GPU Clusters](https://www.anchorterminal.com/compare/cerebrium-vs-together-gpu-clusters.md)\n- [Cloud Run GPUs vs Hyperbolic](https://www.anchorterminal.com/compare/cloud-run-gpus-vs-hyperbolic.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 Hyperbolic](https://www.anchorterminal.com/compare/coreweave-vs-hyperbolic.md)\n- [CoreWeave vs Together GPU Clusters](https://www.anchorterminal.com/compare/coreweave-vs-together-gpu-clusters.md)\n- [Crusoe Cloud vs Hyperbolic](https://www.anchorterminal.com/compare/crusoe-cloud-vs-hyperbolic.md)\n- [Crusoe Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/crusoe-cloud-vs-together-gpu-clusters.md)\n- [GPUsMarket vs Hyperbolic](https://www.anchorterminal.com/compare/gpusmarket-vs-hyperbolic.md)\n- [GPUsMarket vs Together GPU Clusters](https://www.anchorterminal.com/compare/gpusmarket-vs-together-gpu-clusters.md)\n- [Hugging Face Inference Endpoints vs Hyperbolic](https://www.anchorterminal.com/compare/hugging-face-inference-endpoints-vs-hyperbolic.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 Koyeb](https://www.anchorterminal.com/compare/hyperbolic-vs-koyeb.md)\n- [Hyperbolic vs Lambda Cloud](https://www.anchorterminal.com/compare/hyperbolic-vs-lambda.md)\n- [Hyperbolic vs Massed Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-massed-compute.md)\n- [Hyperbolic vs Modal](https://www.anchorterminal.com/compare/hyperbolic-vs-modal.md)\n- [Hyperbolic vs Nebius AI Cloud](https://www.anchorterminal.com/compare/hyperbolic-vs-nebius-ai-cloud.md)\n- [Hyperbolic vs Northflank](https://www.anchorterminal.com/compare/hyperbolic-vs-northflank.md)\n- [Hyperbolic vs Replicate Deployments](https://www.anchorterminal.com/compare/hyperbolic-vs-replicate-deploy.md)\n- [Hyperbolic vs Runpod](https://www.anchorterminal.com/compare/hyperbolic-vs-runpod.md)\n- [Hyperbolic vs Thunder Compute](https://www.anchorterminal.com/compare/hyperbolic-vs-thunder-compute.md)\n- [Hyperbolic vs Vast.ai](https://www.anchorterminal.com/compare/hyperbolic-vs-vast-ai.md)\n- [Hyperbolic vs Verda](https://www.anchorterminal.com/compare/hyperbolic-vs-verda.md)\n- [Koyeb vs Together GPU Clusters](https://www.anchorterminal.com/compare/koyeb-vs-together-gpu-clusters.md)\n- [Lambda Cloud vs Together GPU Clusters](https://www.anchorterminal.com/compare/lambda-vs-together-gpu-clusters.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": "Hyperbolic vs Together GPU Clusters", "url": "" } ], "description": "Together GPU Clusters scores 58.1 (C) to Hyperbolic's 38.7 (E) for gpu compute. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Hyperbolic E 38.7", "Together GPU Clusters C 58.1", "scores" ], "h1": "Hyperbolic vs Together GPU Clusters", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/hyperbolic-vs-together-gpu-clusters", "published": "2026-10-01", "section": "tools", "title": "Hyperbolic vs Together GPU Clusters for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters" }, "tokens": { "markdown": 5100, "slim": 2780 }, "version": 1 }