Choose a pool for your data
Anything sensitive goes to the Certified pool. Find your work below.
If you are a business and you send any sensitive data at all, such as personal data (PII), use the Certified pool. Use the Community pool when you just need GPUs and the data is not sensitive.
Recommended
If you are unsure, choose the Certified pool. We always recommend it: it is certified, it retains none of your data, and it has the normal prices.
What are you building?
Pick the closest.
What is in the requests?
Choose the most sensitive thing any request will hold.
Your pool
Your pool: the Certified pool. You are not sure yet, so: the Certified pool. We always recommend it if you are unsure.
For: Not sure yet, not sure. Change your answers above
Use the Certified pool
Certified facilitiesIf it holds nothing sensitive, choose Nothing sensitive above to run it in the Community pool for a lower price.
You are not sure yet, so: the Certified pool. We always recommend it if you are unsure.
What HIPS guarantees here
- Every facility is certified by HIPS's compliance team, and HIPS guarantees that certification for every request here.
- The facility retains none of your data, and HIPS does not store, log or train on it.
Name the pool: a request that names no pool, on a key that names none, runs under Auto, which may choose either pool.
pip install openaiimport osfrom openai import OpenAI client = OpenAI( api_key=os.environ["HIPS_API_KEY"], base_url="https://ai.hips.com/v1", # Sensitive data, or not sure: the Certified pool default_headers={"x-hips-pool": "certified"},)result = client.chat.completions.create( model=os.environ["HIPS_MODEL"], messages=[{"role": "user", "content": "Summarize this customer's last three orders."}],)print(result.choices[0].message.content)Or end the model id in :certified on chat completions, Responses and Messages, with no header (A pool in the model id).
Set HIPS_MODEL to a model the pool offers: GET /v1/models lists each model's pools.
To set it once: a key's Pool, Tool defaults for signed-in tools, or Exclude the Community pool for a whole workspace (Set the pool).
| Work | Pool | Why |
|---|---|---|
| Coding agents, and any request with tool calls | Certified pool, always. HIPS enforces this; you cannot send it to the Community pool | Because of the risk of prompt injection: the answer runs commands and edits files on your computer |
| Customer support chat, or anything else that holds personal data (PII) | Certified pool | Personal data always goes to the Certified pool |
| Business documents, contracts, source code, financial information, credentials | Certified pool | If you are a business and you send any sensitive data at all, use the Certified pool |
| A chat for fun with no personal data, public content, test data, or a low-cost project on data that is not sensitive | Community pool, for a lower price | The content is harmless if seen, and the provider never learns who sent it |
| Image generation, text-to-speech, speech-to-text, classifiers and ONNX models, on data that is not sensitive | Community pool, for a lower price, as these kinds are served | Today HIPS serves chat on open-weight language models, listed in GET /v1/models and on Models. The same kinds with sensitive data: Certified pool |
| Embeddings and Knowledge (RAG) | Sensitive content: Certified pool. Other content: either pool | See Knowledge and RAG data |
| Anything you are unsure about | Certified pool | We always recommend it if you are unsure |
- Work
- Coding agents, and any request with tool calls
- Pool
- Certified pool, always. HIPS enforces this; you cannot send it to the Community pool
- Why
- Because of the risk of prompt injection: the answer runs commands and edits files on your computer
- Work
- Customer support chat, or anything else that holds personal data (PII)
- Pool
- Certified pool
- Why
- Personal data always goes to the Certified pool
- Work
- Business documents, contracts, source code, financial information, credentials
- Pool
- Certified pool
- Why
- If you are a business and you send any sensitive data at all, use the Certified pool
- Work
- A chat for fun with no personal data, public content, test data, or a low-cost project on data that is not sensitive
- Pool
- Community pool, for a lower price
- Why
- The content is harmless if seen, and the provider never learns who sent it
- Work
- Image generation, text-to-speech, speech-to-text, classifiers and ONNX models, on data that is not sensitive
- Pool
- Community pool, for a lower price, as these kinds are served
- Why
- Today HIPS serves chat on open-weight language models, listed in
GET /v1/modelsand on Models. The same kinds with sensitive data: Certified pool
- Work
- Embeddings and Knowledge (RAG)
- Pool
- Sensitive content: Certified pool. Other content: either pool
- Why
- See Knowledge and RAG data
- Work
- Anything you are unsure about
- Pool
- Certified pool
- Why
- We always recommend it if you are unsure
| Where | How | What it covers |
|---|---|---|
| In a request | The x-hips-pool header on the OpenAI-compatible routes and on Messages, or the hips.pool field on the task API: auto, community or certified (Requirements and headers) | That request. It beats the key's default |
| In the model id | On chat completions, Responses and Messages, end the model id in :certified or :community (A pool in the model id) | That request, in that pool alone, with no fallback |
| On an API key | Its Pool in the Console (API keys) | Every request of the key that names no pool |
| For signed-in tools | The workspace's Tool defaults (Workspace settings). From hi 0.1.7, a coding agent hi starts runs in the Certified pool alone, whatever they say (Coding agents) | hi, HIPS Code and HIPS Provider in the workspace |
| For a whole workspace | Exclude the Community pool, for an owner or admin (Workspace settings) | Every new request and batch runs in the Certified pool, with fallback off |
- Where
- In a request
- How
- The
x-hips-poolheader on the OpenAI-compatible routes and on Messages, or thehips.poolfield on the task API:auto,communityorcertified(Requirements and headers) - What it covers
- That request. It beats the key's default
- Where
- In the model id
- How
- On chat completions, Responses and Messages, end the model id in
:certifiedor:community(A pool in the model id) - What it covers
- That request, in that pool alone, with no fallback
- Where
- On an API key
- How
- Its Pool in the Console (API keys)
- What it covers
- Every request of the key that names no pool
- Where
- For signed-in tools
- How
- The workspace's Tool defaults (Workspace settings). From
hi0.1.7, a coding agenthistarts runs in the Certified pool alone, whatever they say (Coding agents) - What it covers
hi, HIPS Code and HIPS Provider in the workspace
- Where
- For a whole workspace
- How
- Exclude the Community pool, for an owner or admin (Workspace settings)
- What it covers
- Every new request and batch runs in the Certified pool, with fallback off
A request that names no pool takes its key's default pool, and Auto where the key sets none: Auto runs the request wherever HIPS has capacity for the model now, in the Certified or the Community pool, among the pools the workspace and its guardrails allow (Pools). A value in the request beats the key's default, and the key's default beats the platform default (Request requirements). To be sure a request stays in the Certified pool, name it.
The answer's x-hips-pool header names the pool that ran it. If the named pool has no capacity for the model now, the request answers 503 pool_unavailable with Retry-After; it never moves to the other pool unless you turn fallback on (Requirements and headers).
- Your identity: a provider never learns who sent a request.
- Keys and secrets: before a request reaches a GPU a provider owns, HIPS recognizes and redacts API keys, tokens, private keys and the values of environment variables in its text.
- What you mask: with Guardrails you can also mask email addresses, phone numbers, names and other customer information before any model sees them. The checks read text only: images and files are not scanned.
- Tests, encryption and attestation: HIPS runs thousands of different tests on the Community pool's GPUs, every connection is encrypted, and models are signed by HIPS and verified before they load.
None of this can be guaranteed in the Community pool: the GPUs are out in the wild, as with anything on the internet, and the owner of the GPU that processes a request could in theory see or alter it. For anything sensitive, use the Certified pool. Read What a Community pool provider can see.
In either pool, you can keep a request to one region, for example only the EU or only the US. Knowledge is the exception: a knowledge base is stored and searched in the European Union (Ireland), whatever region its requests are kept to (Knowledge).
Related sheets
- Sheet
- 03 of 21
- Detail
- A
- Updated
- 2026-11-18