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
    1. APython
    2. BTypeScript and JavaScript
    3. CGo
    4. DRust
    5. EJava
    6. F.NET
    7. GPHP
    8. HRuby
  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. 09Coding-tool setup
    1. AClaude Code
    2. BOther coding tools and editor integrations
  7. 10Command line
    1. ASign in

Reference

  1. 11API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DModels
    5. ETasks
    6. FJobs
    7. GUploads
    8. HDeployments
    9. IRequirements and headers
    10. JErrors
    11. KUsage
    12. LVersioning
  2. 12Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 13Changelog
Sheet indexAPI reference

Get started

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

Guides

  1. 04HIPS SDK
    1. APython
    2. BTypeScript and JavaScript
    3. CGo
    4. DRust
    5. EJava
    6. F.NET
    7. GPHP
    8. HRuby
  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. 09Coding-tool setup
    1. AClaude Code
    2. BOther coding tools and editor integrations
  7. 10Command line
    1. ASign in

Reference

  1. 11API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DModels
    5. ETasks
    6. FJobs
    7. GUploads
    8. HDeployments
    9. IRequirements and headers
    10. JErrors
    11. KUsage
    12. LVersioning
  2. 12Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 13Changelog
11
  1. Docs/
  2. API reference/
  3. Usage
(Detail K)

PreviewNot yet validated. Join early access

llms.txt

Usage

On this sheet4 sections
  1. The usage object on chat completions
  2. The usage object on tasks and jobs
  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 11API 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

    Reported where the engine reports prefix-cache hits; otherwise 0. A cached prompt token is billed at the model's cached-input rate (Prompt caching).

  4. 04
    completion_tokens_details.reasoning_tokens

    On models advertising reasoning; counted inside completion_tokens.

The usage object on tasks and jobs

usage

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

units counts the inputs, unit names the task's unit, billed_units the inputs that were answered. On a job, usage is null until the job is completed.

Units per task

TaskBilling unitWhat is counted
chatinput_output_tokensprompt_tokens and completion_tokens, at separate input and output rates
classificationper_1000_classificationsunits and billed_units in the task's usage; one item evaluated once under the task's input conditions is one classification
image_generation, image_editper_imagePer output image at a stated dimension band, and per step where the model exposes steps
video_generationper_secondPer second of output video at a stated resolution and frame rate
transcription, translationper_minutePer minute of input audio
speechper_1000_characters or per_secondPer 1,000 input characters, or per second of output audio where the model's cost follows the output
embeddinginput_output_tokensInput tokens; no output rate
  • Task
    chat
    Billing unit
    input_output_tokens
    What is counted
    prompt_tokens and completion_tokens, at separate input and output rates
  • Task
    classification
    Billing unit
    per_1000_classifications
    What is counted
    units and billed_units in the task's usage; one item evaluated once under the task's input conditions is one classification
  • Task
    image_generation, image_edit
    Billing unit
    per_image
    What is counted
    Per output image at a stated dimension band, and per step where the model exposes steps
  • Task
    video_generation
    Billing unit
    per_second
    What is counted
    Per second of output video at a stated resolution and frame rate
  • Task
    transcription, translation
    Billing unit
    per_minute
    What is counted
    Per minute of input audio
  • Task
    speech
    Billing unit
    per_1000_characters or per_second
    What is counted
    Per 1,000 input characters, or per second of output audio where the model's cost follows the output
  • Task
    embedding
    Billing unit
    input_output_tokens
    What is counted
    Input tokens; no output rate

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.

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. 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
11 of 13
Detail
K
Updated
2026-10-21
Status
Preview
Join early access

On this sheet

  1. The usage object on chat completions
  2. The usage object on tasks and jobs
  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 preview
  • 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

Company

  • About
  • Contact
  • Affiliate program
  • HIPS Payments

Legal

  • Legal
  • Consumer Health Data Privacy Policy
  • Report content
  • Cookie settings

Support

  • Contact HIPS
  • Looking for payments support?

HIPS. AI inference for builders.

hips.com

Hyperscale Inference Processing Systems OÜ