AI Providers¶
The AI Providers page defines the application-level AI services that Emakin features can use.
Open Platform Services → AI Providers. Select Add New AI Provider to create a provider, complete the settings below, and then save the host configuration.
Provider Settings¶
| Setting | Description |
|---|---|
| Is Enabled? | Controls whether the provider is available. A provider is usable only when it is enabled and has an API key. |
| Client Type | Selects the provider protocol: OpenAI, OpenRouter, Claude, or Ollama. |
| Name | Identifies the provider in Emakin. Use a name that distinguishes the service and model from other configured providers. |
| Base Url | Specifies the provider API endpoint. Enter the endpoint required by the selected client type or compatible service. |
| Model | Specifies the model identifier sent to the provider. Use the exact identifier published by the provider. |
| Context Length | Specifies the model's maximum context size, in tokens, for request planning. |
| Input Modalities | Declares the input types accepted by the model: Text, Image, and/or Audio. If no value is stored, Emakin treats the provider as text-only. |
| API Key | Supplies the credential used to call the provider. This value is stored as a password field. |
Protect the API Key¶
The API Key field supports environment-variable placeholders. Prefer a placeholder to storing the credential directly in Host Administration.
1 | |
The named environment variable must be available to the Emakin agent. If it is missing, the application cannot resolve the provider configuration.
Note: Emakin considers a provider available only when it is not disabled and its resolved API key is not empty. This requirement also applies to providers whose endpoint does not validate an API key; use an appropriate non-empty value for that deployment.
Domain Overrides¶
The settings on this page are application defaults. A domain can override an AI provider from the domain configuration. Providers are matched by Client Type; values left empty in the domain setting inherit the corresponding application value. A domain can also add a provider type that is not configured at application level.
When a feature requests a provider, Emakin uses the first effective provider in configured order. It does not automatically fail over to later providers after a request failure, so place the preferred provider first. Disabled providers and providers whose resolved API key is empty are skipped.