Hyperbolic vs Runpod

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.

Runpod

Per-second billing across more than a dozen serverless GPU classes, H100 at $4.79 and A100 80 GB at $2.72 an hour. Data-centre outages of 6 to 24 hours in each of July, August and September 2026.

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.

Runpod

1. Create a Restricted or Read Only key per endpoint for the agent, not an All key
2. Use REST v2 at api.runpod.io/v2 with a Bearer header; avoid GraphQL, which puts the key in the URL
3. Fetch /run results within 30 minutes and /runsync results within 1 minute, or they're gone
4. Call /retry on a failed job ID rather than submitting a duplicate job
5. Check /health before relying on an endpoint idle for a week, since max workers drop to 0