Resources

The Docs landing page: what the API is intended to be, and how to follow its progress.

The intended setup for a supported chat-completion model using familiar clients, in Python, JavaScript, or cURL.

Check the features your application uses, test quality and operating behavior, and move deliberately.

The intended path for image, video, audio, and specialist models such as classifiers.

From a model on Hugging Face to inference: import, compatibility checks, profiling, pool choice, and policies.

What each model accepts, returns, and costs, and each task's request format, usage units, and result handling.

Per task, the request format, the usage unit and the result handling, in that order.

Supported configurations for coding tools, each validated separately before it is listed as supported.

Send many requests at once, run them when capacity is free at half the on-demand price, and collect the results when they are done.

Automatic prompt caching: cached input tokens at their own lower rate, no write charge, isolated per workspace.

hi, the HIPS command line for buyers: sign-in, models, batches, imports, keys and usage, with no API key.

The HIPS inference API routes, parameters, headers, errors, and usage fields, generated from the contract.

Limits, errors, retries and billing outcomes, idempotency, streaming, data handling, and the compatibility matrix.

Dated entries, newest first, each naming the pages changed. The docs are versioned by date; the API is versioned by its path.

The agreement between HIPS and everyone who buys inference from HIPS, whether a business or a consumer.

What personal data HIPS collects, why, who receives it, how long it is kept, and the rights you have.

The rules on what may and may not be done with the HIPS Services, binding every Buyer, Member, Provider and Program Partner, what HIPS checks and when, and how HIPS enforces the rules and hears reports of abuse.

The terms on which HIPS processes personal data on behalf of a business customer when it answers that customer's Requests, as Article 28 of the GDPR requires.

The agreement under which HIPS buys GPU Time from the people and organizations whose computers supply it, and settles and pays for that GPU Time.

The agreement under which people who hold a HIPS Account promote HIPS to people who are new to it through their own referral link and code, and under which HIPS pays them commissions for the referrals that qualify.

The clauses every HIPS agreement shares, written once and incorporated word for word by the Terms of Service, the Provider Agreement, the Affiliate Program Agreement and the Acceptable Use Policy.

How HIPS uses the email address and the answers you give when you register your interest in early access or send HIPS an inquiry, how long it keeps them, and how you withdraw.

Which cookies and browser storage hips.com and console.hips.com use, why, for how long, and how you make and change your choice.

How long the face captures and biometric data of the automated face check are kept, how they are permanently destroyed, and what HIPS does if an incident may compromise them.

What consumer health data HIPS collects under the Washington My Health My Data Act and Nevada Senate Bill 370, why, who receives it, and how you exercise your rights, including deletion.

The terms on which anyone may use the HIPS website at hips.com, with or without an Account.

How to report a security vulnerability in HIPS's systems and software, what is in scope, the rules for research, and HIPS's commitment not to act against good-faith research.

The model form a Consumer may use to withdraw from a contract with HIPS within the withdrawal period.

A short summary of HIPS and its pages, for AI tools.

The full text of the site, for AI tools.

Where to report a security issue.