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 indexModel and task guides

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
06
  1. Docs/
  2. Model and task guides
llms.txt

Models and task guides

On this sheet5 sections
  1. What a model page carries
  2. Model types and their routes
  3. Request parameters
  4. Ids, aliases and pinned versions
  5. What a model page never claims

A model page explains the supported task, input and output formats, relevant limits, model version, and billing units; where a model has specific licensing or usage conditions, those sit alongside the practical details. This page shows the catalog's shape. The catalog lists every model HIPS has published, each with its status, on Models and in GET /v1/models.

Each published model also has a sheet of its own here, at /docs/models/<id> with the id GET /v1/models lists: its pools and the precision each serves it at, its limits, its rates and, where the model takes only some of them, the request parameters it takes, all read from the catalog.

Note

The catalog is the only source of model names, limits and prices. Nothing here is hardcoded, and no model id appears on these pages; samples use the HIPS_MODEL variable.

F
Fig. 1, sheet 06Model and task guides

What a model page carries

FieldWhat it holds
Catalog idThe unversioned id (the alias) and the pinned ids of its versions
Display nameThe name shown on the page and in GET /v1/models; no version in a display name
Family, size, variantThe three tokens of the id, as structured fields so the catalog can be filtered
Type and taskThe model type and the task key the request is validated against
ModalityInputs accepted (text, image, audio, video) and outputs returned
FormatsInput and output formats per modality; for language models, the runtime weight format per pool
LimitsContext length, maximum output tokens, images per request, input dimensions, audio or video duration, batch, upload size; set per model in the catalog
VersionThe current version the alias resolves to; every pinned version with its status, release, deprecation and sunset dates
License and usage conditionsLicense name, the conditions that bind the customer and HIPS, the recorded source
Billing unitThe unit charged and the rates per pool and pricing mode; language models show input and output rates separately
Current availabilityThe supply state per pool: available, limited, unavailable, unknown, with its last update; a stale reading becomes unknown
Hardware fitPer pool, the hardware classes the version fits, with engine and format per class
Supported featuresFor language models, each feature of the compatibility matrix with its validated status; unvalidated is shown as unvalidated
  • Field
    Catalog id
    What it holds
    The unversioned id (the alias) and the pinned ids of its versions
  • Field
    Display name
    What it holds
    The name shown on the page and in GET /v1/models; no version in a display name
  • Field
    Family, size, variant
    What it holds
    The three tokens of the id, as structured fields so the catalog can be filtered
  • Field
    Type and task
    What it holds
    The model type and the task key the request is validated against
  • Field
    Modality
    What it holds
    Inputs accepted (text, image, audio, video) and outputs returned
  • Field
    Formats
    What it holds
    Input and output formats per modality; for language models, the runtime weight format per pool
  • Field
    Limits
    What it holds
    Context length, maximum output tokens, images per request, input dimensions, audio or video duration, batch, upload size; set per model in the catalog
  • Field
    Version
    What it holds
    The current version the alias resolves to; every pinned version with its status, release, deprecation and sunset dates
  • Field
    License and usage conditions
    What it holds
    License name, the conditions that bind the customer and HIPS, the recorded source
  • Field
    Billing unit
    What it holds
    The unit charged and the rates per pool and pricing mode; language models show input and output rates separately
  • Field
    Current availability
    What it holds
    The supply state per pool: available, limited, unavailable, unknown, with its last update; a stale reading becomes unknown
  • Field
    Hardware fit
    What it holds
    Per pool, the hardware classes the version fits, with engine and format per class
  • Field
    Supported features
    What it holds
    For language models, each feature of the compatibility matrix with its validated status; unvalidated is shown as unvalidated

Model types and their routes

TypeTask keys (working)Public route
languagechat (text in, text out; image inputs where the model is a vision-language model)OpenAI-compatible routes
imageimage_generation, image_editTask API, and OpenAI's image routes (Image generation and editing)
audiotranscription, translation, speechTask API
videovideo_generationTask API
specialistclassification, embedding, detection, and further focused tasks as the catalog adds themTask API
  • Type
    language
    Task keys (working)
    chat (text in, text out; image inputs where the model is a vision-language model)
    Public route
    OpenAI-compatible routes
  • Type
    image
    Task keys (working)
    image_generation, image_edit
    Public route
    Task API, and OpenAI's image routes (Image generation and editing)
  • Type
    audio
    Task keys (working)
    transcription, translation, speech
    Public route
    Task API
  • Type
    video
    Task keys (working)
    video_generation
    Public route
    Task API
  • Type
    specialist
    Task keys (working)
    classification, embedding, detection, and further focused tasks as the catalog adds them
    Public route
    Task API

A model is offered in a pool only when that pool's engine for its type runs it on at least one hardware class of the pool, as measured. The task list is set per model in the catalog.

Request parameters

HIPS never strips a parameter to serve a request. Where a model's sheet lists the request parameters it takes in the Certified pool, among temperature, top_p, stop, seed, presence_penalty, frequency_penalty, n, response_format, tools, tool_choice, parallel_tool_calls, logprobs, top_logprobs, logit_bias and reasoning_effort, a request carrying one it does not take is answered 400 unsupported_parameter, its param naming the parameter, and nothing is charged:

A parameter the model does not take

00000000000000000000000000000000000000001{"error": {"message": "`logit_bias` is not supported by `<model>`.", "type": "invalid_request_error", "param": "logit_bias", "code": "unsupported_parameter"}}
A parameter the model does not take sample

The Messages route answers the same code in Anthropic's shape (Errors).

Ids, aliases and pinned versions

A catalog id (<family>-<size>[-<variant>], lowercase) resolves to the current pinned version and moves with releases; a pinned id (<catalog id>-<version>) names one version and does not move. An alias moves with releases. Retirement of a pinned id and its notice period are open Not decided yet; a pinned id with a retirement date carries deprecates_at in GET /v1/models.

What a model page never claims

No availability before the catalog's listing state says so. No accuracy or benchmark claim without a labeled evaluation set and task-relevant error measures. No cost or performance comparison without measured representative workloads with the comparison, model, hardware, configuration and date stated.

Related sheets

  • Task guides
  • Models reference
  • Models on the site
Previous sheetImport and run your model
Next sheetTask guides
Sheet
06 of 20
Updated
2026-11-16
Sign in to the Console

On this sheet

  1. What a model page carries
  2. Model types and their routes
  3. Request parameters
  4. Ids, aliases and pinned versions
  5. What a model page never claims

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Ü