Configuring language models

Purpose

dAI Pro talks to several providers of language models. An LLM configuration bundles provider, access, models and region; collections pick one configuration each for chat and for embeddings from it, plus additional models for comparisons. This way the provider can be changed without touching a collection, and each collection can have its own access with its own billing.

Where

LLM configurations in the top bar. The list shows all configurations with type, models and region; the order determines the selection lists. "Add configuration" asks for the provider type first.

The providers

Type	Chat	Embeddings	Audio	Region
Mistral AI	yes	yes	yes (Voxtral)	EU
OpenAI	yes	yes	yes	per contract, usually USA
Anthropic (Claude)	yes	no	no	USA
Google Gemini	yes	yes	no	per contract
OpenAI-compatible endpoint	yes	depends on the server	no	freely selectable

The type "OpenAI-compatible endpoint" covers every server that speaks the OpenAI dialect: European providers such as IONOS, STACKIT, Mittwald, OVHcloud and Scaleway, but also your own server with Ollama or vLLM. For the well-known providers there are presets that fill in endpoint, models and region.

Costs and prices

You enter the list prices per model under "Usage" (Chapter 19); they apply to all collections. The provider's billing runs per API key, which is why a separate key per customer pays off.

Frequently asked questions

The chat answers with an "authentication" error. The API key has expired, has been blocked, or the credit is used up. Check the account at the provider; a new key is simply entered in the configuration.

Can I delete configurations? Only if no collection uses them. The list shows the usage.

Which model is the right one? For most websites, a current large model of the provider for the chat and the standard embedding model. Compare via "Additional language models" in the test chat before you switch.