Documentation

Residency & models

Per-request residency headers, the response provenance set, and the live-verified model catalog.

Residency headers

Sluis reads these on the request and returns the x-sluis-* set on the response.

HeaderDescription
X-Sluis-ResidencyOverride the key's policy for this call. Stricter only, e.g. eu-only, eu-uk.
X-Sluis-ClassForce a data class instead of letting the classifier decide: phi, pii, secrets.
x-sluis-regionResponse · the region the request actually ran in.
x-sluis-decisionResponse · in-region, fallback, or blocked.
x-sluis-sealResponse · this entry's hash in the audit chain.

Supported models

Every provider runs on Sluis's managed keys out of the box: 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 verified live: a model is only offered when an EU surface actually serves it. Connect your own key (BYOK) or add a custom OpenAI-compatible provider in the Console to override or extend the catalog.

  • Mistral: mistral/mistral-large-latest, mistral/codestral-2508, mistral/mistral-embed · EU (Paris), EU-sovereign
  • Scaleway: scaleway/llama-3.3-70b-instruct, scaleway/qwen3-235b-a22b-instruct-2507, scaleway/mistral-small-3.2-24b-instruct-2506 · EU (Paris), EU-sovereign
  • Anthropic on Vertex: vertex/claude-opus-4-8, vertex/claude-opus-4-7, vertex/claude-sonnet-5, vertex/claude-haiku-4-5 · EU multi-region / europe-west1 (US-owned, CLOUD Act)
  • Google: vertex/gemini-3.5-flash, vertex/gemini-3.1-flash-lite, vertex/gemini-2.5-pro, vertex/gemini-2.5-flash · Vertex EU multi-region / EU regions (US-owned, CLOUD Act)
  • Custom: any OpenAI-compatible endpoint you connect (your base URL + key), called as your-provider/model