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 indexHIPS SDK

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
04
  1. Docs/
  2. HIPS SDK

PreviewNot yet validated. Join early access

llms.txt

The HIPS SDK for other supported model types

On this sheet7 sections
  1. Eight languages, released together
  2. The same task in every language
  3. What the SDK wraps
  4. What the SDK adds
  5. What the SDK never does
  6. One behavior for every language
  7. SDK task guides

Go beyond language models with the HIPS SDK

The HIPS SDK will provide the intended path for other supported model types, including image, video, audio, and specialist models such as classifiers. Import your supported model from Hugging Face, then use the SDK to send inputs and work with its results. The guides will explain each task’s request format, usage units, and result handling.

Fig. 1, sheet 04HIPS SDK

Eight languages, released together

The HIPS SDK will ship in Python, TypeScript and JavaScript, Go, Rust, Java (usable from Kotlin), .NET, PHP and Ruby, released together. Package names and methods are not yet decided Not decided yet; each language's page previews its configuration, a first task and its idioms.

LanguageRuntimeRepository
PythonPython 3.10 and newerhips-ai/hips-sdk-python
TypeScript and JavaScriptNode 20 and newer, Deno, Bun, edge runtimeships-ai/hips-sdk-node
GoSet with the buildhips-ai/hips-sdk-go
RustSet with the buildhips-ai/hips-sdk-rust
Java (usable from Kotlin)JVM 17 and newerhips-ai/hips-sdk-java
.NET.NET 8 and newerhips-ai/hips-sdk-dotnet
PHPPHP 8.2 and newerhips-ai/hips-sdk-php
RubyRuby 3.2 and newerhips-ai/hips-sdk-ruby
  • Language
    Python
    Runtime
    Python 3.10 and newer
    Repository
    hips-ai/hips-sdk-python
  • Language
    TypeScript and JavaScript
    Runtime
    Node 20 and newer, Deno, Bun, edge runtimes
    Repository
    hips-ai/hips-sdk-node
  • Language
    Go
    Runtime
    Set with the build
    Repository
    hips-ai/hips-sdk-go
  • Language
    Rust
    Runtime
    Set with the build
    Repository
    hips-ai/hips-sdk-rust
  • Language
    Java (usable from Kotlin)
    Runtime
    JVM 17 and newer
    Repository
    hips-ai/hips-sdk-java
  • Language
    .NET
    Runtime
    .NET 8 and newer
    Repository
    hips-ai/hips-sdk-dotnet
  • Language
    PHP
    Runtime
    PHP 8.2 and newer
    Repository
    hips-ai/hips-sdk-php
  • Language
    Ruby
    Runtime
    Ruby 3.2 and newer
    Repository
    hips-ai/hips-sdk-ruby

Note

No install command or package name appears until the package names are decided and every SDK passes the shared conformance suite Not decided yet. Swift, Kotlin-native and Dart get a page only if they ship.

The same task in every language

One call, a classification task against your own model's deployment, as each SDK will write it. The names are proposals and the shapes illustrative; each language's page has the rest.

00000000000000000000000000000000000000001from hips import Hips2 3# Reads HIPS_API_KEY and HIPS_BASE_URL (https://ai.hips.com/v1);4# fails without a key.5client = Hips()6 7result = client.tasks.run(8    deployment="dep_...",9    input={"text": "I was charged twice and nobody has replied."},10    requirements={"pool": "approved", "pricing_mode": "stable"},11)12 13print(result.output.label)       # the model's label, as sent14print(result.usage.units)        # in the model's billing unit15print(result.meta.cost_micros)   # what this request cost16print(result.meta.request_id)
Reads from the environmentHIPS_API_KEYHIPS_BASE_URL

What the SDK wraps

The SDK wraps the HIPS task API, the versioned contract for every model type other than open-weight language models: POST /v1/tasks for synchronous work, POST /v1/jobs with GET /v1/jobs/{id} for asynchronous work, POST /v1/uploads for task inputs, and the read side of deployments and models.

The SDK runs a customer model through its deployment and never imports a model, uploads weights or handles a hub token: the import is the Console's, described on Import and run your model.

For open-weight language models the SDK adds nothing: the OpenAI client is the client, and the SDK's documentation says so rather than wrapping it. A customer who uses both paths holds one key and one base URL; the OpenAI client and the HIPS SDK read the same three environment variables, HIPS_API_KEY, HIPS_BASE_URL and HIPS_MODEL; the base URL is https://ai.hips.com/v1.

What the SDK adds

  • Typed methods per task type with the result shapes the catalog defines.
  • An upload helper that sends an input through POST /v1/uploads above an inline threshold and names the upl_ id.
  • An idempotency-key generated per task and job call, so a retry can never double-bill.
  • Polling of GET /v1/jobs/{id} with backoff and a wait helper.
  • Retries on 429 and 503 honoring Retry-After, and on connection failures before any byte; never on a 400.
  • The error envelope as typed exceptions by type and code.
  • The x-hips-* headers and the streamed hips object as typed fields.
  • The requirement object (pool, pricing mode, region, fallback) as a per-client default and a per-call override; the SDK sends the hips body object and never the headers on the task API.

What the SDK never does

  • No telemetry: nothing is sent that the call does not need.
  • No second network destination, except the upload PUT to the address the API returned, always on a HIPS-controlled host over https.
  • No stored keys: the key is read from an argument or the environment and never written to a file, a keychain or a cache; it is never logged.
  • No caching, no deduplication, no thresholds, no interpretation: a score is returned as sent.
  • No model substitution and no weakened requirement: the SDK sends what it was given; the server rejects what it cannot serve.

One behavior for every language

A language's SDK is released only when it implements the whole specification and passes the whole conformance suite: a language-neutral case file, a mock server for behavior cases, and a smoke test against the hosted API. There are no partial SDKs and no language-only features.

SDK task guides

One guide per task follows, each with the request format, the usage unit and the result handling, in that order. Until the languages are decided, the task guides carry the wire shapes of the task API, which every SDK method maps onto.

Related sheets

  • Python
  • Task guides
  • Import and run your model
  • Tasks reference
Previous sheetMigrate to HIPS
Next sheetPython
Sheet
04 of 13
Updated
2026-10-21
Status
Preview
Join early access

On this sheet

  1. Eight languages, released together
  2. The same task in every language
  3. What the SDK wraps
  4. What the SDK adds
  5. What the SDK never does
  6. One behavior for every language
  7. SDK task guides

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Ü