Get an audit

Head to head · Compute gpu · October 2026 research run

CoreWeave vs Hyperbolic

CoreWeave scores 61.5 (C) on agent readiness against Hyperbolic's 48 (D), and leads in 6 of 7 scored categories. Both do compute gpu.

CoreWeaveCoreWeave, Inc. · HTTP API C61.5/100#421 of 841 HyperbolicHyperbolic Labs, Inc. · HTTP API D48/100#729 of 841

Which one, for what

CoreWeave C

Good for Teams that already run Kubernetes and need whole multi-GPU nodes or clusters for training and dedicated inference, with a contract and IAM.

Ahead on

  • Security & auth, 74 against 47
  • Payments & pricing, 20 against 15
  • Maintenance & community, 80 against 42
  • Transparency & trust, 77 against 61

Also in its favour

  • No incidents deducted, where Hyperbolic loses 3 points for them

Watch for

No self-serve route. CoreWeave's sales team approves an organisation and emails the activation link before a token can be created

Hyperbolic D

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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

API keys carry no scopes or expiry in the reviewed documentation, and the same key can call DELETE /v2/users/me

Score by category

CategoryWeight this runCoreWeaveHyperbolicEdge
Reliability16%205052Hyperbolic +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27977CoreWeave +2
Agent ergonomics13%16.25855CoreWeave +3
Security & auth14%17.57447CoreWeave +27
Payments & pricing10%12.52015CoreWeave +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88042CoreWeave +38
Transparency & trust7%8.87761CoreWeave +16
Negative events≤150-3
Total61.5 · C48 · D

Facts side by side

FactCoreWeaveHyperbolic
KindHTTP APIHTTP API
VendorCoreWeave, Inc.Hyperbolic Labs, Inc.
Hosted endpointhttps://api.coreweave.comhttps://api.hyperbolic.ai
TransportsHTTPHTTP
AuthTokenAPI key
PricingPay per usePay per use
x402nono
LicenceProprietary service under CoreWeave's Terms of Service. The Terraform provider on GitHub is MITProprietary service under Hyperbolic's Terms of Service. The unmaintained hyperbolic-mcp repository on GitHub is MIT
Tools exposed38none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-022026-10-05
Terms last updated2022-06-302025-03-24
Privacy policy last updated2026-02-24no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textyes

Verdicts

CoreWeave

Per-hour prices for 8-GPU H100, H200 and B200 nodes are public, the docs ship as Markdown with llms.txt and embedded OpenAPI specs, and IAM has read-only roles per service. An organisation must be approved by CoreWeave's sales team before any token exists, and no request rate limits were found in the reviewed documentation.

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.

Before you call either

CoreWeave

  1. Create an API access token at console.coreweave.com/tokens with an expiry and send it as Authorization: Bearer to https://api.coreweave.com
  2. Add GPUs by applying a NodePool resource (compute.coreweave.com/v1alpha1) to a CKS cluster with instanceType and targetNodes. instanceType can't be changed afterwards
  3. Set targetNodes to 0 or delete the Node Pool when a job ends. Nodes are whole 8-GPU machines billed by the hour
  4. Never pass dry_run to the MCP tool coreweave_kubectl_apply expecting a preview. The reference says the parameter is ignored and the manifest is applied
  5. Use a separate Forge API key and https://api.inference.wandb.ai/v1 for Serverless Inference. A CoreWeave API access token doesn't work there

Hyperbolic

  1. Read GET /v2/on-demand/rental-options first. It needs no key and lists what can be rented now, with costPerHourCents per GPU configuration.
  2. 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.
  3. List active rentals before retrying a failed create call. There is no idempotency key and every ready rental bills hourly.
  4. Save an SSH public key with POST /v2/ssh-keys before renting. Without sshPublicKeyIds the newest saved key is attached.
  5. Do not create reserved rentals unless asked. They are paid in full up front and cannot be terminated early.

Questions

Which is better for AI agents, CoreWeave or Hyperbolic?

CoreWeave scores 61.5 (C) on agent readiness against Hyperbolic's 48 (D), and leads in 6 of 7 scored categories.

Do CoreWeave and Hyperbolic need an API key?

CoreWeave needs an access token. Hyperbolic needs an API key.

Can an agent call CoreWeave and Hyperbolic without installing anything?

Yes. CoreWeave has a hosted endpoint at https://api.coreweave.com and Hyperbolic at https://api.hyperbolic.ai.

Other comparisons with CoreWeave or Hyperbolic

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report