telnyx 6.41.1 → 6.43.0

package/src/resources/ai/assistants/versions.ts

@@ -125,15 +125,31 @@ export interface UpdateAssistant {
   dynamic_variables?: { [key: string]: unknown };
 
   /**
-   * If the dynamic_variables_webhook_url is set for the assistant, we will send a
-   * request at the start of the conversation. See our
-   * [guide](https://developers.telnyx.com/docs/inference/ai-assistants/dynamic-variables)
-   * for more information.
+   * Timeout in milliseconds for the dynamic variables webhook. Must be between 1 and
+   * 10000 ms. If the webhook does not respond within this timeout, the call proceeds
+   * with default values. See the
+   * [dynamic variables guide](https://developers.telnyx.com/docs/inference/ai-assistants/dynamic-variables).
+   */
+  dynamic_variables_webhook_timeout_ms?: number;
+
+  /**
+   * If `dynamic_variables_webhook_url` is set, Telnyx sends a POST request to this
+   * URL at the start of the conversation to resolve dynamic variables. **Gotcha:**
+   * the webhook response must wrap variables under a top-level `dynamic_variables`
+   * object, e.g. `{"dynamic_variables": {"customer_name": "Jane"}}`. Returning a
+   * flat object will be ignored and variables will fall back to their defaults. See
+   * the
+   * [dynamic variables guide](https://developers.telnyx.com/docs/inference/ai-assistants/dynamic-variables)
+   * for the full request/response format and timeout behavior.
    */
   dynamic_variables_webhook_url?: string;
 
   enabled_features?: Array<AssistantsAPI.EnabledFeatures>;
 
+  external_llm?: UpdateAssistant.ExternalLlm;
+
+  fallback_config?: UpdateAssistant.FallbackConfig;
+
   /**
    * Text that the assistant will use to start the conversation. This may be
    * templated with
@@ -153,20 +169,47 @@ export interface UpdateAssistant {
   instructions?: string;
 
   /**
-   * This is only needed when using third-party inference providers. The `identifier`
-   * for an integration secret
+   * Connected integrations attached to the assistant. The catalog of available
+   * integrations is at `/ai/integrations`; the user's connected integrations are at
+   * `/ai/integrations/connections`. Each item references a catalog integration by
+   * `integration_id`.
+   */
+  integrations?: Array<UpdateAssistant.Integration>;
+
+  /**
+   * Settings for interruptions and how the assistant decides the user has finished
+   * speaking. These timings are most relevant when using non turn-taking
+   * transcription models. For turn-taking models like `deepgram/flux`, end-of-turn
+   * behavior is controlled by the transcription end-of-turn settings under
+   * `transcription.settings` (`eot_threshold`, `eot_timeout_ms`,
+   * `eager_eot_threshold`).
+   */
+  interruption_settings?: UpdateAssistant.InterruptionSettings;
+
+  /**
+   * This is only needed when using third-party inference providers selected by
+   * `model`. The `identifier` for an integration secret
    * [/v2/integration_secrets](https://developers.telnyx.com/api-reference/integration-secrets/create-a-secret)
-   * that refers to your LLM provider's API key. Warning: Free plans are unlikely to
-   * work with this integration.
+   * that refers to your LLM provider's API key. For bring-your-own endpoint
+   * authentication, use `external_llm.llm_api_key_ref` instead. Warning: Free plans
+   * are unlikely to work with this integration.
    */
   llm_api_key_ref?: string;
 
+  /**
+   * MCP servers attached to the assistant. Create MCP servers with
+   * `/ai/mcp_servers`, then reference them by `id` here.
+   */
+  mcp_servers?: Array<UpdateAssistant.McpServer>;
+
   messaging_settings?: AssistantsAPI.MessagingSettings;
 
   /**
-   * ID of the model to use. You can use the
+   * ID of the model to use when `external_llm` is not set. You can use the
    * [Get models API](https://developers.telnyx.com/api-reference/chat/get-available-models)
-   * to see all of your available models,
+   * to see available models. If `external_llm` is provided, the assistant uses
+   * `external_llm` instead of this field. If neither `model` nor `external_llm` is
+   * provided, Telnyx applies the default model.
    */
   model?: string;
 
@@ -174,20 +217,46 @@ export interface UpdateAssistant {
 
   observability_settings?: AssistantsAPI.ObservabilityReq;
 
+  /**
+   * Configuration for post-conversation processing. When enabled, the assistant
+   * receives one additional LLM turn after the conversation ends, allowing it to
+   * execute tool calls such as logging to a CRM or sending a summary. The assistant
+   * can execute multiple parallel or sequential tools during this phase.
+   * Telephony-control tools (e.g. hangup, transfer) are unavailable
+   * post-conversation. Beta feature.
+   */
+  post_conversation_settings?: UpdateAssistant.PostConversationSettings;
+
   privacy_settings?: AssistantsAPI.PrivacySettings;
 
+  /**
+   * Tags associated with the assistant. Tags can also be managed with the assistant
+   * tag endpoints.
+   */
+  tags?: Array<string>;
+
   telephony_settings?: AssistantsAPI.TelephonySettings;
 
+  /**
+   * IDs of shared tools to attach to the assistant. New integrations should prefer
+   * `tool_ids` over inline `tools`.
+   */
   tool_ids?: Array<string>;
 
   /**
-   * The tools that the assistant can use. These may be templated with
-   * [dynamic variables](https://developers.telnyx.com/docs/inference/ai-assistants/dynamic-variables)
+   * Deprecated for new integrations. Inline tool definitions available to the
+   * assistant. Prefer `tool_ids` to attach shared tools created with the AI Tools
+   * endpoints.
    */
   tools?: Array<AssistantsAPI.AssistantTool>;
 
   transcription?: AssistantsAPI.TranscriptionSettings;
 
+  /**
+   * Human-readable name for the assistant version.
+   */
+  version_name?: string;
+
   voice_settings?: AssistantsAPI.VoiceSettings;
 
   /**
@@ -196,6 +265,242 @@ export interface UpdateAssistant {
   widget_settings?: AssistantsAPI.WidgetSettings;
 }
 
+export namespace UpdateAssistant {
+  export interface ExternalLlm {
+    /**
+     * Base URL for the external LLM endpoint.
+     */
+    base_url: string;
+
+    /**
+     * Model identifier to use with the external LLM endpoint.
+     */
+    model: string;
+
+    /**
+     * Authentication method used when connecting to the external LLM endpoint.
+     */
+    authentication_method?: 'token' | 'certificate';
+
+    /**
+     * Integration secret identifier for the client certificate used with certificate
+     * authentication.
+     */
+    certificate_ref?: string;
+
+    /**
+     * When `true`, Telnyx forwards the assistant's dynamic variables to the external
+     * LLM endpoint as a top-level `extra_metadata` object on the chat completion
+     * request body. Defaults to `false`. Example payload sent to the external
+     * endpoint:
+     * `{"extra_metadata": {"customer_name": "Jane", "account_id": "acct_789", "telnyx_agent_target": "+13125550100", "telnyx_end_user_target": "+13125550123"}}`.
+     * Distinct from OpenAI's native `metadata` field, which has its own size and type
+     * limits.
+     */
+    forward_metadata?: boolean;
+
+    /**
+     * Integration secret identifier for the external LLM API key.
+     */
+    llm_api_key_ref?: string;
+
+    /**
+     * URL used to retrieve an access token when certificate authentication is enabled.
+     */
+    token_retrieval_url?: string;
+  }
+
+  export interface FallbackConfig {
+    external_llm?: FallbackConfig.ExternalLlm;
+
+    /**
+     * Integration secret identifier for the fallback model API key.
+     */
+    llm_api_key_ref?: string;
+
+    /**
+     * Fallback Telnyx-hosted model to use when the primary LLM provider is
+     * unavailable.
+     */
+    model?: string;
+  }
+
+  export namespace FallbackConfig {
+    export interface ExternalLlm {
+      /**
+       * Base URL for the external LLM endpoint.
+       */
+      base_url: string;
+
+      /**
+       * Model identifier to use with the external LLM endpoint.
+       */
+      model: string;
+
+      /**
+       * Authentication method used when connecting to the external LLM endpoint.
+       */
+      authentication_method?: 'token' | 'certificate';
+
+      /**
+       * Integration secret identifier for the client certificate used with certificate
+       * authentication.
+       */
+      certificate_ref?: string;
+
+      /**
+       * When `true`, Telnyx forwards the assistant's dynamic variables to the external
+       * LLM endpoint as a top-level `extra_metadata` object on the chat completion
+       * request body. Defaults to `false`. Example payload sent to the external
+       * endpoint:
+       * `{"extra_metadata": {"customer_name": "Jane", "account_id": "acct_789", "telnyx_agent_target": "+13125550100", "telnyx_end_user_target": "+13125550123"}}`.
+       * Distinct from OpenAI's native `metadata` field, which has its own size and type
+       * limits.
+       */
+      forward_metadata?: boolean;
+
+      /**
+       * Integration secret identifier for the external LLM API key.
+       */
+      llm_api_key_ref?: string;
+
+      /**
+       * URL used to retrieve an access token when certificate authentication is enabled.
+       */
+      token_retrieval_url?: string;
+    }
+  }
+
+  /**
+   * Reference to a connected integration attached to an assistant. Discover
+   * available integrations with `/ai/integrations` and connected integrations with
+   * `/ai/integrations/connections`.
+   */
+  export interface Integration {
+    /**
+     * Catalog integration ID to attach. This is the `id` from the integrations catalog
+     * at `/ai/integrations` (the same value also appears as `integration_id` on
+     * entries returned by `/ai/integrations/connections`). It is **not** the
+     * connection-level `id` from `/ai/integrations/connections`.
+     */
+    integration_id: string;
+
+    /**
+     * Optional per-assistant allowlist of integration tool names. When omitted or
+     * empty, all tools allowed by the connected integration are available to the
+     * assistant.
+     */
+    allowed_list?: Array<string>;
+  }
+
+  /**
+   * Settings for interruptions and how the assistant decides the user has finished
+   * speaking. These timings are most relevant when using non turn-taking
+   * transcription models. For turn-taking models like `deepgram/flux`, end-of-turn
+   * behavior is controlled by the transcription end-of-turn settings under
+   * `transcription.settings` (`eot_threshold`, `eot_timeout_ms`,
+   * `eager_eot_threshold`).
+   */
+  export interface InterruptionSettings {
+    /**
+     * Whether users can interrupt the assistant while it is speaking.
+     */
+    enable?: boolean;
+
+    /**
+     * Controls when the assistant starts speaking after the user stops. These
+     * thresholds primarily apply to non turn-taking transcription models. For
+     * turn-taking models like `deepgram/flux`, end-of-turn detection is driven by the
+     * transcription end-of-turn settings under `transcription.settings` instead.
+     */
+    start_speaking_plan?: InterruptionSettings.StartSpeakingPlan;
+  }
+
+  export namespace InterruptionSettings {
+    /**
+     * Controls when the assistant starts speaking after the user stops. These
+     * thresholds primarily apply to non turn-taking transcription models. For
+     * turn-taking models like `deepgram/flux`, end-of-turn detection is driven by the
+     * transcription end-of-turn settings under `transcription.settings` instead.
+     */
+    export interface StartSpeakingPlan {
+      /**
+       * Endpointing thresholds used to decide when the user has finished speaking.
+       * Applies to non turn-taking transcription models. For `deepgram/flux`, use
+       * `transcription.settings.eot_threshold` / `eot_timeout_ms` /
+       * `eager_eot_threshold`.
+       */
+      transcription_endpointing_plan?: StartSpeakingPlan.TranscriptionEndpointingPlan;
+
+      /**
+       * Minimum seconds to wait before the assistant starts speaking.
+       */
+      wait_seconds?: number;
+    }
+
+    export namespace StartSpeakingPlan {
+      /**
+       * Endpointing thresholds used to decide when the user has finished speaking.
+       * Applies to non turn-taking transcription models. For `deepgram/flux`, use
+       * `transcription.settings.eot_threshold` / `eot_timeout_ms` /
+       * `eager_eot_threshold`.
+       */
+      export interface TranscriptionEndpointingPlan {
+        /**
+         * Seconds to wait after the transcript ends without punctuation.
+         */
+        on_no_punctuation_seconds?: number;
+
+        /**
+         * Seconds to wait after the transcript ends with a number.
+         */
+        on_number_seconds?: number;
+
+        /**
+         * Seconds to wait after the transcript ends with punctuation.
+         */
+        on_punctuation_seconds?: number;
+      }
+    }
+  }
+
+  /**
+   * Reference to an MCP server attached to an assistant. Create and manage MCP
+   * servers with the `/ai/mcp_servers` endpoints, then attach them to assistants by
+   * ID.
+   */
+  export interface McpServer {
+    /**
+     * ID of the MCP server to attach. This must be the `id` of an MCP server returned
+     * by the `/ai/mcp_servers` endpoints.
+     */
+    id: string;
+
+    /**
+     * Optional per-assistant allowlist of MCP tool names. When omitted, the assistant
+     * uses the MCP server's configured `allowed_tools`.
+     */
+    allowed_tools?: Array<string>;
+  }
+
+  /**
+   * Configuration for post-conversation processing. When enabled, the assistant
+   * receives one additional LLM turn after the conversation ends, allowing it to
+   * execute tool calls such as logging to a CRM or sending a summary. The assistant
+   * can execute multiple parallel or sequential tools during this phase.
+   * Telephony-control tools (e.g. hangup, transfer) are unavailable
+   * post-conversation. Beta feature.
+   */
+  export interface PostConversationSettings {
+    /**
+     * Whether post-conversation processing is enabled. When true, the assistant will
+     * be invoked after the conversation ends to perform any final tool calls. Defaults
+     * to false.
+     */
+    enabled?: boolean;
+  }
+}
+
 export interface VersionRetrieveParams {
   /**
    * Path param
@@ -225,10 +530,22 @@ export interface VersionUpdateParams {
   dynamic_variables?: { [key: string]: unknown };
 
   /**
-   * Body param: If the dynamic_variables_webhook_url is set for the assistant, we
-   * will send a request at the start of the conversation. See our
-   * [guide](https://developers.telnyx.com/docs/inference/ai-assistants/dynamic-variables)
-   * for more information.
+   * Body param: Timeout in milliseconds for the dynamic variables webhook. Must be
+   * between 1 and 10000 ms. If the webhook does not respond within this timeout, the
+   * call proceeds with default values. See the
+   * [dynamic variables guide](https://developers.telnyx.com/docs/inference/ai-assistants/dynamic-variables).
+   */
+  dynamic_variables_webhook_timeout_ms?: number;
+
+  /**
+   * Body param: If `dynamic_variables_webhook_url` is set, Telnyx sends a POST
+   * request to this URL at the start of the conversation to resolve dynamic
+   * variables. **Gotcha:** the webhook response must wrap variables under a
+   * top-level `dynamic_variables` object, e.g.
+   * `{"dynamic_variables": {"customer_name": "Jane"}}`. Returning a flat object will
+   * be ignored and variables will fall back to their defaults. See the
+   * [dynamic variables guide](https://developers.telnyx.com/docs/inference/ai-assistants/dynamic-variables)
+   * for the full request/response format and timeout behavior.
    */
   dynamic_variables_webhook_url?: string;
 
@@ -237,6 +554,16 @@ export interface VersionUpdateParams {
    */
   enabled_features?: Array<AssistantsAPI.EnabledFeatures>;
 
+  /**
+   * Body param
+   */
+  external_llm?: VersionUpdateParams.ExternalLlm;
+
+  /**
+   * Body param
+   */
+  fallback_config?: VersionUpdateParams.FallbackConfig;
+
   /**
    * Body param: Text that the assistant will use to start the conversation. This may
    * be templated with
@@ -259,23 +586,51 @@ export interface VersionUpdateParams {
   instructions?: string;
 
   /**
-   * Body param: This is only needed when using third-party inference providers. The
-   * `identifier` for an integration secret
+   * Body param: Connected integrations attached to the assistant. The catalog of
+   * available integrations is at `/ai/integrations`; the user's connected
+   * integrations are at `/ai/integrations/connections`. Each item references a
+   * catalog integration by `integration_id`.
+   */
+  integrations?: Array<VersionUpdateParams.Integration>;
+
+  /**
+   * Body param: Settings for interruptions and how the assistant decides the user
+   * has finished speaking. These timings are most relevant when using non
+   * turn-taking transcription models. For turn-taking models like `deepgram/flux`,
+   * end-of-turn behavior is controlled by the transcription end-of-turn settings
+   * under `transcription.settings` (`eot_threshold`, `eot_timeout_ms`,
+   * `eager_eot_threshold`).
+   */
+  interruption_settings?: VersionUpdateParams.InterruptionSettings;
+
+  /**
+   * Body param: This is only needed when using third-party inference providers
+   * selected by `model`. The `identifier` for an integration secret
    * [/v2/integration_secrets](https://developers.telnyx.com/api-reference/integration-secrets/create-a-secret)
-   * that refers to your LLM provider's API key. Warning: Free plans are unlikely to
-   * work with this integration.
+   * that refers to your LLM provider's API key. For bring-your-own endpoint
+   * authentication, use `external_llm.llm_api_key_ref` instead. Warning: Free plans
+   * are unlikely to work with this integration.
    */
   llm_api_key_ref?: string;
 
+  /**
+   * Body param: MCP servers attached to the assistant. Create MCP servers with
+   * `/ai/mcp_servers`, then reference them by `id` here.
+   */
+  mcp_servers?: Array<VersionUpdateParams.McpServer>;
+
   /**
    * Body param
    */
   messaging_settings?: AssistantsAPI.MessagingSettings;
 
   /**
-   * Body param: ID of the model to use. You can use the
+   * Body param: ID of the model to use when `external_llm` is not set. You can use
+   * the
    * [Get models API](https://developers.telnyx.com/api-reference/chat/get-available-models)
-   * to see all of your available models,
+   * to see available models. If `external_llm` is provided, the assistant uses
+   * `external_llm` instead of this field. If neither `model` nor `external_llm` is
+   * provided, Telnyx applies the default model.
    */
   model?: string;
 
@@ -289,24 +644,42 @@ export interface VersionUpdateParams {
    */
   observability_settings?: AssistantsAPI.ObservabilityReq;
 
+  /**
+   * Body param: Configuration for post-conversation processing. When enabled, the
+   * assistant receives one additional LLM turn after the conversation ends, allowing
+   * it to execute tool calls such as logging to a CRM or sending a summary. The
+   * assistant can execute multiple parallel or sequential tools during this phase.
+   * Telephony-control tools (e.g. hangup, transfer) are unavailable
+   * post-conversation. Beta feature.
+   */
+  post_conversation_settings?: VersionUpdateParams.PostConversationSettings;
+
   /**
    * Body param
    */
   privacy_settings?: AssistantsAPI.PrivacySettings;
 
+  /**
+   * Body param: Tags associated with the assistant. Tags can also be managed with
+   * the assistant tag endpoints.
+   */
+  tags?: Array<string>;
+
   /**
    * Body param
    */
   telephony_settings?: AssistantsAPI.TelephonySettings;
 
   /**
-   * Body param
+   * Body param: IDs of shared tools to attach to the assistant. New integrations
+   * should prefer `tool_ids` over inline `tools`.
    */
   tool_ids?: Array<string>;
 
   /**
-   * Body param: The tools that the assistant can use. These may be templated with
-   * [dynamic variables](https://developers.telnyx.com/docs/inference/ai-assistants/dynamic-variables)
+   * Body param: Deprecated for new integrations. Inline tool definitions available
+   * to the assistant. Prefer `tool_ids` to attach shared tools created with the AI
+   * Tools endpoints.
    */
   tools?: Array<AssistantsAPI.AssistantTool>;
 
@@ -315,6 +688,11 @@ export interface VersionUpdateParams {
    */
   transcription?: AssistantsAPI.TranscriptionSettings;
 
+  /**
+   * Body param: Human-readable name for the assistant version.
+   */
+  version_name?: string;
+
   /**
    * Body param
    */
@@ -326,6 +704,242 @@ export interface VersionUpdateParams {
   widget_settings?: AssistantsAPI.WidgetSettings;
 }
 
+export namespace VersionUpdateParams {
+  export interface ExternalLlm {
+    /**
+     * Base URL for the external LLM endpoint.
+     */
+    base_url: string;
+
+    /**
+     * Model identifier to use with the external LLM endpoint.
+     */
+    model: string;
+
+    /**
+     * Authentication method used when connecting to the external LLM endpoint.
+     */
+    authentication_method?: 'token' | 'certificate';
+
+    /**
+     * Integration secret identifier for the client certificate used with certificate
+     * authentication.
+     */
+    certificate_ref?: string;
+
+    /**
+     * When `true`, Telnyx forwards the assistant's dynamic variables to the external
+     * LLM endpoint as a top-level `extra_metadata` object on the chat completion
+     * request body. Defaults to `false`. Example payload sent to the external
+     * endpoint:
+     * `{"extra_metadata": {"customer_name": "Jane", "account_id": "acct_789", "telnyx_agent_target": "+13125550100", "telnyx_end_user_target": "+13125550123"}}`.
+     * Distinct from OpenAI's native `metadata` field, which has its own size and type
+     * limits.
+     */
+    forward_metadata?: boolean;
+
+    /**
+     * Integration secret identifier for the external LLM API key.
+     */
+    llm_api_key_ref?: string;
+
+    /**
+     * URL used to retrieve an access token when certificate authentication is enabled.
+     */
+    token_retrieval_url?: string;
+  }
+
+  export interface FallbackConfig {
+    external_llm?: FallbackConfig.ExternalLlm;
+
+    /**
+     * Integration secret identifier for the fallback model API key.
+     */
+    llm_api_key_ref?: string;
+
+    /**
+     * Fallback Telnyx-hosted model to use when the primary LLM provider is
+     * unavailable.
+     */
+    model?: string;
+  }
+
+  export namespace FallbackConfig {
+    export interface ExternalLlm {
+      /**
+       * Base URL for the external LLM endpoint.
+       */
+      base_url: string;
+
+      /**
+       * Model identifier to use with the external LLM endpoint.
+       */
+      model: string;
+
+      /**
+       * Authentication method used when connecting to the external LLM endpoint.
+       */
+      authentication_method?: 'token' | 'certificate';
+
+      /**
+       * Integration secret identifier for the client certificate used with certificate
+       * authentication.
+       */
+      certificate_ref?: string;
+
+      /**
+       * When `true`, Telnyx forwards the assistant's dynamic variables to the external
+       * LLM endpoint as a top-level `extra_metadata` object on the chat completion
+       * request body. Defaults to `false`. Example payload sent to the external
+       * endpoint:
+       * `{"extra_metadata": {"customer_name": "Jane", "account_id": "acct_789", "telnyx_agent_target": "+13125550100", "telnyx_end_user_target": "+13125550123"}}`.
+       * Distinct from OpenAI's native `metadata` field, which has its own size and type
+       * limits.
+       */
+      forward_metadata?: boolean;
+
+      /**
+       * Integration secret identifier for the external LLM API key.
+       */
+      llm_api_key_ref?: string;
+
+      /**
+       * URL used to retrieve an access token when certificate authentication is enabled.
+       */
+      token_retrieval_url?: string;
+    }
+  }
+
+  /**
+   * Reference to a connected integration attached to an assistant. Discover
+   * available integrations with `/ai/integrations` and connected integrations with
+   * `/ai/integrations/connections`.
+   */
+  export interface Integration {
+    /**
+     * Catalog integration ID to attach. This is the `id` from the integrations catalog
+     * at `/ai/integrations` (the same value also appears as `integration_id` on
+     * entries returned by `/ai/integrations/connections`). It is **not** the
+     * connection-level `id` from `/ai/integrations/connections`.
+     */
+    integration_id: string;
+
+    /**
+     * Optional per-assistant allowlist of integration tool names. When omitted or
+     * empty, all tools allowed by the connected integration are available to the
+     * assistant.
+     */
+    allowed_list?: Array<string>;
+  }
+
+  /**
+   * Settings for interruptions and how the assistant decides the user has finished
+   * speaking. These timings are most relevant when using non turn-taking
+   * transcription models. For turn-taking models like `deepgram/flux`, end-of-turn
+   * behavior is controlled by the transcription end-of-turn settings under
+   * `transcription.settings` (`eot_threshold`, `eot_timeout_ms`,
+   * `eager_eot_threshold`).
+   */
+  export interface InterruptionSettings {
+    /**
+     * Whether users can interrupt the assistant while it is speaking.
+     */
+    enable?: boolean;
+
+    /**
+     * Controls when the assistant starts speaking after the user stops. These
+     * thresholds primarily apply to non turn-taking transcription models. For
+     * turn-taking models like `deepgram/flux`, end-of-turn detection is driven by the
+     * transcription end-of-turn settings under `transcription.settings` instead.
+     */
+    start_speaking_plan?: InterruptionSettings.StartSpeakingPlan;
+  }
+
+  export namespace InterruptionSettings {
+    /**
+     * Controls when the assistant starts speaking after the user stops. These
+     * thresholds primarily apply to non turn-taking transcription models. For
+     * turn-taking models like `deepgram/flux`, end-of-turn detection is driven by the
+     * transcription end-of-turn settings under `transcription.settings` instead.
+     */
+    export interface StartSpeakingPlan {
+      /**
+       * Endpointing thresholds used to decide when the user has finished speaking.
+       * Applies to non turn-taking transcription models. For `deepgram/flux`, use
+       * `transcription.settings.eot_threshold` / `eot_timeout_ms` /
+       * `eager_eot_threshold`.
+       */
+      transcription_endpointing_plan?: StartSpeakingPlan.TranscriptionEndpointingPlan;
+
+      /**
+       * Minimum seconds to wait before the assistant starts speaking.
+       */
+      wait_seconds?: number;
+    }
+
+    export namespace StartSpeakingPlan {
+      /**
+       * Endpointing thresholds used to decide when the user has finished speaking.
+       * Applies to non turn-taking transcription models. For `deepgram/flux`, use
+       * `transcription.settings.eot_threshold` / `eot_timeout_ms` /
+       * `eager_eot_threshold`.
+       */
+      export interface TranscriptionEndpointingPlan {
+        /**
+         * Seconds to wait after the transcript ends without punctuation.
+         */
+        on_no_punctuation_seconds?: number;
+
+        /**
+         * Seconds to wait after the transcript ends with a number.
+         */
+        on_number_seconds?: number;
+
+        /**
+         * Seconds to wait after the transcript ends with punctuation.
+         */
+        on_punctuation_seconds?: number;
+      }
+    }
+  }
+
+  /**
+   * Reference to an MCP server attached to an assistant. Create and manage MCP
+   * servers with the `/ai/mcp_servers` endpoints, then attach them to assistants by
+   * ID.
+   */
+  export interface McpServer {
+    /**
+     * ID of the MCP server to attach. This must be the `id` of an MCP server returned
+     * by the `/ai/mcp_servers` endpoints.
+     */
+    id: string;
+
+    /**
+     * Optional per-assistant allowlist of MCP tool names. When omitted, the assistant
+     * uses the MCP server's configured `allowed_tools`.
+     */
+    allowed_tools?: Array<string>;
+  }
+
+  /**
+   * Configuration for post-conversation processing. When enabled, the assistant
+   * receives one additional LLM turn after the conversation ends, allowing it to
+   * execute tool calls such as logging to a CRM or sending a summary. The assistant
+   * can execute multiple parallel or sequential tools during this phase.
+   * Telephony-control tools (e.g. hangup, transfer) are unavailable
+   * post-conversation. Beta feature.
+   */
+  export interface PostConversationSettings {
+    /**
+     * Whether post-conversation processing is enabled. When true, the assistant will
+     * be invoked after the conversation ends to perform any final tool calls. Defaults
+     * to false.
+     */
+    enabled?: boolean;
+  }
+}
+
 export interface VersionDeleteParams {
   assistant_id: string;
 }