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
  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. 09Code with HIPS
  7. 10Coding-tool setup
    1. AHIPS Code
    2. BClaude Code
    3. CCodex
    4. DOpenCode
    5. EKilo
    6. FPi
    7. GQwen Code
    8. HCrush
    9. ICline
    10. JPrime Agent
    11. KAider
    12. LGoose
    13. MHermes Agent
    14. NGrok Build
    15. ODeepSeek Harness
    16. POther coding tools and editor integrations
  8. 11Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 12Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 13Billing
  11. 14Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 15Semantic routing
  13. 16Guardrails
  14. 17Knowledge

Reference

  1. 18API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GPrices API
    8. HTasks
    9. IEmbeddings and rerank
    10. JImages
    11. KJobs
    12. LUploads
    13. MFiles
    14. NBatches
    15. OWebhooks
    16. PVector stores
    17. QDeployments
    18. RRequirements and headers
    19. SErrors
    20. TUsage
    21. UVersioning
  2. 19Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 20Changelog
Sheet indexCommand line

Get started

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

Guides

  1. 04HIPS SDK
  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. 09Code with HIPS
  7. 10Coding-tool setup
    1. AHIPS Code
    2. BClaude Code
    3. CCodex
    4. DOpenCode
    5. EKilo
    6. FPi
    7. GQwen Code
    8. HCrush
    9. ICline
    10. JPrime Agent
    11. KAider
    12. LGoose
    13. MHermes Agent
    14. NGrok Build
    15. ODeepSeek Harness
    16. POther coding tools and editor integrations
  8. 11Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 12Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 13Billing
  11. 14Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 15Semantic routing
  13. 16Guardrails
  14. 17Knowledge

Reference

  1. 18API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GPrices API
    8. HTasks
    9. IEmbeddings and rerank
    10. JImages
    11. KJobs
    12. LUploads
    13. MFiles
    14. NBatches
    15. OWebhooks
    16. PVector stores
    17. QDeployments
    18. RRequirements and headers
    19. SErrors
    20. TUsage
    21. UVersioning
  2. 19Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 20Changelog
11
  1. Docs/
  2. Command line/
  3. Sign in
(Detail B)
llms.txt

Sign in with device authorization

On this sheet10 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. Authorized devices and apps
  10. 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 by device authorization is served: the provider app and hi sign in this way, and HIPS Code does once it is published.

F
Fig. 1, sheet 11Command 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
Option of `hi login`What it does
--no-browserDoes not open the browser; shows the link and the QR code only, for a machine you reach over SSH
--device-name <NAME>A name for this computer on the approval page and in Authorized devices and apps; none is sent otherwise
  • Option of `hi login`
    --no-browser
    What it does
    Does not open the browser; shows the link and the QR code only, for a machine you reach over SSH
  • Option of `hi login`
    --device-name <NAME>
    What it does
    A name for this computer on the approval page and in Authorized devices and apps; none is sent otherwise

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
account_restrictedThe workspace owner, or you, cannot use HIPS. Contact HIPS support
verification_requiredThe workspace owner has not passed identity verification. Not sent while identity verification is switched off, as it is since 2026-11-09; documented for when it is switched back on
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
    account_restricted
    What it means
    The workspace owner, or you, cannot use HIPS. Contact HIPS support
  • The Console answers
    verification_required
    What it means
    The workspace owner has not passed identity verification. Not sent while identity verification is switched off, as it is since 2026-11-09; documented for when it is switched back on
  • 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 is replaced each time it is used and has no idle expiry, so a tool stays signed in until you sign out or revoke it.
  • 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/codeserved

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

POST/auth/device/tokenserved

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

POST/auth/device/revokeserved

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.

Authorized devices and apps

Account in the Console lists, under Authorized devices and apps, every tool you signed in with a code: the tool and the device it runs on, the scopes, the workspace or provider account it is granted for, where it was asked from and approved from, when it signed in and was last used, and its state. Revoke signs one out at once: every token of that sign-in is refused from then on, and the tool asks you to sign in again. Revoke all ends every tool sign-in of your own, for a lost or stolen computer; a machine connected with an enrollment code stays connected and is signed out on Connect many machines instead. Signing out your other browser sessions leaves tools signed in; revoke them here.

Revoking HIPS Provider's sign-in revokes the device certificates it issued, so those devices stop at once; each stays enrolled in My GPUs, signed out, until you connect it again. Revoking never removes a device; that is Remove in My GPUs.

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 sheetInstall and update
Next sheetStatus and models
Sheet
11 of 20
Detail
B
Updated
2026-11-11
Sign in to the Console

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. Authorized devices and apps
  10. 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
  • 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

Compare

  • OpenRouter alternatives
  • Together AI alternatives
  • Groq alternatives
  • All comparisons

Company

  • About
  • Contact
  • Affiliate program
  • HIPS Payments

Legal

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

Support

  • Contact HIPS
  • Looking for payments support?

HIPS. AI inference for builders.

hips.com

Hyperscale Inference Processing Systems OÜ