Skip to content
HIPS
  • Earn with your GPU
  • Pricing
  • Docs
Sign inJoin early access
⌘K

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Migrate to HIPS

Guides

  1. 04HIPS SDK
    1. APython
    2. BTypeScript and JavaScript
    3. CGo
    4. DRust
    5. EJava
    6. F.NET
    7. GPHP
    8. HRuby
  2. 05Import and run your model
  3. 06Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 07Batch jobs
  5. 08Prompt caching
  6. 09Coding-tool setup
    1. AClaude Code
    2. BOther coding tools and editor integrations
  7. 10Command line
    1. ASign in

Reference

  1. 11API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DModels
    5. ETasks
    6. FJobs
    7. GUploads
    8. HDeployments
    9. IRequirements and headers
    10. JErrors
    11. KUsage
    12. LVersioning
  2. 12Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 13Changelog
Sheet indexCommand line

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Migrate to HIPS

Guides

  1. 04HIPS SDK
    1. APython
    2. BTypeScript and JavaScript
    3. CGo
    4. DRust
    5. EJava
    6. F.NET
    7. GPHP
    8. HRuby
  2. 05Import and run your model
  3. 06Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 07Batch jobs
  5. 08Prompt caching
  6. 09Coding-tool setup
    1. AClaude Code
    2. BOther coding tools and editor integrations
  7. 10Command line
    1. ASign in

Reference

  1. 11API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DModels
    5. ETasks
    6. FJobs
    7. GUploads
    8. HDeployments
    9. IRequirements and headers
    10. JErrors
    11. KUsage
    12. LVersioning
  2. 12Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 13Changelog
10
  1. Docs/
  2. Command line/
  3. Sign in
(Detail A)

PreviewNot yet validated. Join early access

llms.txt

Sign in with device authorization

On this sheet9 sections
  1. Four steps
  2. The code
  3. Approving
  4. What hi asks for
  5. Tokens
  6. The routes
  7. At the gateway
  8. Sign out and revoke
  9. HIPS Code signs in the same way

Your tools sign in as you with OAuth 2.0 device authorization (RFC 8628). The tool shows a code; you approve it in the Console, where you are already signed in, and choose the workspace its usage belongs to. The tool never sees your password and never needs an API key.

Note

Sign-in is decided and not yet served; hi and HIPS Code use it once they are published.

F
Fig. 1, sheet 10Command line

Four steps

  1. 01

    Step 1: Run hi login. It prints a user code XXXX-XXXX, a QR code drawn in the terminal and the link that both encode.

  2. 02

    Step 2: Open the link, or scan the QR code with a phone: the approval page needs no browser on the same machine.

  3. 03

    Step 3: In the Console, check the tool's name, the access it asks for and where the request came from, choose the workspace, and approve.

  4. 04

    Step 4: hi stops waiting and says which workspace it is signed in to.

Shell

00000000000000000000000000000000000000001hi login
Shell sample

The code

  • Eight characters from an alphabet with no look-alike characters, shown as XXXX-XXXX.
  • Single use, and valid for 10 minutes.
  • Void after five wrong attempts, and rate-limited per address and per account.
  • Approve only a code you started yourself. If a code reaches you any other way, deny it.

Approving

The approval page at console.hips.com/device shows the tool's name, the access it asks for in plain words, the address and country the request came from, and the workspace choice with that workspace's tool defaults. Approve or deny; nothing happens until you do.

The Console answersWhat it means
tool_defaults_requiredThe workspace has no tool defaults yet: an owner or admin sets the pool, pricing mode, region and fallback used for tools in Workspace settings, then you approve again
verification_requiredThe workspace owner has not passed identity verification
Not foundThe code is unknown, expired, used or voided. One message for all four, so a guess learns nothing
  • The Console answers
    tool_defaults_required
    What it means
    The workspace has no tool defaults yet: an owner or admin sets the pool, pricing mode, region and fallback used for tools in Workspace settings, then you approve again
  • The Console answers
    verification_required
    What it means
    The workspace owner has not passed identity verification
  • The Console answers
    Not found
    What it means
    The code is unknown, expired, used or voided. One message for all four, so a guess learns nothing

What hi asks for

The client `hi` asks for two of the four scopes; `provider` is the provider app's and `admin` is never asked for by a buyer's tool

ScopeAllows
inferenceRequests in the workspace you chose, attributed to you
accountReading who is signed in
  • Scope
    inference
    Allows
    Requests in the workspace you chose, attributed to you
  • Scope
    account
    Allows
    Reading who is signed in

Tokens

  • An access token that lasts 1 hour, and a refresh token that lasts 30 days and is replaced each time it is used.
  • Both kept in the operating system's keystore and refreshed by the tool without asking. Never printed.
  • At the gateway the access token works like a key of the workspace you chose, with the same rate limits, and the workspace's tool defaults in place of a key's defaults.

The routes

Three exact paths on ai.hips.com, in OAuth's own wire format. A tool calls them; you never do.

POST/auth/device/codepreview

Start a sign-in: the device code, the user code XXXX-XXXX and the links.

POST/auth/device/tokenpreview

Poll with the device code until approved; later, exchange the refresh token for a new access token.

POST/auth/device/revokepreview

Revoke the sign-in (RFC 7009); hi logout calls it.

While pollingWhat hi does
authorization_pendingKeeps waiting
slow_downWaits longer between polls
access_deniedStops: the code was denied in the Console
expired_tokenStops: the code expired; run hi login again
  • While polling
    authorization_pending
    What hi does
    Keeps waiting
  • While polling
    slow_down
    What hi does
    Waits longer between polls
  • While polling
    access_denied
    What hi does
    Stops: the code was denied in the Console
  • While polling
    expired_token
    What hi does
    Stops: the code expired; run hi login again

At the gateway

AnswerWhat the tool does
401 authentication_error, code token_expiredRefreshes the access token and retries once
403 permission_error, code insufficient_scopeThe sign-in lacks the scope; sign in again
  • Answer
    401 authentication_error, code token_expired
    What the tool does
    Refreshes the access token and retries once
  • Answer
    403 permission_error, code insufficient_scope
    What the tool does
    The sign-in lacks the scope; sign in again

Sign out and revoke

Shell

00000000000000000000000000000000000000001hi logout
Shell sample

hi logout revokes the sign-in at HIPS and removes the stored tokens. To revoke a tool from anywhere, open Account in the Console, Authorized devices and apps, and revoke it there; it takes effect on the tool's next request.

HIPS Code signs in the same way

HIPS Code, the company's coding agent, is the client hips-code with the scopes inference and account. Its sign-in shows the same code, QR code and link in the terminal, keeps the tokens in the keystore and sends the access token to the gateway; HIPS_API_KEY remains the path for CI and scripted use. Its row in the supported-tools matrix is the first one, unvalidated until tested Not decided yet.

Related sheets

  • The hi command line
  • Authentication reference
  • Coding-tool setup
Previous sheetCommand line
Next sheetOverview
Sheet
10 of 13
Detail
A
Updated
2026-10-21
Status
Preview
Join early access

On this sheet

  1. Four steps
  2. The code
  3. Approving
  4. What hi asks for
  5. Tokens
  6. The routes
  7. At the gateway
  8. Sign out and revoke
  9. HIPS Code signs in the same way

Product

  • Inference
  • Models
  • Deploy your model
  • Always-on GPU capacity
  • How it works
  • Use cases
  • Pricing

Developer

  • Docs
  • Quickstart preview
  • Migrate to HIPS
  • HIPS SDK
  • Batch jobs
  • API reference

Provider

  • Earn with your GPU
  • Register GPU interest
  • Download for Mac
  • Download for Windows
  • Download for Linux

Resource

  • Security and Data
  • Resources
  • llms.txt

Company

  • About
  • Contact
  • Affiliate program
  • HIPS Payments

Legal

  • Legal
  • Consumer Health Data Privacy Policy
  • Report content
  • Cookie settings

Support

  • Contact HIPS
  • Looking for payments support?

HIPS. AI inference for builders.

hips.com

Hyperscale Inference Processing Systems OÜ