Models

List the models an endpoint serves, with their moving ids, pinned builds and retirement dates.

http

GET https://api.mellix.com/v1/models

Lists the models an endpoint serves. No token needed. Every model listed is a Myles-G decision model, called with POST /v1/decide.

Response

json

{
  "object": "list",
  "data": [
    { "id": "myles-g-31b", "object": "model", "owned_by": "mellix", "pinned": false },
    { "id": "myles-g-31b-20261027", "object": "model", "owned_by": "mellix", "pinned": true, "moving_id": "myles-g-31b", "release_date": "2026-10-27" }
  ],
  "models": [
    { "name": "myles-g-31b", "description": "Myles-G 31B: one-pass typed decisions (yes/no, choice, score) with calibrated probabilities, text and images", "release_date": "2026-10-17", "pinned": false },
    { "name": "myles-g-31b-20261027", "description": "...", "release_date": "2026-10-27", "pinned": true, "moving_id": "myles-g-31b" }
  ],
  "retired": [
    { "id": "myles-g-31b-20261024", "retired_on": "2026-10-27", "successor": "myles-g-31b-20261027", "moving_id": "myles-g-31b", "migration_url": "https://mellix.com/docs/changelog#2026-10-27" }
  ]
}

data and models list the same models in two forms, for clients that read either; the example shows one model of each kind. Each hosted model has a moving id (myles-g-12b, myles-g-31b), which always answers with that model's current build, and a pinned id per build ("pinned": true, with its moving_id and release_date), which always answers with exactly that build. Today the pinned builds are myles-g-12b-20261029 and myles-g-31b-20261027. release_date may be null for a model without one.

retired lists ids that are no longer served, each with its successor. A request naming a retired id is answered 410 model_retired (see Errors); send the moving id or the successor instead.