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 indexOperating guidance

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
19
  1. Docs/
  2. Operating guidance/
  3. Idempotency
(Detail D)
llms.txt

Idempotency

idempotency-key is accepted on POST /v1/tasks, POST /v1/embeddings and POST /v1/rerank, and, where they are offered, on POST /v1/uploads, POST /v1/files, POST /v1/batches and POST /v1/batches/{batch_id}/cancel; its value is the client's, up to a length Not decided yet, scoped to the key. A replay of an upload, a file or a batch carries idempotent-replayed: true. The SDK generates one per task call.

F
Fig. 1, sheet 19Operating guidance
RuleBehavior
First requestServed; the key, a keyed hash of the body and the requirement headers, and the request's state are kept for the window Not decided yet. No answer is kept
Same key, same body, after a task, embeddings or rerank request completed404 result_expired, its message naming the first request's req_ id. Nothing runs, nothing is billed again
Same key, different body400 idempotency_key_reused
Same key while the first is still being answered400 idempotency_in_progress
A replay of an upload, a file or a batchAnswers the object as it now is, read from its record, with idempotent-replayed: true; a replayed file upload stores nothing twice
Not on chat completions, Responses or MessagesPOST /v1/chat/completions, /v1/responses and /v1/messages take no idempotency-key: a replay would need the gateway to store a completion body, which it never does. A retried completion is a new request, a new quote and a new charge
  • Rule
    First request
    Behavior
    Served; the key, a keyed hash of the body and the requirement headers, and the request's state are kept for the window Not decided yet. No answer is kept
  • Rule
    Same key, same body, after a task, embeddings or rerank request completed
    Behavior
    404 result_expired, its message naming the first request's req_ id. Nothing runs, nothing is billed again
  • Rule
    Same key, different body
    Behavior
    400 idempotency_key_reused
  • Rule
    Same key while the first is still being answered
    Behavior
    400 idempotency_in_progress
  • Rule
    A replay of an upload, a file or a batch
    Behavior
    Answers the object as it now is, read from its record, with idempotent-replayed: true; a replayed file upload stores nothing twice
  • Rule
    Not on chat completions, Responses or Messages
    Behavior
    POST /v1/chat/completions, /v1/responses and /v1/messages take no idempotency-key: a replay would need the gateway to store a completion body, which it never does. A retried completion is a new request, a new quote and a new charge

How to use it

  • Generate the key before the first attempt and reuse it on every retry of the same body.
  • Treat a 400 idempotency_in_progress as a signal to wait and retry with the same key, not as a failure.
  • A different body with the same key is a 400 idempotency_key_reused: a bug in the caller, never retried.
  • A task, embeddings or rerank request that completed is never answered again: a retry with its key answers 404 result_expired, naming the first request's req_ id, so keep the answer you received.
  • A replay of an upload, a file or a batch carries the original x-hips-request-id, so the Console shows one request and one charge.

Related sheets

  • Tasks reference
  • Retries and billing outcomes
Previous sheetRetries and billing outcomes
Next sheetStreaming
Sheet
19 of 20
Detail
D
Updated
2026-11-14
Sign in to the Console

On this sheet

  1. How to use it

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Ü