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. FThinking levels
    7. GData handling
    8. HCompatibility matrix
  3. 21Changelog
Sheet indexOperating guidance

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. FThinking levels
    7. GData handling
    8. HCompatibility matrix
  3. 21Changelog
20
  1. Docs/
  2. Operating guidance/
  3. Thinking levels
(Detail F)
llms.txt

Thinking levels

On this sheet3 sections
  1. Setting it on each route
  2. What a level does on each model
  3. What you are billed

A model that reasons thinks before it answers. How much it thinks is set with one level, the same on every route and every model: OpenAI's reasoning_effort values. HIPS translates the level into what the model you call takes, so you set it once and never need to know each model's own words for it.

F
Fig. 1, sheet 20Operating guidance

The central levels, lowest first

LevelMeaning
noneNo thinking, where the model can turn it off.
minimalAs little as the model allows.
low, medium, highLess or more thinking; medium is the usual default.
xhigh, maxThe most the model allows.
  • Level
    none
    Meaning
    No thinking, where the model can turn it off.
  • Level
    minimal
    Meaning
    As little as the model allows.
  • Level
    low, medium, high
    Meaning
    Less or more thinking; medium is the usual default.
  • Level
    xhigh, max
    Meaning
    The most the model allows.

Every level is accepted on every model, so a valid level is never refused. On a model that does not reason it is accepted and has no effect. A value outside the seven is refused with a 400 invalid_value that names the field.

Setting it on each route

RouteHow to set it
Chat completionsreasoning_effort, one of the seven levels.
Responsesreasoning.effort, one of the seven levels.
Messagesthinking and output_config.effort. thinking: {"type": "disabled"} is none. thinking: {"type": "enabled", "budget_tokens": N} is low for a budget under 4,096 tokens, medium under 16,384 and high above. adaptive, or enabled with no budget, leaves the model at its own level. output_config.effort (low, medium, high or max) is the level itself, and is used over a budget; a disabled thinking is used over both.
  • Route
    Chat completions
    How to set it
    reasoning_effort, one of the seven levels.
  • Route
    Responses
    How to set it
    reasoning.effort, one of the seven levels.
  • Route
    Messages
    How to set it
    thinking and output_config.effort. thinking: {"type": "disabled"} is none. thinking: {"type": "enabled", "budget_tokens": N} is low for a budget under 4,096 tokens, medium under 16,384 and high above. adaptive, or enabled with no budget, leaves the model at its own level. output_config.effort (low, medium, high or max) is the level itself, and is used over a budget; a disabled thinking is used over both.

What a level does on each model

Each model's sheet in the catalog says, under Reasoning, which of these kinds it is. A model with no Reasoning section does not reason, and the level has no effect on it.

KindWhat the level does
LevelsThe model's chat template takes named levels. The level you send goes as the nearest level the model takes; between two equally near, the lower one. A model that takes only low, medium and high is sent high for xhigh or max and low for minimal. none turns thinking off where the model can be turned off; where it cannot, it goes as the model's lowest level, the closest it comes. A level the model has no word for, and that is nearer its own default, leaves it at its default. A model that refuses some levels is never sent one it refuses.
On or offnone turns thinking off. Any other level leaves it on, nothing finer.
Its own levelThe model thinks at its own level. The level is accepted, and nothing of it is promised.
  • Kind
    Levels
    What the level does
    The model's chat template takes named levels. The level you send goes as the nearest level the model takes; between two equally near, the lower one. A model that takes only low, medium and high is sent high for xhigh or max and low for minimal. none turns thinking off where the model can be turned off; where it cannot, it goes as the model's lowest level, the closest it comes. A level the model has no word for, and that is nearer its own default, leaves it at its default. A model that refuses some levels is never sent one it refuses.
  • Kind
    On or off
    What the level does
    none turns thinking off. Any other level leaves it on, nothing finer.
  • Kind
    Its own level
    What the level does
    The model thinks at its own level. The level is accepted, and nothing of it is promised.

On HIPS's data-center capacity in the Certified pool, the level is passed in the form each model there takes it, the nearest it takes; where a model there takes no level, it is accepted and has no effect.

What you are billed

The tokens a model spends thinking are output tokens, billed as completion_tokens (output_tokens on Messages and Responses), whether or not the route returns the thinking: Messages returns none of it. Turning thinking off with none, where the model can turn it off, is how to stop paying for it.

Note

A level is never sent to a model in a form it does not take: it reaches each model as the nearest level that model takes, or not at all.

Related sheets

  • Chat completions reference
  • Messages reference
  • The catalog
Previous sheetStreaming
Next sheetData handling
Sheet
20 of 21
Detail
F
Updated
2026-11-18
Sign in to the Console

On this sheet

  1. Setting it on each route
  2. What a level does on each model
  3. What you are billed

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Ü