Head to head · Compute gpu · October 2026 research run

Hyperbolic vs Verda

Verda scores 62.3 (B) on agent readiness against Hyperbolic's 48 (D), and leads in every scored category. Both do compute gpu.

Which one, for what

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

Verda B

Good for Agents that rent whole GPU machines or clusters in Finland for training or batch work, or deploy scale-to-zero container endpoints, and that can run a local CLI for MCP.

Ahead on

  • Reliability, 67 against 52
  • Schema & documentation, 82 against 77
  • Agent ergonomics, 63 against 55
  • Security & auth, 68 against 47
  • Payments & pricing, 20 against 15
  • Maintenance & community, 83 against 42
  • Transparency & trust, 76 against 61

Also in its favour

  • Runs on your own machine

Watch for

No free tier. Accounts are prepaid, and instances are discontinued and volumes deleted when the balance reaches zero

Score by category

CategoryWeight this runHyperbolicVerdaEdge
Reliability16%205267Verda +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27782Verda +5
Agent ergonomics13%16.25563Verda +8
Security & auth14%17.54768Verda +21
Payments & pricing10%12.51520Verda +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84283Verda +41
Transparency & trust7%8.86176Verda +15
Negative events≤15-3-3
Total48 · D62.3 · B

Facts side by side

FactHyperbolicVerda
KindHTTP APIHTTP API
VendorHyperbolic Labs, Inc.Verda
Hosted endpointhttps://api.hyperbolic.aihttps://api.verda.com/v1
TransportsHTTPHTTP, stdio
AuthAPI keyOAuth
PricingPay per usePay per use
x402nono
LicenceProprietary service under Hyperbolic's Terms of Service. The unmaintained hyperbolic-mcp repository on GitHub is MITProprietary service under Verda's Terms of Service. The CLI, the Python SDK and the Go SDK on GitHub are Apache-2.0
Tools exposednone18
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-052026-10-07
Terms last updated2025-03-242025-09-30
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularitynone10k PyPI/wk

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.

Verda

The REST API has a public OpenAPI 3.1 document, a dated changelog, published rate limits with Retry-After, and an audit log endpoint. The CLI's MCP server refuses billed or destructive calls without confirm: true. Access needs a browser signup and a prepaid balance, credentials carry one scope, and instance creation has no idempotency key.

Before you call either

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.

Verda

  1. Exchange the client ID and secret at POST /v1/oauth2/token, then send the access token as a Bearer header. It expires after 3,600 seconds, so refresh it.
  2. Send location_code on every create call. Requests without it have returned 400 since March 2026.
  3. Call GET /v1/instance-availability before launching. POST /v1/instances returns 503 service_unavailable when the location has no capacity.
  4. List instances before retrying a failed launch, because create has no idempotency key.
  5. Use the delete action to stop charges. shutdown keeps billing, and deleted volumes stay recoverable for 96 hours unless delete_permanently is set.

Questions

Which is better for AI agents, Hyperbolic or Verda?

Verda scores 62.3 (B) on agent readiness against Hyperbolic's 48 (D), and leads in every scored category.

Do Hyperbolic and Verda need an API key?

Hyperbolic needs an API key. Verda uses an OAuth sign-in.

Can an agent call Hyperbolic and Verda without installing anything?

Yes. Hyperbolic has a hosted endpoint at https://api.hyperbolic.ai and Verda at https://api.verda.com/v1.

Other comparisons with Hyperbolic or Verda

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.