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 indexAPI reference

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
18
  1. Docs/
  2. API reference/
  3. Usage
(Detail T)
llms.txt

Usage

On this sheet4 sections
  1. The usage object on chat completions
  2. The usage object on tasks
  3. Units per task
  4. The usage record

Usage is counted in the model's billing unit and reported on every answered request. Money is never in usage: the cost is x-hips-cost-micros, or on a streamed answer the hips object of the final usage chunk, and the usage record.

F
Fig. 1, sheet 18API reference

The usage object on chat completions

usage

00000000000000000000000000000000000000001{"usage": {"prompt_tokens": 0, "completion_tokens": 0, "total_tokens": 0, "prompt_tokens_details": {"cached_tokens": 0}, "completion_tokens_details": {"reasoning_tokens": 0}}}
usage sample
  1. 01
    prompt_tokens, completion_tokens

    Counted by the serving engine's tokenizer for the pinned model. These are the billable units at the model's separate input and output rates.

  2. 02
    total_tokens

    The sum; not a billing unit.

  3. 03
    prompt_tokens_details.cached_tokens

    0 on every answer today: HIPS keeps no prompt cache yet, so every input token is billed at the input rate (Prompt caching).

  4. 04
    prompt_tokens_details.cache_write_tokens

    Always 0: writing a cache costs nothing.

  5. 05
    completion_tokens_details.reasoning_tokens

    On models advertising reasoning; counted inside completion_tokens.

The usage object on tasks

usage

00000000000000000000000000000000000000001{"usage": {"units": 2, "unit": "classification", "billed_units": 1}}
usage sample

unit names the task's unit. On a classification units counts the inputs and billed_units the inputs that were answered. On an embedding or a rerank the unit is second: units and billed_units are the started seconds of the request's compute time, at least one, and input_tokens the tokens the gateway counted with the model's own tokenizer, a figure that is never the bill (H109, decided 2026-11-05). POST /v1/embeddings keeps OpenAI's usage (prompt_tokens, total_tokens), and POST /v1/rerank says the same in Cohere's meta.billed_units.seconds and meta.tokens.input_tokens. On an image task the unit is image: units counts the images asked and billed_units the images delivered, each billed at the model's price for its size (Image generation and editing); OpenAI's image routes answer no usage, and the cost is x-hips-cost-micros.

Units per task

TaskUnitWhat is countedPriced now
chat (chat completions, Responses, Messages)tokensInput and output tokens at separate rates; cached input at its own rate, though no cached token is billed todayYes
classificationclassificationOne item evaluated once under the task's input conditions is one classification, priced per 1,000Yes
embeddingsecondStarted seconds of the request's compute time, at least one (H109, decided 2026-11-05). The tokens counted are a figure only, never the billYes
reranksecondStarted seconds of the request's compute time, at least one (H109); every document is scored, whatever top_n returnsYes
detectiondetectionDetectionsNo: not served until priced
transcription, translationaudio_secondSeconds of input audioNo: not served until priced
speechcharacterInput charactersNo: not served until priced
image_generation, image_editimageOutput images delivered, each at the model's fixed price for its size; an image the content checks withhold is not billed (Image generation and editing)Yes
video_generationvideo_secondSeconds of output videoNo: not served until priced
  • Task
    chat (chat completions, Responses, Messages)
    Unit
    tokens
    What is counted
    Input and output tokens at separate rates; cached input at its own rate, though no cached token is billed today
    Priced now
    Yes
  • Task
    classification
    Unit
    classification
    What is counted
    One item evaluated once under the task's input conditions is one classification, priced per 1,000
    Priced now
    Yes
  • Task
    embedding
    Unit
    second
    What is counted
    Started seconds of the request's compute time, at least one (H109, decided 2026-11-05). The tokens counted are a figure only, never the bill
    Priced now
    Yes
  • Task
    rerank
    Unit
    second
    What is counted
    Started seconds of the request's compute time, at least one (H109); every document is scored, whatever top_n returns
    Priced now
    Yes
  • Task
    detection
    Unit
    detection
    What is counted
    Detections
    Priced now
    No: not served until priced
  • Task
    transcription, translation
    Unit
    audio_second
    What is counted
    Seconds of input audio
    Priced now
    No: not served until priced
  • Task
    speech
    Unit
    character
    What is counted
    Input characters
    Priced now
    No: not served until priced
  • Task
    image_generation, image_edit
    Unit
    image
    What is counted
    Output images delivered, each at the model's fixed price for its size; an image the content checks withhold is not billed (Image generation and editing)
    Priced now
    Yes
  • Task
    video_generation
    Unit
    video_second
    What is counted
    Seconds of output video
    Priced now
    No: not served until priced

The embeddings and rerank routes are on Embeddings and rerank. A task type with no price kind is not served until it is priced. Every setting that changes the charge is a named parameter of the task's request, is shown in the Playground beside the measured usage, and is carried in the quote. The unit is set per model in the catalog.

A request sent to a router is billed exactly as the model the router chose, at that model's quote, rates, pool and units, with no router fee (what it costs).

The usage record

One per request. It holds the request id, timestamps (received, accepted, first byte, completed), the key, the workspace, the pinned id, the deployment if any, task, pool, lane, pricing mode, region, the quote, units in and out, the rate version, the cost, the outcome (completed, failed, canceled, interrupted), the error code if any, the attempt count, latency, the client's address and user agent for abuse control, and the sizes of the body and the output; under a router, the router, its preference and how it chose. It holds no prompt, no input, no output. The Console's Usage and activity view shows and exports it.

Related sheets

  • Requirements and headers
  • Pricing
Previous sheetErrors
Next sheetVersioning
Sheet
18 of 20
Detail
T
Updated
2026-11-16
Sign in to the Console

On this sheet

  1. The usage object on chat completions
  2. The usage object on tasks
  3. Units per task
  4. The usage record

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Ü