Give AI features one product-owned gateway.

The current source explores a shared route from your product to multiple model providers—so credentials, model choices, streaming responses, files, tools, batches, and usage do not become unrelated integrations.

Understand the direction Inspect post-release source ↗

Intended product journey

Your product asks for useful workSummarize, classify, embed, generate, or call a tool

Daptin chooses a configured pathProvider, credential, model deployment, and product rules meet

The experience receives one coherent resultStreaming and usage remain connected to the request

Direction shown; release not promised

One product surfaceAvoid provider-specific behavior leaking into every client.

Controlled connectionsKeep provider credentials and deployments behind the backend.

Accountable workRelate usage and lifecycle to the request that caused it.

Why this direction matters

An AI feature is more than one text response.

A real product may need a model catalogue, several provider accounts, streaming responses, embeddings, uploaded files, batch jobs, tool calls, usage records, and a way to stop or drain outstanding work.

If every screen talks directly to a provider, those decisions spread through the product. The source work brings them behind one Daptin-facing compatibility layer and connects them with stored credentials, deployments, files, usage, and runtime lifecycle.

The intended benefit is not a fashionable endpoint. It is keeping AI work inside the same product context and operating boundary as the application that requested it.

What the source work connects

One journey across model work.

These are development areas visible after v0.12.36, not current-release commitments.

ChooseProviders and models

Represent available models and product-selected deployments without hard-wiring every client.

AuthorizeCredentials and access

Keep reusable provider secrets on the backend and associate work with a caller.

PerformStreaming, tools, files, batches

Support more than a one-shot response while retaining a shared request context.

AccountUsage and lifecycle

Relate consumption, cancellation, multi-node work, and shutdown to the product operation.

Release boundary

Evaluate the code, not a release promise.

This capability is not presented as available in Daptin v0.12.36. Interfaces, compatibility, provider coverage, lifecycle, and operating requirements may change before a containing release. Do not plan production adoption from this page alone.

Review the actual changes ↗See usage-plan work →