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

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

The HIPS SDK for other supported model types

On this sheet6 sections
  1. Eight languages, released together
  2. What the SDK wraps
  3. What the SDK adds
  4. What the SDK never does
  5. One behavior for every language
  6. 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.

Note

No SDK is published yet. No install command, package name or method appears here until the package names are decided and every SDK passes the shared conformance suite Not decided yet; then each language gets its page. Swift, Kotlin-native and Dart get a page only if they ship. Until then, open-weight language models work through the OpenAI client, as the Quickstart shows.

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/uploads for task inputs, and the read side of deployments and models. Asynchronous work will go through the job routes (POST /v1/jobs and GET /v1/jobs/{id}), which the API does not serve yet: today they answer 404 route_not_found.

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

  • Task guides
  • Import and run your model
  • Tasks reference
Previous sheetMigrate to HIPS
Next sheetImport and run your model
Sheet
04 of 20
Updated
2026-11-11
Sign in to the Console

On this sheet

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

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Ü