Hyperbolic vs Northflank

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.

Northflank

OpenAPI 3.0 with over 100 paths, enums and per_page, page and cursor on every list. No scale to zero for services; minimum instances must be at least 1.

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.

Northflank

1. Issue the agent a team token under an API role limited to one project, not a personal token
2. Read x-ratelimit-remaining and wait x-ratelimit-reset seconds on a 429; the default is 1,000 calls an hour
3. Page lists with per_page up to 100 and the returned cursor instead of numbered pages
4. Use a job, not a service, for anything that finishes; services bill until paused or deleted
5. Fetch any docs page with .md appended to get Markdown