---
title: "GET /v1/configs/models/{*id} — dual-purpose dispatcher."
method: GET
path: "/v1/configs/models/{id}"
tags: ["config"]
---

# GET /v1/configs/models/{*id} — dual-purpose dispatcher.

`GET /v1/configs/models/{id}`

Handles two endpoints sharing the same wildcard route:

- `GET /v1/configs/models/{id}` — YAML view of the gateway's model.
- `GET /v1/configs/models/{id}/status` — JSON worker-ack readiness for
  that model on this specific gateway replica.

The `{*id}` wildcard is necessary because model IDs routinely contain
forward slashes (`BAAI/bge-m3`), so we strip an optional trailing
`/status` segment here rather than maintain two overlapping axum routes
(axum's `matchit` panics on overlapping catch-all routes).

Disambiguation when a model literally named `something/status` exists:
we prefer the status interpretation only when the `/status`-stripped
id resolves to a real model. That keeps an accidental model whose ID
ends with `/status` addressable under `GET
/v1/configs/models/foo/status` as a config read, and matches what
admin tooling expects (status requests are only meaningful against
models that actually exist). `sie-config` additionally refuses to
register model IDs ending in `/status` so the pathological case where
**both** `foo` and `foo/status` are models cannot arise, but we
still degrade gracefully if it ever does.

## Path parameters

- `id` string, required

## Response `200`

Model config YAML

## Other responses

- `401` — Missing or invalid bearer token (inference token)
- `404` — Model not found
- `500` — Failed to serialize YAML; gateway auth enabled but no tokens configured

---

[API](https://skmtc.net/superlinked/apis/sie-gateway.md) · [All operations](https://skmtc.net/superlinked/apis/sie-gateway/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/superlinked/sie-gateway/versions/06a326e2c3e9/schema)