Custom AI Providers

​

Provider architecture

​

When to create a provider

• You use a private or on-premise LLM.
• Your vendor has a custom API that is not OpenAI-compatible.
• Your company routes AI requests through an internal gateway.
• You need capabilities or connection behavior that the built-in adapters do not provide.

​

Implementation steps

1. Add a Composer dependency or suggestion on nitsan/ns-t3af.
2. Create an adapter class in your extension.
3. Implement NITSAN\NsT3AF\Provider\Contract\AdapterInterface.
4. Tag the service with nst3af.adapter in your extension.
5. Flush TYPO3 caches.
6. Create a provider row in T3AF > AI Providers and select your adapter.
7. Run the connection test.

​

Minimal adapter shape

use NITSAN\NsT3AF\Domain\Model\Provider;
use NITSAN\NsT3AF\Provider\Capability;
use NITSAN\NsT3AF\Provider\Contract\AdapterInterface;
use NITSAN\NsT3AF\Provider\Contract\VerifyResult;

final class AcmeAdapter implements AdapterInterface
{
    public function getType(): string
    {
        return 'custom.acme';
    }

    public function getDisplayName(): string
    {
        return 'ACME AI Gateway';
    }

    public function getDefaultEndpoint(): string
    {
        return 'https://llm.example.internal/v1';
    }

    public function getDefaultCapabilities(): array
    {
        return [Capability::CHAT, Capability::STREAMING];
    }

    public function testConnection(Provider $provider): VerifyResult
    {
        // Return VerifyResult::ok() or VerifyResult::failure().
    }

    public function platform(Provider $provider): object
    {
        // Return the SDK/platform object used by the runtime adapter layer.
    }
}

​

Service registration

services:
  _defaults:
    autowire: true
    public: false

  _instanceof:
    NITSAN\NsT3AF\Provider\Contract\AdapterInterface:
      tags: ['nst3af.adapter']

  MyVendor\MyExt\Provider\:
    resource: '../Classes/Provider/*'
    autoconfigure: true

​

Credentials

​

Best practices

• Use the custom.{vendor} prefix for custom adapter types.
• Keep adapter type values stable after release.
• Return connection failures through VerifyResult::failure() instead of throwing from testConnection().
• Advertise only the capabilities your adapter really supports.
• Reuse T3AF provider rows instead of adding your own provider configuration table.

​

Verification

1. Flush caches.
2. Open T3AF > AI Providers.
3. Create or edit a provider row and select your adapter.
4. Save the row.
5. Run the connection test and confirm the status updates.
6. Trigger a feature that uses AiServiceInterface with that provider.

​

Related documentation

• Extension Integration
• AI Providers
• Configuration