Skip to main content
Every data call to Hive needs a signed-in account. How you sign in depends on whether a human is present when the agent connects. initialize and tools/list stay open without a credential, so your client can connect, show Hive’s tools, and prompt you to sign in. Calling a tool needs the sign-in.

Sign-in for interactive clients

Clients like Claude, Cursor, VS Code, and ChatGPT authorize with OAuth in the browser. You add only the URL. The first time the client uses Hive, it opens a sign-in page. Sign in with GitHub, Google or a code sent to your email, approve the connection, and the client stores the credential itself. An account is created on first sign-in. It starts on the Free plan with 10,000 credits a month.
No secret goes in your config file with OAuth. If a setup guide tells you to paste a key into mcp.json, you are looking at the headless path by mistake.
You can review and revoke connected clients any time from dashboard settings. Disconnecting revokes every access and refresh token issued to that client.

Sign in on a machine with no browser

An SSH session, a container or a cloud agent cannot open a sign-in page. Run:
The CLI prints a short code and a link. Open the link on any device where you can sign in, check that the app is “Hive CLI”, and select Approve. The CLI is waiting, and it saves its credential as soon as you approve. The code works once and expires after 10 minutes. hive auth login chooses this flow on its own when SSH_CONNECTION or CI is set, when a Linux machine has no DISPLAY, or when the browser fails to open. Approving creates a new Hive CLI key for your account and disables your older CLI keys, the same as signing in with the browser. MCP clients that support the OAuth device flow can use the device_authorization_endpoint in Hive’s OAuth metadata. The client must list urn:ietf:params:oauth:grant-type:device_code in its registered grant_types.

API keys for servers and scripts

Cron jobs, backends, and CI have no browser, so they use a key instead:
Create one at dashboard keys. A few things worth knowing before you do:
  • The full secret appears once, at creation. Hive stores a hash and a short non-secret prefix afterwards, so there is no way to retrieve it later. Put it in your secret manager immediately.
  • Credits are tracked on your account, not per key. Creating a second key does not give you a second allowance.
  • Disabling a key stops it authenticating once the change propagates. Disabled keys stay listed for audit history and stop counting toward your active key limit.
Never commit a Hive key or paste it into a client config that syncs to a repository. Use an environment variable or your platform’s secret storage.

Which method applies

When a call is rejected

A rejected call says what failed and what to do next. The common cases:
  • Not signed in. The client called a tool without a credential. Complete the sign-in your client opens, or add an API key.
  • Credits exhausted. Your plan’s monthly allowance is spent. Hive stops rather than billing overage, so requests fail with a clear quota error until the cycle resets.
See limits for how credits and rate limits work, and errors for every code.