AI Providers 

Providers represent connections to AI services. Each provider stores an adapter type, optional endpoint, encrypted credentials, models, and capability flags.

Path: AI Foundation > AI Providers

AI Foundation Providers Demo

AI Providers with Own API Keys mode, provider list, models, and connection status

AI Providers — Your Own API Keys mode, configured adapters, models, connection status, and default provider.

Without at least one working provider, no AI feature runs.

Alternatively, use T3Planet Credits when you want AI without configuring your own vendor API keys.

Adding a provider 

  1. Open AI Foundation > AI Providers.
  2. Click Add provider.

  3. Fill in the required fields:

    • Display name — Friendly label for your team (for example `OpenAI production`).
    • Adapter type — Vendor protocol (OpenAI, Anthropic, Gemini, Azure, Mistral, DeepSeek, xAI, Ollama, or custom OpenAI-compatible).
    • API key — Cloud vendors need a key. Leave empty for local Ollama.
    • Model ID — Completion model (for example gpt-4o-mini).
  4. Optionally set the endpoint URL, embedding model, capabilities, temperature, and pricing fields.
  5. Click Save.
  6. Enable Default on exactly one provider.
Edit AI Provider drawer with adapter, API key, model, and capabilities

Edit AI Provider — adapter type, API key, chat model, and capability flags.

Testing a connection 

After saving a provider, click Test connection to verify the setup. The test calls the provider API and reports:

  • Connection status (success or failure)
  • Error details on failure
  • Model / capability hints when the adapter can list them

If your server reaches the internet only through a corporate proxy, configure TYPO3 HTTP settings:

config/system/additional.php 
$GLOBALS['TYPO3_CONF_VARS']['HTTP']['proxy'] = 'http://proxy.example.com:8080';
Copied!

Editing and deleting providers 

  • Click a provider row to edit its settings in the drawer.
  • Use Test connection after rotating an API key or changing the model.
  • Use Delete to remove a provider. Features that pointed at that provider fall back to the global default (or fail until another provider is assigned).

Supported adapters 

Built-in and discovered adapters include:

  • symfony.openai — OpenAI
  • symfony.anthropic — Anthropic Claude
  • symfony.gemini — Google Gemini
  • symfony.mistral — Mistral AI
  • symfony.ollama — Local Ollama
  • symfony.openrouter — OpenRouter
  • nst3af.openai_compatible — Custom / OpenAI-compatible endpoints
  • Additional Symfony AI bridges when their Composer packages are installed (for example Azure, DeepSeek, xAI)

Custom adapters: Custom AI Providers.

Capabilities 

Pick a model that supports what you need. Test connection helps validate the choice.

  • Chat — Text generation
  • Streaming — Live response display in the backend
  • Embeddings — Search and similarity features
  • Vision — Image analysis
  • Tool use — MCP agent workflows

Multiple providers — when and why 

Dev and live — Separate rows with different API keys per environment.

Cost saving — Cheap model as global default; premium model assigned in AI Features for important tasks.

EU hosting — Mistral or Azure in an EU region for data residency requirements.

Provider fields 

Fields below map to the AI Providers drawer and the tx_nst3af_provider table.

Required 

identifier

identifier
Type
string
Required

true

Unique slug for programmatic access (for example openai-prod, ollama-local). Must be unique.

title

title
Type
string
Required

true

Display name shown in the backend and dropdowns.

adapter_type

adapter_type
Type
string
Required

true

Adapter protocol identifier, for example symfony.openai or nst3af.openai_compatible.

Connection 

api_key

api_key
Type
string

API key for authentication. Stored as sodium ciphertext with an enc:v1: prefix — raw keys are never kept in the database. Required for cloud adapters; usually empty for local Ollama.

endpoint_url

endpoint_url
Type
string
Default
Adapter default

Custom API base URL. Required for OpenAI-compatible and Ollama-style adapters when the default host is wrong for your network.

model_id

model_id
Type
string

Default completion / chat model ID.

embedding_model_id

embedding_model_id
Type
string

Default embedding model ID when embeddings are enabled.

Optional configuration 

capabilities

capabilities
Type
string list

Enabled capabilities: chat, completion, embeddings, vision, streaming, tool_use.

temperature

temperature
Type
float
Default
0.7

Default sampling temperature (0.0–2.0).

system_prompt

system_prompt
Type
text

Optional provider-level system message prepended to requests.

is_default

is_default
Type
bool
Default
false

Mark as the global default. Keep exactly one default among enabled rows.

is_enabled

is_enabled
Type
bool
Default
true

Soft on/off switch without deleting the row.

priority

priority
Type
integer
Default
50

Ordering hint (0–100) when multiple providers are listed.

be_groups

be_groups
Type
backend groups

Restrict this provider to selected backend groups. Empty means available to all groups.

privacy_level

privacy_level
Type
string
Default
standard

Logging privacy only — controls how much is stored in the local request log (standard, reduced without prompt fingerprint, or none). This setting does not redact, strip, or block prompts, brand context, or documents sent to the AI provider.

Governance and status 

Optional pricing (pricing_input_per_1m, pricing_output_per_1m, pricing_currency, cost_center), retention overrides, dashboard analytics flags, and read-only status fields (last_status, last_status_at, last_status_message, last_used_at) support monitoring and cost tracking. Status fields update after Test connection and live requests.

Troubleshooting 

Test fails — Check the API key, model ID, endpoint URL, and outbound HTTPS/firewall rules.

Rate limit — Wait or upgrade the vendor plan.

Vision returns empty — Use a vision-capable model (for example GPT-4o with vision).

Module works but child extension fails — Check AI Features for per-task overrides.

Security 

  • Rotate keys every 90 days
  • Use one key per environment (dev, staging, live)
  • Restrict access via AI Permissions
  • Never commit API keys to Git

Where to get API keys 

More links: Helpful Links