Transports
A transport defines how a Bot connects to an AI service. It is separate from the provider so connection settings can be reused or changed without replacing provider behavior.
Create transports under Bot → Transports. The Console exposes the endpoint, static headers, connection timeout, read timeout, keepalive interval, and Bot assignments.
Endpoint rules
The endpoint must be an absolute URI when provided. Voxtronics validates the URI scheme when a modality selects the transport:
| Modality | Accepted endpoint schemes |
|---|---|
| LLM | http or https |
| Realtime, STT, TTS | ws or wss |
An endpoint may be left empty when the provider integration supplies its standard endpoint.
Static headers apply to every connection that uses the transport. Do not place provider API keys in transport headers when the provider form supports a Vault-backed credential.
Assignments
Assign the transport to the same Bots as the modalities that reference it. The control plane rejects incompatible schemes, missing Bot assignments, and deletion of a transport still used by a modality.