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

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Migrate to HIPS

Guides

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

Reference

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

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Migrate to HIPS

Guides

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

Reference

  1. 18API 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. 19Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 20Changelog
03
  1. Docs/
  2. Migrate to HIPS
llms.txt

Move your inference API to HIPS

On this sheet4 sections
  1. Check what your application uses
  2. Test quality and operating behavior
  3. Move deliberately
  4. Where HIPS differs by design

Keep the client patterns you know. For supported OpenAI-style integrations, the intended starting point is three settings: your HIPS API key, base URL, and model.

Our migration guide will help you choose a model, check the features your application uses, and compare results before moving traffic.

Familiar tools, with a new inference network behind them.

Fig. 1, sheet 03Migrate to HIPS

Check what your application uses

Review the endpoints, parameters, response fields, streaming behavior, structured outputs, and tool calls your application depends on. A shared client format does not mean every provider feature or model behavior is identical.

For image, audio, video, and specialist tasks, follow the relevant task guide. Some workflows may require asynchronous jobs or a different request shape.

Note

The compatibility matrix is required before migration is encouraged. Every row is unvalidated at launch, so the matrix is empty of supported rows until then.

Test quality and operating behavior

Start with a small representative set of inputs. Compare output usefulness, errors, latency, and measured cost. Confirm the applicable data-use policy and execution requirements.

Add streaming, concurrency, and failure handling after the simplest request works. Follow the documented rate limits and retry rules, including how charges are handled. Do not assume that every failed or retried attempt has the same billing outcome.

The rules are on Retries and billing outcomes and Data handling.

Move deliberately

Keep your existing configuration recoverable. Begin with limited traffic and use the Console to understand results and usage. Expand after the integration and selected models meet your requirements.

Where HIPS differs by design

Three settings move; three things do not behave as a drop-in. Nothing is silently dropped: a field that would change the output or the bill and that the named model cannot honor is a 400, never ignored. Nothing is silently substituted: the model served is the model named. A requirement is never weakened to make a request succeed.

WhereOpenAI's behaviorHIPS
Unknown modelinvalid_request_error404 not_found_error, code model_not_found
Rate limittype carries the dimensionrate_limit_error with the dimension in param
nSeveral answers per request1 only: one quote, one line on the bill
store, metadataAccepted400 stateful_not_supported: the gateway stores no bodies
Completion idA completion idThe request id, req_...
ExtrasIn the bodyIn x-hips-* headers, and in the hips object of a stream's final usage chunk
  • Where
    Unknown model
    OpenAI's behavior
    invalid_request_error
    HIPS
    404 not_found_error, code model_not_found
  • Where
    Rate limit
    OpenAI's behavior
    type carries the dimension
    HIPS
    rate_limit_error with the dimension in param
  • Where
    n
    OpenAI's behavior
    Several answers per request
    HIPS
    1 only: one quote, one line on the bill
  • Where
    store, metadata
    OpenAI's behavior
    Accepted
    HIPS
    400 stateful_not_supported: the gateway stores no bodies
  • Where
    Completion id
    OpenAI's behavior
    A completion id
    HIPS
    The request id, req_...
  • Where
    Extras
    OpenAI's behavior
    In the body
    HIPS
    In x-hips-* headers, and in the hips object of a stream's final usage chunk

Related sheets

  • Explore the Quickstart
  • Compatibility matrix
  • Retries and billing outcomes
  • Data handling
Previous sheetQuickstart
Next sheetHIPS SDK
Sheet
03 of 20
Updated
2026-11-11
Sign in to the Console

On this sheet

  1. Check what your application uses
  2. Test quality and operating behavior
  3. Move deliberately
  4. Where HIPS differs by design

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Ü