Head to head · Compute gpu · October 2026 research run
Hyperbolic vs Thunder Compute
Thunder Compute scores 56.1 (C) on agent readiness against Hyperbolic's 48 (D), and leads in 5 of 7 scored categories. Hyperbolic leads on schema & documentation and agent ergonomics. Both do compute gpu.
Which one, for what
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.
Ahead on
- Schema & documentation, 77 against 70
- Agent ergonomics, 55 against 48
Watch for
API keys carry no scopes or expiry in the reviewed documentation, and the same key can call DELETE /v2/users/me
Good for Agents in coding tools that rent a single persistent GPU machine for development, fine-tuning or a model server, at low hourly prices and over MCP.
Ahead on
- Reliability, 65 against 52
- Payments & pricing, 20 against 15
- Maintenance & community, 79 against 42
Also in its favour
- No incidents deducted, where Hyperbolic loses 3 points for them
Watch for
No rate limits, 429 guidance or SLA were found in the reviewed documentation, and the terms disclaim availability
Score by category
| Category | Weight this run | Hyperbolic | Thunder Compute | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 52 | 65 | Thunder Compute +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 77 | 70 | Hyperbolic +7 |
| Agent ergonomics | 13%16.2 | 55 | 48 | Hyperbolic +7 |
| Security & auth | 14%17.5 | 47 | 51 | Thunder Compute +4 |
| Payments & pricing | 10%12.5 | 15 | 20 | Thunder Compute +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 42 | 79 | Thunder Compute +37 |
| Transparency & trust | 7%8.8 | 61 | 64 | Thunder Compute +3 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 48 · D | 56.1 · C |
Facts side by side
| Fact | Hyperbolic | Thunder Compute |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Hyperbolic Labs, Inc. | Thunder Compute |
| Hosted endpoint | https://api.hyperbolic.ai | https://api.thundercompute.com:8443/v1 |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for compute gpu | not published | $0.219 per GB per month |
| x402 | no | no |
| Licence | Proprietary service under Hyperbolic's Terms of Service. The unmaintained hyperbolic-mcp repository on GitHub is MIT | Proprietary service under Thunder Compute's Terms and Conditions. The tnr CLI on GitHub is MIT |
| Tools exposed | none | 28 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.Thunder-Compute/thunder-compute |
| Last release | 2026-10-05 | 2026-09-16 |
| Terms last updated | 2025-03-24 | 2026-09-28 |
| Privacy policy last updated | no date given | 2026-09-28 |
| Customer content may train models | not found in the text | not found in the text |
| 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 | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | none | 34 stars |
Verdicts
Hyperbolic
The API serves its own OpenAPI 3.1 document without a key, lists GPU prices on an open endpoint and dates the removal of legacy paths at 1 March 2027. API keys carry no scopes and can delete the account, rental creation has no idempotency key, and renting needs a browser signup and a $5 deposit.
Thunder Compute
The hosted MCP server signs in with OAuth and separate read and write scopes, and the REST API has a public OpenAPI 3.1 document with keyless price and availability endpoints. No rate limits, SLA or API changelog were found, instance creation has no idempotency key, and instances cannot be stopped, only deleted.
Before you call either
Hyperbolic
- Read
GET /v2/on-demand/rental-optionsfirst. It needs no key and lists what can be rented now, withcostPerHourCentsper GPU configuration. - Send
rentalTypeandgpuCounttoPOST /v2/on-demand/rentals. Region defaults tous-central-1and GPU type toh100, 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-keysbefore renting. WithoutsshPublicKeyIdsthe newest saved key is attached. - Do not create reserved rentals unless asked. They are paid in full up front and cannot be terminated early.
Thunder Compute
- Call
GET /v2/statusor theget_availabilitytool before creating an instance. Availability can change before launch, and creation fails when a type is sold out. - List instances before retrying a failed create, because the call has no idempotency key.
- Pass
public_keyon create. If omitted, the response carries a generated private key that is returned once. - To pause work, create a snapshot, delete the instance and later create a new instance from the snapshot. Snapshot storage keeps billing until deleted.
- For headless use set
TNR_API_TOKENto a token from the console. The MCP server needs a browser sign-in on first connection.
Questions
Which is better for AI agents, Hyperbolic or Thunder Compute?
Thunder Compute scores 56.1 (C) on agent readiness against Hyperbolic's 48 (D), and leads in 5 of 7 scored categories. Hyperbolic leads on schema & documentation and agent ergonomics.
Do Hyperbolic and Thunder Compute need an API key?
Hyperbolic needs an API key. Thunder Compute takes an API key or an OAuth sign-in.
Can an agent call Hyperbolic and Thunder Compute without installing anything?
Yes. Hyperbolic has a hosted endpoint at https://api.hyperbolic.ai and Thunder Compute at https://api.thundercompute.com:8443/v1.
Other comparisons with Hyperbolic or Thunder Compute
- Baseten vs Hyperbolic
- Baseten vs Thunder Compute
- Beam vs Hyperbolic
- Beam vs Thunder Compute
- Cerebrium vs Hyperbolic
- Cerebrium vs Thunder Compute
- CoreWeave vs Hyperbolic
- CoreWeave vs Thunder Compute
- Hugging Face Inference Endpoints vs Hyperbolic
- Hugging Face Inference Endpoints vs Thunder Compute
- Hyperbolic vs Koyeb
- Hyperbolic vs Lambda Cloud
- Hyperbolic vs Modal
- Hyperbolic vs Nebius AI Cloud
- Hyperbolic vs Northflank
- Hyperbolic vs Replicate Deployments
- Hyperbolic vs Runpod
- Hyperbolic vs Vast.ai
- Hyperbolic vs Verda
- Koyeb vs Thunder Compute
- Lambda Cloud vs Thunder Compute
- Modal vs Thunder Compute
- Nebius AI Cloud vs Thunder Compute
- Northflank vs Thunder Compute
- Replicate Deployments vs Thunder Compute
- Runpod vs Thunder Compute
- Thunder Compute vs Vast.ai
- Thunder Compute vs Verda
Machine-readable
- This page as Markdown
/compare/hyperbolic-vs-thunder-compute.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hyperbolic.json·/api/v1/tools/thunder-compute.json - From a terminal
anchor compare hyperbolic thunder-compute(the CLI) - Over MCP
compare_tools {"a": "hyperbolic", "b": "thunder-compute"}at/mcp, no key