# Hyperbolic vs Together GPU Clusters (slim)

> 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.

- Full: https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.md (~5,100 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters.json · canonical https://www.anchorterminal.com/compare/hyperbolic-vs-together-gpu-clusters
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- Hyperbolic: E 38.7, rank #1335 of 1486 · https://www.anchorterminal.com/tools/hyperbolic.min.md
- Together GPU Clusters: C 58.1, rank #764 of 1486 · https://www.anchorterminal.com/tools/together-gpu-clusters.min.md
- Hyperbolic, good 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.
- Together GPU Clusters, good for Training, fine-tuning and batch jobs that need several 8-GPU nodes with InfiniBand, run by a pipeline that creates and deletes clusters. Ahead on Reliability, 38 against 25; Schema & documentation, 92 against 52; Security & auth, 68 against 48; Payments & pricing, 20 against 15; Maintenance & community, 75 against 39. Also No incidents deducted, where Hyperbolic loses 3 points for them.

| Category | Hyperbolic | Together GPU Clusters |
| --- | --- | --- |
| Reliability (16%) | 25 | 38 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 52 | 92 |
| Agent ergonomics (13%) | 55 | 55 |
| Security & auth (14%) | 48 | 68 |
| Payments & pricing (10%) | 15 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 39 | 75 |
| Transparency & trust (7%) | 64 | 65 |

| Fact (where they differ) | Hyperbolic | Together GPU Clusters |
| --- | --- | --- |
| Vendor | Hyperbolic Labs, Inc. | Together AI |
| Hosted endpoint | `https://api.hyperbolic.ai` | `https://api.together.ai/v1/compute/clusters` |
| Transports | HTTP |  |
| 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 |
| Last release | 2026-10-05 | 2026-10-22 |
| Terms last updated | 2025-03-24 | no date given |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |

Why the edge:
- Schema & documentation, Together GPU Clusters +40: 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.); 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.)
- Maintenance & community, Together GPU Clusters +36: 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.); 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.)
- Security & auth, Together GPU Clusters +20: 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.); 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.)
- Reliability, Together GPU Clusters +13: 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.); 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.)
- Payments & pricing, Together GPU Clusters +5: 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.); 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.)