LowRouterBeta

Available models

The full catalogue lives on the model browser. It’s generated from the same data the API exposes at GET /models, so the two agree by construction.

How model IDs are formed

A model ID has three parts, with an optional fourth for region pinning:

Text
<provider>/<creator>/<model>[/<locode>]

Examples:

  • openai/openai/gpt-4o-mini
  • anthropic/anthropic/claude-sonnet-4.5
  • vertex/anthropic/claude-opus-4.6/sg-sin

The <provider> segment is the upstream that serves the request; the <creator> segment is who created the model (these differ for re-hosted models); the <model> segment is the model name, with version numbers written dotted (e.g. claude-sonnet-4.5). Two-part IDs are rejected — a request must carry at least the three-part form.

The optional fourth segment is a UN/LOCODE that pins the request to a specific region (e.g. sg-sin for Singapore). Appending it is how you route a request through a particular region.

Every ID listed here is callable as printed. If you omit the region, it resolves to the model’s global endpoint or — for models served only in specific regions — to its lowest-carbon one; if you omit the version, it resolves to the most recent version of that same model. The response echoes the fully resolved ID. See how IDs resolve for the exact rules and for what stays strict.

What each model card shows

  • Display name — the human-readable name, sometimes versioned.
  • Provider and owner — who serves it and who created it (these differ for re-hosted models, e.g. Llama on Mistral).
  • Context window — max input tokens.
  • Pricing — prompt, completion, and (where applicable) cached prompt rates per 1M tokens, in your account currency.
  • Capabilities — tool_use, vision, structured_output, streaming. Filter the catalogue by these.
  • Eco data — active parameter count and the energy estimate per 1K tokens. Both numbers come from the methodology. The confidence band (accurate, medium, gross) reflects how well-sourced the parameter count is.
  • Regions — where the upstream serves it (eu-west, us-east, …).

Auto-routed IDs

An auto/<creator>/<model> ID names the model you want and leaves the provider and region to the router — same weights, same output, only the route chosen for you. These appear in this listing alongside the explicit IDs for every model served by more than one route. See routing.

When an auto-routed ID is used, the response’s model field is the resolved four-segment ID.

Lifecycle

  • Added. When an upstream releases a new model and we integrate it, it appears on the model browser. Brand-new models start with a medium or gross eco confidence band until the parameter count is verified.
  • Deprecated. When an upstream announces deprecation, the model card flags it with a deprecated badge and a sunset date. Routing still uses it until the sunset date.
  • Removed. After the sunset date, requests for the model return model_deprecated. A migration suggestion is included in the error body when we have one.

Filtering the catalogue

The model browser supports filtering by:

  • Provider
  • Context window
  • Capability flags
  • Eco confidence band
  • Price range

The same filters are reflected in GET /models query parameters.