An AI inference API for developers
Familiar code.
A new inference network.
For open-weight language models, we’re designing HIPS to work with familiar coding tools and supported provider-style client SDKs, starting with OpenAI-style integrations.
Connect your client with a HIPS API key, base URL, and supported model ID, and let HIPS coordinate the GPU capacity behind each request.
import osfrom openai import OpenAI client = OpenAI( api_key=os.environ["HIPS_API_KEY"], base_url=os.environ["HIPS_BASE_URL"], # https://ai.hips.com/v1)result = client.chat.completions.create( model=os.environ["HIPS_MODEL"], messages=[{"role": "user", "content": "Explain GPU inference in two sentences."}],)print(result.choices[0].message.content)Guides and reference
- 05Import and run your modelFrom a model on Hugging Face to inference: import, compatibility checks, profiling, pool choice, and policies.Hugging FacePreview
- 07Batch jobsSend many requests at once, run them when capacity is free at half the on-demand price, and collect the results when they are done.POST /v1/batchesPreview
- 08Prompt cachingAutomatic prompt caching: cached input tokens at their own lower rate, no write charge, isolated per workspace.cached_tokensPreview
- 10Command linehi, the HIPS command line for buyers: sign-in, models, batches, imports, keys and usage, with no API key.hi loginPreview
- 11API referenceThe HIPS inference API routes, parameters, headers, errors, and usage fields, generated from the contract./v1/chat/completionsPreview
- 12Operating guidanceLimits, errors, retries and billing outcomes, idempotency, streaming, data handling, and the compatibility matrix.Retry-AfterPreview
These developer pages preview the intended experience. Credentials, endpoint addresses, the model catalog, and compatibility details will be supplied with access.
Follow examples in Python, JavaScript, or cURL. Test a small request, inspect the result and usage, then build around the model’s supported features.
The goal is a familiar integration path with clear boundaries. Model behavior, available parameters, and supported endpoints will be documented explicitly. HIPS will not host OpenAI’s proprietary models simply because it uses a compatible request style.
We also want developers to use HIPS with coding tools, including Claude Code where compatibility can be established. Each tool needs its own supported configuration and tested behavior.
An intended setup helper will guide configuration for supported tools. Tool-specific instructions will explain what changes, how credentials are handled, and how to restore the previous setup.
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.
Two integration paths, never mixed on one page. A client guide documents only the OpenAI-compatible routes and only language models; an SDK guide documents only the task API and the model types it serves.
| Work | Path | Where to read |
|---|---|---|
| Open-weight language models from the catalog, and customer-owned language models in supported architectures | A provider-style OpenAI client with a HIPS key, the base URL https://ai.hips.com/v1 and a model or deployment id | Quickstart, Migrate to HIPS, Chat completions |
| Every other supported model type (image, video, audio, classifiers and other specialist models), and customer-owned models of those types | The HIPS SDK over the task API: tasks, jobs, uploads | HIPS SDK, Task guides, Tasks |
- Work
- Open-weight language models from the catalog, and customer-owned language models in supported architectures
- Path
- A provider-style OpenAI client with a HIPS key, the base URL
https://ai.hips.com/v1and a model or deployment id - Where to read
- Quickstart, Migrate to HIPS, Chat completions
- Work
- Every other supported model type (image, video, audio, classifiers and other specialist models), and customer-owned models of those types
- Path
- The HIPS SDK over the task API: tasks, jobs, uploads
- Where to read
- HIPS SDK, Task guides, Tasks
Related sheets
- Sheet
- 01 of 13
- Updated
- 2026-10-21
- Status
- Preview