Skip to main content
Hostlinku provides a single centralized model catalog. Each model has a unique slug that is used in the model parameter in Chat Completions, along with context size, capabilities, and price per token.

GET /v1/models

Returns all models that are marked as available, not yet deprecated, and available for the Service Mode API key being used (Performance or Low-Cost), along with the price per 1M tokens in that mode.
Example:
Response (example truncated; the exact value for your account is retrieved from this endpoint):

Public catalog (no authentication required)

For marketing or exploratory use without an API key, a public catalog is available:
The public catalog displays only Hostlinku models along with their slugs, names, contexts, capabilities, and public prices. Supported queries: q (search by name/description), capability, family, sort (popular, newest, price-asc, price-desc, context-desc, name-asc), page, and pageSize (max 100). The data response contains items, total, page, pageSize, and totalPages.

List of Models

There are currently 45 models available. Click a model name to view its context, capabilities, price, and supported endpoints.

How to Choose a Model

  1. Determine your needs: general chat, reasoning, vision/multimodal, tool invocation, or structured JSON output. Check the capabilities field.
  2. Pay attention to the context size: make sure context_window is large enough to accommodate your prompt and output.
  3. Compare prices: pricing.input for prompt tokens and pricing.output for tokens Answer: Reasoning models generally have higher output costs.
  4. Start with a small model: for development, use a lightweight model (e.g., gpt-6-luna, deepseek-v4-1-flash, qwen3-6-plus) are much cheaper; only upgrade the model if the quality is insufficient.
  5. View the console: the Model menu at console.hostlinku.com displays a catalog with the same prices and features, plus a detail page for each model.

Routing and Failover

Hostlinku automatically manages the internal routes that serve each model. If an error occurs on the route currently being used (5xx/timeout), the request is automatically retried via another route before giving up. You continue to use the same model slug and don’t need to change anything; these internal details are not displayed in the response.