Hyperbolic: API key and base URL

Low-cost open-model inference. Bring your own key; nothing is billed by us.

What the harness already knows

Provider id	`hyperbolic`
Bundled base URL	`https://api.hyperbolic.xyz/v1`
Protocol	OpenAI-compatible chat completions
API key	`HYPERBOLIC_API_KEY`
Model discovery	Yes — the model list is asked of the endpoint rather than shipped.

Connecting it

$export HYPERBOLIC_API_KEY="..."

Keys are issued by Hyperbolic — where to get one.

API key setup and troubleshooting

Official setup guide (checked 2026-10-24)

Hyperbolic has retired the .xyz inference API. Create a new sk_live_ key in the current dashboard; legacy keys are not accepted. Check the current plan and balance requirements before retrying.

Create a key using the official guide below, then run this command and paste the key into the prompt. OHarness saves it in its credential store. A key set in the process environment takes precedence over a stored key.

$oharness auth login hyperbolic

HYPERBOLIC_API_KEY is an environment variable, not a top-level config.json field. For an endpoint override, merge the providers block below into ~/.oharness/config.json; preserve your other settings. The base URL must not include /chat/completions.

The bundled catalog uses https://api.hyperbolic.xyz/v1. The current official guide uses https://api.hyperbolic.ai/inference/v1. To use the documented endpoint, merge this override into ~/.oharness/config.json. Check current model IDs and key requirements in the official guide; changing the URL alone does not migrate credentials or models.

{
  "providers": {
    "hyperbolic": {
      "baseUrl": "https://api.hyperbolic.ai/inference/v1"
    }
  }
}

If the request fails

401 or 403: read the response body, check the active key, account access and credit. An old environment variable can override a newly saved key. A terminal export only applies to that shell and processes started from it.
404: check the endpoint and the exact model ID in the vendor console. 429: check the provider’s rate limits and quota before retrying. Model names in a bundled snapshot may no longer be available.

Install OHarness · Provider configuration · Configuration files

What you get either way

The same agent loop, the same tools, the same MCP servers and the same permission rules, whichever provider is underneath — and switching between them mid-session converts nothing, because history is never stored in a vendor’s shape. What an agent harness is covers why that is the hard part, and the providers reference covers the catalogue itself.

All 34 providers · Install OHarness