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 indexBatch jobs

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
07
  1. Docs/
  2. Batch jobs
llms.txt

Batch jobs

On this sheet11 sections
  1. How a batch runs
  2. Collect the results
  3. The routes
  4. What a line can call
  5. Validation and line errors
  6. The completion window
  7. Price
  8. Limits
  9. Where batch lines run
  10. Files and retention
  11. In the Console

Send many requests at once and collect the results when they are done. HIPS runs batch lines when GPU capacity is free, at 50% less than the on-demand price of the same model, and tells you when the batch is finished. The API is designed to follow OpenAI's Batch API, so that the official SDKs and the batch scripts you already have work with a HIPS key, base URL and model id; the compatibility matrix records each case once it is validated.

Note

Batches are built and not offered in production yet: POST /v1/files and POST /v1/batches answer 404 route_not_available until they are switched on. The queue of enqueued tokens per model and workspace is set per plan, and its values are still open Not decided yet.

F
Fig. 1, sheet 07Batch jobs

How a batch runs

  1. 01

    Step 1: Write a JSONL file, one request per line, each with your own custom_id.

  2. 02

    Step 2: Upload it with POST /v1/files and the purpose batch.

  3. 03

    Step 3: Create the batch with POST /v1/batches, naming the endpoint and the completion window. The price is quoted and bound here.

  4. 04

    Step 4: HIPS runs the lines when capacity is free. Live requests always come first.

  5. 05

    Step 5: When the batch ends, a signed webhook and a mail tell you; download the output and error files.

00000000000000000000000000000000000000001import json2import os3from openai import OpenAI4 5client = OpenAI(6    api_key=os.environ["HIPS_API_KEY"],7    base_url=os.environ["HIPS_BASE_URL"],  # https://ai.hips.com/v18)9 10# One request per line, each with your own custom_id.11with open("requests.jsonl", "w") as f:12    for i, text in enumerate(["First document.", "Second document."]):13        f.write(json.dumps({14            "custom_id": f"doc-{i}",15            "method": "POST",16            "url": "/v1/chat/completions",17            "body": {18                "model": os.environ["HIPS_MODEL"],19                "messages": [{"role": "user", "content": f"Summarize: {text}"}],20            },21        }) + "\n")22 23batch_file = client.files.create(file=open("requests.jsonl", "rb"), purpose="batch")24batch = client.batches.create(25    input_file_id=batch_file.id,26    endpoint="/v1/chat/completions",27    completion_window="24h",28)29print(batch.id, batch.status)
Reads from the environmentHIPS_API_KEYHIPS_BASE_URLHIPS_MODEL

Collect the results

The output file holds one line per finished request, matched to your input by custom_id, in no particular order. Lines that failed, and lines still unfinished when the window closed, come back in the error file.

Python

00000000000000000000000000000000000000001batch = client.batches.retrieve(batch.id)2 3if batch.status == "completed":4    for line in client.files.content(batch.output_file_id).text.splitlines():5        record = json.loads(line)6        print(record["custom_id"], record["response"]["status_code"])7 8    # Lines that failed, or expired when the window closed, are in the error file.9    if batch.error_file_id:10        print(client.files.content(batch.error_file_id).text)
Python sample

The routes

On https://ai.hips.com, in OpenAI's Batch API shape.

POST/v1/filesnot offered

Upload the JSONL input file with the purpose batch.

POST/v1/batchesnot offered

Create a batch from an input file: input_file_id, endpoint, completion_window.

GET/v1/batches/{id}not offered

A batch with its status, its line counts and its output and error file ids.

POST/v1/batches/{id}/cancelnot offered

Cancel a batch. Finished lines are delivered and charged; the rest are not.

GET/v1/batchesnot offered

The workspace's batches, newest first.

GET/v1/files/{id}/contentnot offered

Download an output or error file.

What a line can call

  • /v1/chat/completions, for language models: the one endpoint a batch takes as built. Any other is a 400 unsupported_value.
  • Embeddings and the HIPS task API come later, as lines OpenAI's Batch API does not offer.
  • One model per input file; your own model's lines follow the pools it may run in.
  • A line may not name a router: a router chooses per request, and a batch runs one model. The file is refused with 400 invalid_file_format naming the first such line.

Validation and line errors

A batch in validating that finds any of these ends failed, each finding in errors.data with its code, message, param and line; nothing is held, run or charged. message is one fixed sentence per code, param names a field only where it is a field the request shape knows (for an unknown field, its parent), and nothing of a line's text is quoted.

CodeWhen
missing_required_parametercustom_id, method, url or body absent, or a field the route requires
duplicate_custom_idA custom_id used on an earlier line
invalid_value, invalid_type, unknown_parameter, unsupported_parameter, unsupported_valueA body that breaks the route's rules, a method other than POST, a streamed line
context_length_exceeded, max_tokens_exceededA limit the body alone decides
token_limit_exceededThe batch's input tokens would take the model's queue for the workspace past its plan's value
insufficient_creditThe prepaid balance cannot carry the held maximum
budget_exceededA budget guardrail of the workspace or the credential cannot carry the batch's maximum charge; the message names the guardrail and when it resets
  • Code
    missing_required_parameter
    When
    custom_id, method, url or body absent, or a field the route requires
  • Code
    duplicate_custom_id
    When
    A custom_id used on an earlier line
  • Code
    invalid_value, invalid_type, unknown_parameter, unsupported_parameter, unsupported_value
    When
    A body that breaks the route's rules, a method other than POST, a streamed line
  • Code
    context_length_exceeded, max_tokens_exceeded
    When
    A limit the body alone decides
  • Code
    token_limit_exceeded
    When
    The batch's input tokens would take the model's queue for the workspace past its plan's value
  • Code
    insufficient_credit
    When
    The prepaid balance cannot carry the held maximum
  • Code
    budget_exceeded
    When
    A budget guardrail of the workspace or the credential cannot carry the batch's maximum charge; the message names the guardrail and when it resets

A line that never ran is in the error file with response: null and error: batch_expired when the window closed first, batch_cancelled when the batch was cancelled, attempt_failed when every attempt failed for a reason that is not yours. None of them is charged.

The completion window

You choose how long HIPS may take: 24h by default, or any whole number of hours or days up to 7d. The price is the same for every window. No finish time is promised inside it: everything that finishes is delivered, and lines still unfinished when the window closes come back as expired and are not charged.

Price

Batch
Discount50% less than the on-demand rate of the same model, pool and unit, applied to every rate a line uses: input, cached input, output and every task unit
QuoteBound when POST /v1/batches accepts the batch, and held for every line through the window
Prompt cachingNo line reuses a cached prompt prefix yet, so every input token is billed at the batch input rate (Prompt caching)
BalanceThe batch's maximum charge (input at batch rates plus each line's output cap) is held against your prepaid balance at creation and released line by line as lines finish or expire
Expired linesNot charged
A model without batchA model whose price cannot carry the discount is sold without batch rather than at a smaller discount, and the catalog says so
  • Discount
    Batch
    50% less than the on-demand rate of the same model, pool and unit, applied to every rate a line uses: input, cached input, output and every task unit
  • Quote
    Batch
    Bound when POST /v1/batches accepts the batch, and held for every line through the window
  • Prompt caching
    Batch
    No line reuses a cached prompt prefix yet, so every input token is billed at the batch input rate (Prompt caching)
  • Balance
    Batch
    The batch's maximum charge (input at batch rates plus each line's output cap) is held against your prepaid balance at creation and released line by line as lines finish or expire
  • Expired lines
    Batch
    Not charged
  • A model without batch
    Batch
    A model whose price cannot carry the discount is sold without batch rather than at a smaller discount, and the catalog says so

Actual prices are set per model in the catalog; the Pricing page shows the shape.

Limits

The limits match OpenAI's

LimitValue
Lines per input file50,000
Input file size200 MB
Models per input fileOne
Embedding inputs per batch50,000
Batches created per hour2,000
Open batches per workspace100
Enqueued input tokens per model and workspaceSet per plan Not decided yet
  • Limit
    Lines per input file
    Value
    50,000
  • Limit
    Input file size
    Value
    200 MB
  • Limit
    Models per input file
    Value
    One
  • Limit
    Embedding inputs per batch
    Value
    50,000
  • Limit
    Batches created per hour
    Value
    2,000
  • Limit
    Open batches per workspace
    Value
    100
  • Limit
    Enqueued input tokens per model and workspace
    Value
    Set per plan Not decided yet

Where batch lines run

  • On every eligible idle GPU: Community pool devices the moment they come online, and spare capacity in the Certified pool.
  • Live requests always come first. A device finishes the batch line it is running before it takes a live request.
  • No line reuses another line's prompt prefix yet: each line is billed for every input token it sends.
  • A batch line on your own model runs only where the model may run: the Certified pool, at launch.

Files and retention

A batch's input file is deleted once the batch ends (completed, failed, expired or cancelled), within about five minutes, unless another open batch reads it; to run it again, upload it again. Output and error files are kept 30 days and then deleted, sooner when you set a shorter expiry (output_expires_after) or delete them.

In the Console

The Console's Batches screens follow every batch of the workspace: the list, and for each batch its timeline through the statuses, its usage and money (cached input counted apart, expired lines neither charged), its files as metadata with a short-lived download link to the workspace's storage, and a failed validation's findings, the line and the parameter, never a line's content. Cancel the batch stops it while it runs; the lines already finished stay delivered and charged.

Webhooks, beside them, holds the workspace's endpoints: add one with its URL and the events it receives, enable or disable it, send it a test once it is enabled, rotate its signing secret (with a recent sign-in), and read its deliveries, sending one again or every failed one.

Note

Batches are not offered yet: until they are, the batch routes answer 404 route_not_available, and the screens have no batch to show.

Related sheets

  • Batches reference
  • Files reference
  • Webhooks
  • Prompt caching
  • Limits
Previous sheetDocument processing
Next sheetPrompt caching
Sheet
07 of 20
Updated
2026-11-14
Sign in to the Console

On this sheet

  1. How a batch runs
  2. Collect the results
  3. The routes
  4. What a line can call
  5. Validation and line errors
  6. The completion window
  7. Price
  8. Limits
  9. Where batch lines run
  10. Files and retention
  11. In the Console

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Ü