Skip to main content
Choose an integration by what your application needs to connect. Each guide covers its import path and configuration. Install the adapter’s optional dependency explicitly and keep credentials in your host environment.

​
Choose the right boundary

  • Speech and media connect recognition, synthesis, native realtime sessions, and room audio. Start with the voice adapter directory.
  • Telephony controls outbound calls through six carrier/SIP adapters. Media routing remains a separate host integration. See telephony.
  • Sandboxes execute code in a local or remote workspace. Choose local, E2B, or Daytona for the trust and ownership contract you need.
  • Telemetry sends bounded observations to files, collectors, host OpenTelemetry, or Langfuse. See exporters.
  • Model providers generate responses or embeddings. Check the selected model’s capabilities and account availability.
  • Toolkits expose functions to a model. Your application still owns authorization and the effects of those functions.
  • Storage retains conversation state. A storage adapter does not automatically make execution recoverable.
  • Protocols connect tools, peers, or task lifecycles. Choose the protocol version and credential audience deliberately.
  • Devices connect an agent to hardware or an edge runtime. Follow the integration’s platform and driver setup.
For retrieval and vector stores, see knowledge integrations. For browser automation, see BrowserAgent. For audio, start with voice sessions.