Configuration 

This extension is configured through TYPO3 Extension Configuration values defined in ext_conf_template.txt.

Configuration overview 

Main groups include:

  • AI engine defaults
  • Provider-specific API keys and models
  • Embedding model settings
  • Translation provider defaults
  • Basic authentication options

Minimum production configuration 

For a working setup:

  1. Set defaultModel (for example openai, gemini, claude, mistral).
  2. Add API key for the selected provider.
  3. Set provider default model.
  4. Keep token and temperature values aligned with your usage/cost policy.

Provider keys 

Commonly used keys:

OpenAI
openai_api_key, openai_model, openai_temperature, openai_max_tokens, openai_embedding_model, openai_admin_api_key
Anthropic / Claude
anthropic_api_key, anthropic_model, anthropic_temperature, anthropic_max_tokens
Gemini
gemini_api_key, gemini_model, gemini_embedding_model
Azure
azure_api_key, azure_api_endpoint, azure_api_model, azure_api_version
Mistral
mistral_api_key, mistral_model, mistral_embedding_model, mistral_temperature, mistral_max_tokens
DeepSeek
deepseek_api_key, deepseek_model, deepseek_temperature, deepseek_response_format
xAI
xai_api_key, xai_model, xai_temperature, xai_response_format
Custom LLM
enable_custom_llm_model, custom_llm_api_url, custom_llm_api_key, custom_llm_model_name, custom_llm_temperature

Basic authentication 

Use these keys when your source URLs are protected:

  • basicAuthEnabled
  • basicAuthUsername
  • basicAuthPassword

The helper HttpAuthUtility retries 401/403 requests with basic auth when this is enabled and fully configured.

Security recommendations 

  • Restrict backend access to trusted administrators.
  • Rotate provider API keys regularly.
  • Avoid sharing backend screenshots that expose secrets.
  • Use dedicated provider keys per environment when possible.