# Available models

The full catalogue lives on the [model browser](/models). It's
generated from the same data the API exposes at
[`GET /models`](../api-reference/models-and-providers), so the two
agree by construction.

## How model IDs are formed

```
<provider>/<model>
```

Examples:

- `openai/gpt-4o-mini`
- `anthropic/claude-sonnet-4-5`
- `mistral/mistral-large-latest`

The `<provider>` segment matches the `id` of an entry in
[`GET /providers`](../api-reference/models-and-providers); the
`<model>` segment is the upstream model name.

## 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 1K 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](../sustainable-ai/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`,
  …).

## Pseudo-models

Two model strings are not actual models but routing primitives:

- **`lowrouter/auto`** — pick a model based on the request and the
  current routing policy. See [routing](routing).
- **`lowrouter/auto-cheap`** — auto-route biased toward the cheapest
  model that can plausibly handle the request. Useful for
  high-volume, low-importance work (classification, simple summaries).

When a pseudo-model is used, the response's `model` field is the
*resolved* model.

## 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; see
the [discovery endpoints](../api-reference/models-and-providers).