Models and regions
isms-fast and isms-thinking model aliases, including EU-oriented -eu variants.
The API exposes a small set of model aliases. You pass the alias as the model field on /v1/chat/completions. Behind the alias, ISMS Copilot routes to a compliance-tuned model stack and injects framework knowledge when relevant.
Aliases
| Alias | Intent |
|---|---|
isms-fast | Fast answers, lower latency and cost |
isms-thinking | Deeper reasoning for harder questions |
isms-fast-eu | Fast path with EU-oriented routing |
isms-thinking-eu | Thinking path with EU-oriented routing |
Exact upstream providers can change. The aliases are the stable contract for your integration.
Regions and dual-mode
- Prefer
-eualiases when you need EU-oriented processing for a request. - Global (non-
-eu) aliases may route through additional capacity when global mode is enabled on the production API. - When global mode is off, non-
-eualiases still complete; they use the EU-safe path.
For the latest operator-facing wording about providers and data residency, see the Trust Center and the in-console docs at platform.ismscopilot.com/docs.
Framework knowledge
Completions are compliance-aware: the stack can inject framework context (for example ISO 27001 or SOC 2 control language) based on the request. You do not maintain a separate RAG store of standards text for the built-in frameworks.
Your application still owns its own proprietary documents. Send that content in the messages payload (or your own retrieval layer) when answers must ground in customer-specific material.