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

PreviewNot yet validated. Join early access

llms.txt

The hi command line

On this sheet3 sections
  1. Sign in
  2. What hi covers
  3. Keys or sign-in

hi is the HIPS command line for buyers: one binary for signing in, models, batches, imports, keys and usage. It signs in as you, in the browser, by device authorization, so it never needs an API key. It is its own binary, separate from the provider app that runs on a GPU owner's machine.

Note

hi is decided and not yet published. It will be distributed through Homebrew, a shell installer and Windows packages; the install command appears here when it is.

F
Fig. 1, sheet 10Command line

Sign in

Shell

00000000000000000000000000000000000000001hi login
Shell sample

hi login shows a code and a link, and you approve it in the Console while signed in. Every step is on Sign in with device authorization.

What hi covers

Command groupWhat it doesPage
hi login, hi logoutSign in by device authorization, sign out and revokeSign in
ModelsThe catalog and your own modelsWhen the command ships
BatchesCreate, follow and download batch jobsWhen the command ships
ImportsImport a model from its hub, follow the importWhen the command ships
KeysThe workspace's API keys, for servers and SDKsWhen the command ships
UsageUsage and cost by key, tool and personWhen the command ships
  • Command group
    hi login, hi logout
    What it does
    Sign in by device authorization, sign out and revoke
    Page
    Sign in
  • Command group
    Models
    What it does
    The catalog and your own models
    Page
    When the command ships
  • Command group
    Batches
    What it does
    Create, follow and download batch jobs
    Page
    When the command ships
  • Command group
    Imports
    What it does
    Import a model from its hub, follow the import
    Page
    When the command ships
  • Command group
    Keys
    What it does
    The workspace's API keys, for servers and SDKs
    Page
    When the command ships
  • Command group
    Usage
    What it does
    Usage and cost by key, tool and person
    Page
    When the command ships

A management command's page waits for the platform API it calls Not decided yet; each command group gets its page once it ships.

Keys or sign-in

An API key is a workspace's credential for servers and SDKs. A person's tools, hi, HIPS Code and the provider app, sign in as the person instead, and their usage is attributed to the person and the workspace chosen at approval. The Authentication reference has both.

Related sheets

  • Sign in with device authorization
  • Authentication reference
  • Coding-tool setup
Previous sheetOther coding tools and editor integrations
Next sheetSign in
Sheet
10 of 13
Updated
2026-10-21
Status
Preview
Join early access

On this sheet

  1. Sign in
  2. What hi covers
  3. Keys or sign-in

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Ü