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. Retries and billing outcomes
(Detail C)
llms.txt

Retries and billing outcomes

On this sheet2 sections
  1. Timeouts
  2. Client guidance

Note

Do not assume that every failed or retried attempt has the same billing outcome.

The principle: the customer is charged once per completed answer, at the quote bound at acceptance. A failed, rejected, interrupted or timed-out attempt costs the customer nothing; what the provider is paid for it is defined independently. The outcomes below are proposals until decided Not decided yet, except where the rule is the company's.

F
Fig. 1, sheet 19Operating guidance
SituationWho retriesBilling outcome
429 or 503The client, after Retry-After; the SDK does itNothing on the refusal; the retry is a new quote (market) or the same stable price
An attempt is rejected or interrupted before any outputThe scheduler, on another eligible worker under the same requirements, up to Not decided yet attemptsNothing until a completed answer; then once
An attempt is interrupted after the first streamed tokenNobody: a stream cannot be restarted transparently. The stream ends with the error envelopeProposed: nothing (no complete answer); the tokens delivered are in the usage record as interrupted
An attempt is interrupted after the first token on a non-streamed requestThe scheduler, within the attempt countOnce, for the completed answer
Retries exhaustedNobody; 500 attempt_failed or job interruptedNothing
A worker timed outThe scheduler, once, on another worker, when the timeout was the worker'sNothing
The client closes a streamNobody; the job is canceled on the workerNot decided yet (proposed: the tokens delivered are charged)
The client cancels a queued jobNobodyNothing
The client cancels a running jobNobodyNot decided yet (proposed: nothing)
A market price changes while a job runsNobodyThe bound quote applies to work already accepted
A retried request with the same idempotency-keyThe idempotency rulesOnce
  • Situation
    429 or 503
    Who retries
    The client, after Retry-After; the SDK does it
    Billing outcome
    Nothing on the refusal; the retry is a new quote (market) or the same stable price
  • Situation
    An attempt is rejected or interrupted before any output
    Who retries
    The scheduler, on another eligible worker under the same requirements, up to Not decided yet attempts
    Billing outcome
    Nothing until a completed answer; then once
  • Situation
    An attempt is interrupted after the first streamed token
    Who retries
    Nobody: a stream cannot be restarted transparently. The stream ends with the error envelope
    Billing outcome
    Proposed: nothing (no complete answer); the tokens delivered are in the usage record as interrupted
  • Situation
    An attempt is interrupted after the first token on a non-streamed request
    Who retries
    The scheduler, within the attempt count
    Billing outcome
    Once, for the completed answer
  • Situation
    Retries exhausted
    Who retries
    Nobody; 500 attempt_failed or job interrupted
    Billing outcome
    Nothing
  • Situation
    A worker timed out
    Who retries
    The scheduler, once, on another worker, when the timeout was the worker's
    Billing outcome
    Nothing
  • Situation
    The client closes a stream
    Who retries
    Nobody; the job is canceled on the worker
    Billing outcome
    Not decided yet (proposed: the tokens delivered are charged)
  • Situation
    The client cancels a queued job
    Who retries
    Nobody
    Billing outcome
    Nothing
  • Situation
    The client cancels a running job
    Who retries
    Nobody
    Billing outcome
    Not decided yet (proposed: nothing)
  • Situation
    A market price changes while a job runs
    Who retries
    Nobody
    Billing outcome
    The bound quote applies to work already accepted
  • Situation
    A retried request with the same idempotency-key
    Who retries
    The idempotency rules
    Billing outcome
    Once

Timeouts

All open Not decided yet: the synchronous request limit on chat completions and tasks; the idle limit between streamed tokens; the per-task maximum run time of a job; the worker's own limits. A request refused before it starts because it cannot fit is a 400 use_jobs or a 503, never a wait until the limit.

Client guidance

  • Retry 429 and 503 after Retry-After.
  • Retry a connection failure before any byte was received.
  • Retry a 500 once.
  • Never retry a 400, 401, 402, 403 or 404 unchanged.
  • On the task API send an idempotency-key so a retry can never double-bill.
  • A retried chat completion is a new request, a new quote and a new charge: the route takes no idempotency key, because the gateway stores no completion body.

Related sheets

  • Idempotency
  • Errors
Previous sheetErrors
Next sheetIdempotency
Sheet
19 of 20
Detail
C
Updated
2026-10-21
Sign in to the Console

On this sheet

  1. Timeouts
  2. Client guidance

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Ü