Residency & models

The response disclosure headers, managed aliases, and the live-verified model catalog.

Response headers

Calls to a sluis/* alias disclose the resolved route via x-sluis-* response headers; plain provider/model calls carry no extra headers. Residency itself is organisation policy, enforced at dispatch, never a request header.

Managed aliases

Managed aliases are reserved sluis/... model names. sluis/auto chooses per request; the use-case aliases choose from daily Artificial Analysis benchmark snapshots curated by Sluis. Artificial AnalysisEvery alias resolves inside the tenant's residency policy first, so the sovereignty rule beats the benchmark rank.

Call an alias anywhere you would pass a provider/model id. The response headers show both the route you asked for and the concrete model that ran.

curl https://api.sluis.ai/v1/chat/completions \
  -H "Authorization: Bearer $SLUIS_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "model": "sluis/auto", "messages": [{ "role": "user", "content": "Plan a GDPR-safe rollout" }] }'

# response headers:
# x-sluis-route: sluis/auto
# x-sluis-model: mistral/mistral-large-latest

x-sluis-route is the managed or tenant alias that resolved the request. x-sluis-model is the concrete provider/model target after residency policy, shadowing and routing.

Supported models

Sluis exposes built-in providers through managed keys when a platform credential is configured; connect your own key (BYOK) or add a custom OpenAI-compatible provider in the Console to override or extend the catalog. Every callable id is provider-prefixed, so pass provider/model (e.g. mistral/mistral-large-latest) and Sluis routes it per your residency policy. The catalog is credential- and policy-aware, uses live provider catalogs where available, and can fall back to declared models during an upstream catalog failure. Vertex candidates are separately probe-verified for EU availability.

# the public catalog behind the list above — sanitized, no auth, refreshed hourly
curl https://api.sluis.ai/public/catalog.json | jq '.operations[0].providers[].id'

# per key: the models your policy, credentials and allow-list actually reach
curl https://api.sluis.ai/v1/models -H "Authorization: Bearer $SLUIS_KEY"