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 |
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 |
On each path (global and EU), Fast and Thinking share the same unit price ($/M). Thinking usually costs more in practice because it uses more tokens, not because the list rate is higher. Live unit rates are shown in the platform Models and Pricing pages.
Exact upstream providers can change. The aliases are the stable contract for your integration.
Thinking and max_tokens
Thinking aliases (isms-thinking, isms-thinking-eu) spend part of the completion budget on internal reasoning before the visible answer. If you set a very low max_tokens (for example under a few hundred), the budget can be used up before any answer text is produced.
For those thinking aliases, the API raises a client max_tokens below 1024 up to 1024 so the request can still return content. Fast aliases are not raised. If you omit max_tokens, the API uses its normal high default (tens of thousands of tokens).
When a raise happens, the response includes:
| Header | Meaning |
|---|---|
x-isms-max-tokens-requested | The value you sent |
x-isms-max-tokens-effective | The value actually used (at least 1024 on thinking) |
You may be billed for output up to the effective budget, not only the lower number you requested.
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, Zero Data Retention, and the in-console docs at platform.ismscopilot.com/docs.
Framework knowledge
Completions are compliance-aware: the stack injects framework reference knowledge based on your request, or exactly the modules you pin. You control it per request with ismscopilot: { "frameworks": "auto" | "none" | ["ISO_27001", ...] }, enumerate coverage with GET /v1/frameworks, and every response discloses what was injected via the x-isms-frameworks header and the ismscopilot response object. The server prompt that frames it is published word for word: see The API system prompt, in full. You do not maintain a separate RAG store of standards text for the built-in frameworks.