Applications

Introduction

• Refer to DIAL-Native Applications to learn about applications in DIAL.
• Refer to Tutorials to learn how to enable applications in DIAL.

Main Screen

On this screen, you can access all the available application deployments in your instance of DIAL. Applications displayed in this section were either added by a direct modification of the DIAL Core config file or via DIAL Admin. Here, you can also create and manage new application deployments.

Note: This section does not display applications in either private user folders or the public folder in DIAL file storage. Applications in private folders are available only to their owners. Applications in public folder are accessible in Assets/Applications section.

Applications grid

TIP: Use the Columns selector to customize which columns are visible in the grid and their order.

Field	Description
Display Name	Name of the application (e.g. "Data Clustering Application") rendered on UI.
Version	Semantic identifier of the application version (e.g. 1.0.0).
Description	Brief free-text summary describing the application (e.g. "Clusters incoming text into semantic groups").
ID	Unique identifier used in the DIAL dynamic settings (e.g. dca, support-bot). This is the path segment of the Application's HTTP endpoint.
Source type	The type of the source used to create application: Endpoints, App Runner or Application Container.
Source	Name, URI or other identifier of the source used to create application.
Author	Information about the application's author.
Topics	Tags or categories (e.g. "finance," "support," "image-capable") you can assign for discovery, filtering, or grouping in large deployments. Helps end users and admins find the right application by the use case.
Attachment types	Types of attachments this application can accept according to MIME types.
Max attachment number	Maximum number of attachments allowed in a single request.
Status	Current status of the application: - Valid: application configuration is compatible with the JSON schema or the related application runner. Only valid entities will be materialized into the DIAL Core configuration. - Invalid: application configuration is incompatible with the JSON schema of the related application runner.
Creation Time	Entity creation timestamp.
Updated Time	Timestamp of the latest update of the entity.

Create

On the main screen you can add new application deployments.

Refer to Enable App to learn more about enabling applications in DIAL.

Follow these steps to add a new application deployment:

1. Click + Create to invoke the Create Application modal.

2. Define application's parameters

   Field	Required	Description
   ID	Yes	Unique identifier under the applications section of DIAL Core's dynamic settings (e.g. support-bot, data-cluster).
   Display Name	Yes	Name of the application (e.g. "Data Clustering Application") rendered on UI.
   Display version	No	Semantic identifier (e.g., 1.2.0) of an application's version.
   Description	No	Free-text summary describing the application (e.g. supported inputs, business purpose).
   Source Type	Yes	Source type of application. - Endpoints: Application with this source type is a standalone application. DIAL Core communicates with such application via the explicitly-provided chat and/or MCP endpoints. - App Runner: Application runners can be seen as application factories, allowing users to create logical instances of apps with different configurations. Application runners are based on JSON schemas, which define structure, properties and endpoints for applications. In Builders/Application Runners you can see all the available runners and add new ones. - Application Container: You can create applications based on running containers.
   Completion endpoint	Yes	Endpoint URL that will be used to process chat completion requests. Available if Source Type is Endpoints.
   Responses endpoint	No	Endpoint URL that supports OpenAI Responses API. Available if Source Type is Endpoints.
   MCP Endpoint	No	The application's MCP endpoint DIAL Core will use to communicate with application. Available if Source Type is Endpoints. -Transport: Transport used by MCP server for transmitting MCP messages between client and server. HTTP by default. -Forward per request key: Set this flag to true if you want a per-request key to be forwarded to the MCP endpoint allowing MCP server to access files in the DIAL storage. -Configuration delivery: Determines how application properties are sent to the MCP server. Choose Header to deliver application properties in Http header. Choose Meta to include application properties in _meta field within the MCP message payload.
   Application runner	Conditional	Select one of the available application runners. Available and is required if Source Type is Application runner.
   Container	Conditional	Select one of the running containers. Available and is required if Source Type is Application Container.

3. Once all required fields are filled click Create. The dialog closes and the new application configuration screen is opened. New application deployment appears immediately in the listing once created. It may take some time for the changes to take effect after saving.

   

Configuration

Click any application on the main screen to open the configuration section.

Properties

In the Properties tab, you can define the application's identity, routing, UI metadata, and other basic runtime controls.

Once configured, your application is ready to orchestrate models and interceptors behind a single HTTP endpoint.

Properties description

Field	Required	Editable	Description
ID	-	-	Unique key under applications in DIAL Core's dynamic settings (e.g. data-clustering, support-bot).
Updated Time	-	-	Date and time when the app's configuration was last updated.
Creation Time	-	-	Date and time when the app's configuration was created.
Status	-	-	Current status of the application: Valid: application configuration is compatible with the JSON schema or the related application runner. Only valid entities will be materialized into the DIAL Core configuration. Invalid: application configuration is incompatible with the JSON schema of the related application runner.
Sync with core	-	-	Indicates the state of the entity's configuration synchronization between Admin and DIAL Core. Synchronization occurs automatically every 2 mins (configurable via CONFIG_AUTO_RELOAD_SCHEDULE_DELAY_MILLISECONDS). Important: Sync state is not available for sensitive information (API keys/tokens/auth settings). Synced: Entity's states are identical in Admin and in Core for valid entities or entity is missing in Core for invalid entities. In progress...: If Synced conditions are not met and changes were applied within last 2 mins (this period is configurable via CONFIG_EXPORT_SYNC_DURATION_THRESHOLD_MS). Out of sync: If Synced conditions are not met and changes were applied more than 2 mins ago (this period is configurable via CONFIG_EXPORT_SYNC_DURATION_THRESHOLD_MS). Unavailable: Displayed when it is not possible to determine the entity's state in Core. This occurs if: - The config was not received from Core for any reason. - The configuration of entities in Core is not entirely compatible with the one in the Admin service.
Display Name	Yes	Yes	Application name displayed on UI (e.g. "Data Clustering Application"). Helps end user to identify and select applications.
Display version	No	Yes	Semantic identifier of the application version (e.g. 1.0.0).
Description	No	Yes	Free-text summary describing the application (e.g. tooling, supported inputs/outputs, SLAs).
Maintainer	No	Yes	Email address of the person or team responsible for the application.
Icon	No	Yes	Logo to visually distinguish the app on the UI.
Topics	No	Yes	Topics are semantic labels that you can assign to apps (e.g. "finance", "support") for better navigation on UI. Click to display a list of available topics. You can add your own custom topics to the list following these rules: - The topic name must not exceed 255 characters. - The topic name must not contain leading or trailing spaces.
Source Type	Yes	Yes	Source type of application. - Endpoints: Application with this source type is a standalone application. DIAL Core communicates with such application via the explicitly-provided chat completion, responses and/or MCP endpoints. - Application runner: Application runners can be seen as application factories, allowing users to create logical instances of apps with different configurations. Application runners are based on JSON schemas, which define structure, properties and endpoints for applications. Select one of the available application runners. If the application is created based on an application runner, DIAL Core will forward all payloads to endpoints defined in the application runner configuration. - Application Container: You can create applications based on running containers.
Container	Conditional	Yes	Application Container used to create application. Available and is required if Source Type is Application Container.
Application runner	Conditional	Yes	Select one of the available application runners. Available and is required if Source Type is Application runner.
Completion endpoint	Yes	Conditional	Endpoint URL that will be used to process chat completion requests. Editable if Source Type is Endpoints. Partially editable (base URL if determined by the selected container and the endpoint path is editable) if Source Type is Application Container Read-only if Source Type is Application Runner.
Responses endpoint	No	Conditional	Endpoint URL that supports OpenAI Responses API. Editable if Source Type is Endpoints.
MCP Endpoint	No	Conditional	The application's MCP endpoint DIAL Core will use to communicate with application. Editable if Source Type is Endpoints. Partially editable (base URL of the selected container is fixed and the endpoint path is editable) if Source Type is Application Container. -Transport: Transport used by MCP server for transmitting MCP messages between client and server. HTTP by default. -Forward per request key: Set this flag to true if you want a per-request key to be forwarded to the MCP endpoint allowing MCP server to access files in the DIAL storage. -Configuration delivery: Determines how application properties are sent to the MCP server. Choose Header to deliver application properties in Http header. Choose Meta to include application properties in _meta field within the MCP message payload.
Viewer URL	No	Conditional	URL of the application's custom UI. A custom UI, if enabled, will override the standard DIAL Chat UI. Available and editable if Source Type is Endpoints.
Editor URL	No	Conditional	URL of the application's custom builder UI. Application builder allows creating instances of apps using a UI wizard. Available and editable if Source Type is Endpoints.
Attachment types	No	Yes	Use to define the attachment types (images, files) this app can have: Available values: No attachments: Disables all attachment types. All attachments types: Allows all types of file attachments. Optionally specify max number of attachments. Specific attachments types: Enables the user to define/select specific MIME types. Start typing to see suggestions or use <type>/<subtype> format for a manual entry.
Attachments max number	No	Yes	Maximum number of input attachments. Enabled if attachment types are defined.
Forward auth token	No	Yes	This parameter allows to determine whether to forward an Auth Token to your apps's endpoint. If enabled, HTTP header with authorization token is forwarded to chat completion endpoint.
Max retry attempts	No	Yes	Number of times DIAL Core will retry a failed run (due to timeouts or 5xx errors).
Completion Defaults	No	Yes	Default parameters are applied if a request doesn't contain them in OpenAI chat/completions API call.
Responses Defaults	No	Conditional	Default parameters are applied if a request doesn't contain them in OpenAI openai/v1/responses API call. Available and editable if OpenAI Responses API is supported.

Tools Overview

Important: This section is enabled for application deployments with the Source Type = Endpoints/MCP or Source Type = Application Runner and the related Application Runner has MCP endpoint enabled as the Source Type.

Tools are functions supported by an MCP server that can be used by clients to perform specific actions. On this screen, you can discover, manage and try all the available tools.

Refer to Toolsets to learn more about the purpose and functionality of this section.

Features

In the Features tab, you can control optional capabilities of applications.

The difference between model and application features

While Model feature flags govern what each AI model integration can do, Application feature flags define which of those capabilities your orchestrated service exposes to clients. Also, you can plug in custom preprocessing endpoints.

Scope

• Model features apply per AI model, controlling what the model endpoint itself supports (e.g. whether GPT-4 can accept system prompts or function calls).
• Application features apply per orchestrated service, governing what your composed workflow will accept and pass through—regardless of which models are called under the hood.

Override Capability

• At the application level, you can disable a feature globally (even if models support it) or plug in custom endpoints that apply above all models.
• At the model level, toggles only reflect the true capabilities of that specific AI model integration.

Use Cases

• Model toggles ensure you don’t accidentally send unsupported parameters to a given model.
• Application toggles let you present a consistent API to your clients (e.g. always accept temperature or never allow attachments), even if different underlying models behave differently.

Endpoints

You can override or extend DIAL Core's built-in protocol calls with your own HTTP services. Here, you can specify endpoints used by Application Runners (e.g. a Python or Node Runner) to perform preprocessing or policy checks before delegating to your underlying models and workflows.

Field	Description
Rate endpoint	URL to call a custom rate-estimation API. Use this to compute cost or quota usage based on your own logic (e.g. grouping by tenant, complex billing rules).
Tokenize endpoint	URL to call a custom tokenization service. When you need precise, app-wide token counting (for mixed-model or multi-step prompts) that the model adapter can't provide.
Truncate prompt endpoint	URL to call your own prompt-truncation API. Handy if you implement advanced context-window management (e.g. dynamic summarization) before the actual application call.
Configuration endpoint	URL to fetch JSON Schema describing settings of the DIAL application. DIAL Core exposes this endpoint to DIAL clients as GET v1/deployments/<deployment name>/configuration. DIAL client must provide a JSON value corresponding to the configuration JSON Schema in a chat completion request in the custom_fields.configuration field.

Feature Flags (Toggles)

Enable or disable per-request options that your application accepts from clients and forwards to the underlying models. Toggle On/Off any feature as needed.

Note: Changes take effect immediately after saving.

Toggle	Description
System prompt	Enables an initial "system" message injection. Useful for orchestrating multi-step agents where you need to enforce a global policy at the application level.
Tools	Enables tools/functions payloads in API calls. Switch on if your application makes external function calls (e.g. calendar lookup, database fetch).
Seed	Enables the seed parameter for reproducible results. Great for testing or deterministic pipelines. Disable to ensure randomized creativity.
URL Attachments	Enables URL references (images, docs) as attachments in API requests. Must be enabled if your workflow downloads or processes remote assets via URLs.
Folder Attachments	Enables attachments of folders (batching multiple files).
Assistant attachments in request	Indicates whether the application supports attachments in messages from role=assistant in chat completion request. When set to true, DIAL Chat preserves attachments in messages in the chat completion requests to DIAL Core, instead of removing them. The feature is especially useful for apps that can generate attachments as well as take attachments in its input.
Accessible by request key	Indicates whether the deployment is accessible using a per-request API key.
Content parts	Indicates whether the deployment supports requests with content parts or not.
Consent required	Indicates whether the application requires user consent before use.
Support comment in rate response	Indicates whether the application supports the field comment in rate response payload.

Parameters

If the application is created based on Application Runner, the content of this screen is determined by the parameters of the related Application Runner. Here, you can configure application-specific parameters that influence its behavior.

Refer to Schema-rich Applications to learn more.

Roles

In the Roles tab, you can create and manage roles that have access to the selected application. Roles are defined in the Access Management section. Here, you can define user groups that can use specific applications and define rate limits for them.

Important: if roles are not selected for a specific application or Make available to specific roles toggle is disabled, it will be available to all user roles.

• Refer to Access & Cost Control to learn more about access control in DIAL.
• Refer to Roles to learn more about roles in DIAL.
• Refer to tutorials to learn how to configure access and limits for JWT and API keys

Roles grid

Column	Description
Display Name	Unique role name.
ID	Unique role identifier.
Description	Description of the role (e.g., "Admin, Prompt Engineer, Developer").
Tokens per minute	Per Minute tokens limit for a specific role. Blank = no limits. Inherits the default value. Can be overridden.
Tokens per day	Daily tokens limit for a specific role. Blank = no limits. Inherits the default value. Can be overridden.
Tokens per week	Weekly tokens limit for a specific role. Blank = no limits. Inherits the default value. Can be overridden.
Tokens per month	Monthly tokens limit for a specific role. Blank = no limits. Inherits the default value. Can be overridden.
Actions	Additional role-specific actions. When Make available to specific roles toggle is off - opens the Roles section in a new tab. When Make available to specific roles toggle is on, you can open the Roles section in a new tab, set Set unlimited, Remove the role from the list or Reset to default limits.

Set Rate Limits

The grid on the Roles screen lists roles that can access a specific application. Here, you can also set individual limits for selected roles. For example, you can give "Admin" role unlimited monthly tokens but throttle "Developer" to 100,000 tokens/day or allow the "External Partner" role a small trial quota (e.g., 10,000 tokens/month) before upgrade.

To set or change rate limits for a role:

1. Click in the desired cell (e.g., Tokens per day for the "ADMIN").
2. Enter a numeric limit or leave blank to set no limits. Click Reset to default limits to restore default settings for all roles.
3. Click Save to apply changes.

Default Rate Limits

Default rate limits are set for all roles in the Roles grid by default; however you can override them for any role.

Field	Description
Default tokens per minute	The maximum tokens any user can consume per minute unless a specific limit is in place.
Default tokens per day	The maximum tokens any user can consume per day unless a specific limit is in place.
Default tokens per week	The maximum tokens any user can consume per week unless a specific limit is in place.
Default tokens per month	The maximum tokens any user may consume per month unless a specific limit is in place.

Role-Specific Access

Use Make available to specific roles toggle to define access to the application:

• Off: Application is callable by any authenticated user. All existing user roles are in the grid.
• On: Application is restricted - only selected roles can access the application. If empty, the application is not available to any role.

Add

You can add a role only if Make available to specific roles toggle is On.

1. Click + Add (top-right of the Roles Grid).
2. Select one or more roles in the modal. The list or roles is defined in the Access Management section.
3. Confirm to add role(s) to the table.

Remove

You can remove a role only if Make available to specific roles toggle is On.

1. Click the actions menu in the role's line.
2. Choose Remove in the menu.

Interceptors

DIAL uses Interceptors to add custom logic to in/out requests for models and apps, enabling PII obfuscation, guardrails, safety checks, and beyond.

You can define Interceptors in the Entities → Interceptors section to add them to the processing pipeline of DIAL Core.

Refer to Interceptors to learn more.

In the Interceptors tab of an application configuration, you can preview global and interceptors defined on the application runner level and also define local interceptors specific to this application.

The difference between model and application interceptors

Scope of Invocation

• Model: Interceptors are triggered with each request to a model (i.e. before/after the LLM invocation).
• Application: Interceptors wrap the entire orchestrated workflow, including multi-model sequences and branching logic.

Use Cases

• Model: Ideal for prompt "pre-processing" or response transformations that are specific for each LLM.
• Application: Manage cross-cutting concerns across the whole application (e.g., tenant-based routing, unified logging, end-to-end policy enforcement).

Interceptors grid

Column	Description
Order	Execution sequence. Interceptors run in ascending order (1 → 2 → 3...). A request will flow through each interceptor's in this order. Response interceptors are invoked in the reversed order.
Display Name	The interceptor's alias, matching the Name field in its definition.
Description	Free-text summary from the interceptor's definition, explaining its purpose.
ID	Unique identifier of the interceptor.
Actions	Additional interceptor-specific actions. Open interceptor in a new tab. Remove the selected interceptor from the app's configuration.

Add

1. Click + Add (in the upper-right of the interceptors grid).
2. In the Add Interceptors modal, choose one or more from the grid of defined interceptors.
3. Apply to append them to the bottom of the list (are added in the same order as selected in the modal).

TIP: If you need a new interceptor, first create it under Entities → Interceptors and then revisit this tab to attach it to the application's configuration.

Reorder

1. Drag & Drop the handle (⋮⋮⋮⋮) to reassign the order in which interceptors are triggered.
2. Release to reposition; order renumbers automatically.
3. Save to lock-in the new execution sequence.

Remove

1. Click the actions menu in the interceptor's row.
2. Choose Remove to detach it from this application.
3. Save to lock-in the interceptors list

Dependencies

In interconnected systems, applications often rely on other applications or AI models to function, forming complex dependency chains. Access to sensitive data in such ecosystems can pose a challenge, especially when multiple applications interact and propagate requests, and can require an explicit consent from a user to allow an application/AI models to access their data or perform actions on their behalf.

Refer to Managing Authorization in Complex Application Ecosystems to learn more.

On this screen, you can find all dependencies configured for the selected application. Administrators can manually add new dependencies (by selecting from available AI models and applications) or remove the existing ones.

Column	Description
Entity Type	Indication whether dependent object is an Application or a Model.
ID	Identifier of the respective model or application.
Display Name	Descriptive name of the dependent model or application.
Version	Version of the dependent model.
Description	Additional textual details about the dependent model or application.
Actions	Allows to open the dependent object in new tab or remove it from the list of dependencies.

Add

1. Click + Add (in the upper-right of the dependencies grid).
2. Select the type of object to add: Application or Model.
3. In the modal window, choose model or application existing in DIAL from the grid.
4. Add to append them to the dependencies grid.

App Routes

In this section, you can defile routes that will be used by DIAL Core for interaction with application via specified endpoints.

If the application is created based on a specific application runner, tab allows only viewing routes inherited from it. Otherwise, it allows creating, viewing, editing, and deleting routes.

Refer to DIAL Core to learn more about routes.

Properties

In the Properties sub-tab you can configure route's identity and requests handling behavior.

Configuration of this tab is similar to routes. See Routes documentation for more information.

Attachments

In the Attachments sub-tab you can configure attachment paths for both requests and responses.

Roles

In the Roles sub-tab you can configure route-specific role assignments, allowing administrators to control access to each individual route.

Configuration of this tab is similar to routes. See Routes documentation for more information.

Audit

In the Audit tab, you can monitor key metrics, activities and usage related to the selected application. This tab provides comprehensive insights into application performance, user interactions, and operational changes. You can track real-time and historical data, identify usage patterns, audit and roll back all modifications made to the selected application for compliance and troubleshooting purposes.

Note: This section mimics the functionality available in the global Dashboard, Activity, and Usage Log sections, but is scoped specifically to the selected application.

JSON Editor

Advanced users with technical expertise can work with the application properties in a JSON editor view mode. It is useful for advanced scenarios of bulk updates, copy/paste between environments, or tweaking settings not exposed on UI.

TIP: You can switch between UI and JSON only if there are no unsaved changes.

In JSON editor, you can use the view dropdown to select between Admin format and Core format. Note, that these formatting options are for your convenience only and do not render properties as they are defined in DIAL Core. After making changes, the Sync with core indicator on the main configuration screen will inform you about the synchronization state with DIAL Core.

Working with JSON Editor

1. Navigate to Entities → Applications, then select the application you want to edit.
2. Click the JSON Editor toggle (top-right). The UI reveals the raw JSON.
3. Chose between the Admin and Core format to see and work with properties in the necessary format. Note: Core format view mode does not render the actual configuration stored in DIAL Core but the configuration in Admin service displayed in the DIAL Core format.
4. Make changes and click Save to apply them.
5. After making changes, the Sync with core indicator on the main configuration screen will inform you about the synchronization state with DIAL Core.

Delete

Use the Delete button in the Configuration screen toolbar to permanently remove the selected application.