Skip to content
HIPS
  • Earn with your GPU
  • Pricing
  • Docs
Sign inJoin early access
⌘K

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Security
    1. AChoose a pool for your data
    2. BCoding agents and prompt injection
    3. CWhat a Community pool provider can see
    4. DWhat HIPS stores
    5. EKnowledge and RAG data
  4. 04Migrate to HIPS

Guides

  1. 05HIPS SDK
  2. 06Import and run your model
  3. 07Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 08Batch jobs
  5. 09Prompt caching
  6. 10Code with HIPS
  7. 11Coding-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. 12Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 13Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 14Billing
  11. 15Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 16Semantic routing
  13. 17Guardrails
  14. 18Knowledge

Reference

  1. 19API 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. 20Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 21Changelog
Sheet indexSecurity

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Security
    1. AChoose a pool for your data
    2. BCoding agents and prompt injection
    3. CWhat a Community pool provider can see
    4. DWhat HIPS stores
    5. EKnowledge and RAG data
  4. 04Migrate to HIPS

Guides

  1. 05HIPS SDK
  2. 06Import and run your model
  3. 07Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 08Batch jobs
  5. 09Prompt caching
  6. 10Code with HIPS
  7. 11Coding-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. 12Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 13Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 14Billing
  11. 15Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 16Semantic routing
  13. 17Guardrails
  14. 18Knowledge

Reference

  1. 19API 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. 20Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 21Changelog
03
  1. Docs/
  2. Security/
  3. Choose a pool for your data
(Detail A)
llms.txt

Choose a pool for your data

On this sheet6 sections
  1. The short rule
  2. Which pool for your work
  3. By kind of work
  4. Set the pool
  5. What HIPS protects in the Community pool
  6. Keep a request in one region

Anything sensitive goes to the Certified pool. Find your work below.

The short rule

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.

Which pool for your work

01

What are you building?

Pick the closest.

Agents and tools

Chat and text

Other kinds of models

02

What is in the requests?

Choose the most sensitive thing any request will hold.

Your pool: the Certified pool. The reason and the code are below.
03

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 facilities

If 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.

Install$ pip install openai
00000000000000000000000000000000000000001import os2from openai import OpenAI3 4client = OpenAI(5    api_key=os.environ["HIPS_API_KEY"],6    base_url="https://ai.hips.com/v1",7    # Sensitive data, or not sure: the Certified pool8    default_headers={"x-hips-pool": "certified"},9)10result = client.chat.completions.create(11    model=os.environ["HIPS_MODEL"],12    messages=[{"role": "user", "content": "Summarize this customer's last three orders."}],13)14print(result.choices[0].message.content)
Reads from the environmentHIPS_API_KEYHIPS_MODEL

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).

By kind of work

WorkPoolWhy
Coding agents, and any request with tool callsCertified pool, always. HIPS enforces this; you cannot send it to the Community poolBecause 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 poolPersonal data always goes to the Certified pool
Business documents, contracts, source code, financial information, credentialsCertified poolIf 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 sensitiveCommunity pool, for a lower priceThe 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 sensitiveCommunity pool, for a lower price, as these kinds are servedToday 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 poolSee Knowledge and RAG data
Anything you are unsure aboutCertified poolWe 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/models and 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

Set the pool

WhereHowWhat it covers
In a requestThe 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 idOn 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 keyIts Pool in the Console (API keys)Every request of the key that names no pool
For signed-in toolsThe 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 workspaceExclude 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-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)
    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 :certified or :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 hi 0.1.7, a coding agent hi starts 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).

What HIPS protects in the Community pool

  • 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.

Keep a request in one region

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

  • Requirements and headers
  • Guardrails
Previous sheetSecurity at HIPS
Next sheetCoding agents and prompt injection
Sheet
03 of 21
Detail
A
Updated
2026-11-18
Sign in to the Console

On this sheet

  1. The short rule
  2. Which pool for your work
  3. By kind of work
  4. Set the pool
  5. What HIPS protects in the Community pool
  6. Keep a request in one region

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Ü