By AI Agent Metric - Kore.ai Docs

The By AI Agent metric lets supervisors configure AI-based evaluations on the Agent Platform. It uses a parent metric with multiple sub-metrics, each with its own question, weight, and logic. A single evaluation call processes all sub-metrics and returns results with justifications. Supervisors can pass requestMeta-based metadata propagation for the Execute API request. The system maps configured custom fields to key-value pairs and sends them in the Execute API request, with conversationId included by default. By AI Agent is available in two versions, By AI Agent V1 and By AI Agent V2 (Artemis). Both use the same parent and sub-metric model; they differ only in how they connect to the Agent Platform. You choose the version when you create the metric.

When to Use This Metric

Use this metric type for evaluation scenarios that require:

Scenario	Description
Multi-dimensional Assessments	Evaluate several facets (sub-metrics) under one parent metric.
Autonomous AI Analysis	Leverage AI agents to interpret, reason, and assess interactions using contextual understanding.
Weighted Evaluations	Assign different weights to sub-metrics to prioritize specific aspects.
Efficient Execution	Reduce redundant API calls by evaluating multiple sub-metrics within one agentic request.
Seamless Configuration	Select agentic applications from the same workspace without entering endpoint URLs.
Context-aware Evaluations	Pass custom metadata (for example, customer ID, ticket ID) to enable external data lookups during evaluation.

Prerequisites

Before creating a By AI Agent metric, confirm:

You have access to both Quality AI and Agent Platform.
The same workspace is available across both platforms.
You have permissions to view and deploy agentic applications.
The By AI Agent Metric feature is enabled for your workspace account.
You have configured at least one agentic app on the Agent Platform with the required response structure.
Custom fields exist in the Quality AI custom field registry to enable request metadata mapping.
For By AI Agent V2 (Artemis): you have access to Agent Platform V2 (Artemis) in the same workspace, and a deployed project with its Project Key, Project ID, Deployment ID, and Channel ID available.

If no agentic app is configured, the Agent App dropdown remains empty. If the agentic app response doesn’t match the required contract, Test Connection fails and blocks configuration.

Choose a Version: V1 or V2

When you add a By AI Agent metric, select the version that matches your Agent Platform integration.

By AI Agent V1: Connect using the existing Agent Platform V1 integration with your current configuration settings.
By AI Agent V2 (Artemis): Connect using Artemis/Agent Platform V2 with project-based authentication and advanced API configuration.

Capability	By AI Agent V1	By AI Agent V2 (Artemis)
Connection	Select an agentic app and environment from your workspace.	Connect to an Artemis project using Project Key, Project ID, Deployment ID, and Channel ID.
Authentication	Uses the current Agent Platform V1 configuration settings.	Project-key-based token, created and refreshed automatically by the system.
Sub-metrics and weightage	Supported.	Supported (same as V1).
Custom field propagation	Supported.	Supported (same as V1).
Audit logs	Standard evaluation results.	Adds a per-evaluation request payload, response, and debug trace.

Configure By AI Agent Metric

Step 1: Navigate to Metric Configuration

Navigate to Quality AI > Configure > Evaluation Forms > Evaluation Metrics.
Select + New Evaluation Metric.
From the Evaluation Metrics Measurement Type dropdown, select By AI Agent.
Select the version, By AI Agent V1 or By AI Agent V2 (Artemis).

Step 2: Create the Parent Metric

Enter a descriptive Name (for example, Compliance Disclosure).
Select the Language for the AI Agent’s evaluation.
The Question field is defined later under sub-metrics.

Step 3: Connect to the Agent Platform

Provide the connection details for the version you selected.

By AI Agent V1

In the Agent App dropdown, choose from available apps in your workspace.
Select the Environment (for example, Draft, Version 1, Version 2).

By AI Agent V2 (Artemis)

Enter the details of the Artemis project to evaluate against:

Field	Description
Project Key	Identifies the Artemis project. The system uses it to create and periodically refresh the authentication token.
Project ID	Used with the authentication token to call the agent API and determine the specific agent.
Deployment ID	Identifies the specific agent deployment used for evaluation.
Channel ID	Identifies the channel that attributes the source of the request.

By AI Agent V2 uses project-key-based authentication. The system creates the authentication token from the Project Key, refreshes it periodically, and sets the required origin header on the run API automatically, no manual token management is needed.

Step 4: Test Connection and Fetch Sub-Metrics

Select Test Connection.
The system sends a test call to the selected app and retrieves available sub-metrics for configuration.
On success, the panel confirms the connection and shows how many sub-metrics the agent application includes.

Test Connection behaves the same for V1 and V2. If the agentic app response doesn’t match the required contract, Test Connection fails and blocks configuration.

Step 5: Configure Sub-Metrics

Upon successful connection, the system displays all sub-metrics returned by the agentic app with their reference names. Select Edit next to the Weightage field to open the sub-metric configuration panel, where you can define the following:

Field	Description
Display Name	Label for the sub-metric.
Question	Evaluation question for this sub-metric.
Evaluation Criteria	Assign a weightage to each outcome (Yes / No).
Fatal Error	If enabled, failing this sub-metric marks the entire interaction as a critical failure.

Sub-metric weightages must add up to 100%, they split the score within the parent metric’s total.

Step 6: Configure Custom Field Propagation

Optionally configure custom fields to send to the Agent Platform as metadata for conversation-metadata-dependent evaluation. These fields populate the requestMeta object of the Execute API request.

Select a conversation-level Custom Field.
Define Header Name as the key in requestMeta.
Add multiple mappings using + Add Custom Field.

For Agent AI and Express sources, customConversationId is automatically included in requestMeta. When all details are configured, select Create to save the metric for AI Agent evaluation.

Setting up Response Format

Make sure that the Agent Platform response follows the required JSON contract for sub-metric evaluation.

Navigate to your AI Agent configuration in the Agent Platform.
Locate the Description field.
Follow the Response format specification.

Example Use Case: UDAP Compliance

For financial services compliance, a single parent metric can evaluate multiple aspects in one API call:

Sub-Metric	Weight	What It Evaluates
Fee Disclosure	25%	All applicable fees are clearly explained
Interest Rate Accuracy	30%	Interest rate information is accurate
Benefit Explanation	20%	Benefits are clearly described
Exclusion Details	15%	All exclusions are clearly listed
Terms Clarity	10%	Overall clarity of terms

Each sub-metric is evaluated independently with a single API call, providing detailed justifications for each aspect.

Evaluation Flow

The system sends a single evaluation request that includes:

Conversation data (transcripts and sub-metrics).
requestMeta (conversationId and configured custom fields).

The agent evaluates all sub-metrics and returns structured results. The system maps results and displays adherence with reasoning.

Request Metadata in Execute API

The system sends metadata in the requestMeta object of the Execute API. The requestMeta object includes:

Contents: The conversationId (always included for Agent AI and Express sources) and custom fields configured for the metric, represented as key-value pairs.
Custom Field Mapping Rules: The system derives keys from Header Names and sources values from conversation-level custom fields. It supports configuration of multiple custom fields per metric.

Example:

{
  "requestMeta": {
    "customConversationId": "AWS_Mono_22April0xxxx",
    "phone_number": "862684xxxx"
  }
}

This metadata is used only during evaluation execution and isn’t stored in the results.

Response Format for Sub-metrics

The Agent Platform must return responses in this JSON format for Quality AI to process sub-metric results:

{
  "botId": "string",
  "accountId": "string",
  "conversationId": "string",
  "agentEvaluation": [
    {
      "PARENTMETRIC_ID_VALUE": {
        "subMetrics": [
          {
            "subMetricId": "string",
            "subMetricName": "string",
            "justification": "string",
            "messageIds": ["array"],
            "timestamps": ["array"],
            "source": "agent | customer",
            "isQualified": "YES | NO | NA",
            "failureReason": "string"
          }
        ]
      }
    }
  ]
}

Sample Response

{
  "botId": "bot_001",
  "accountId": "account_001",
  "conversationId": "conv_001",
  "agentEvaluation": [
    {
      "eval_001": {
        "subMetrics": [
          {
            "subMetricId": "sm_001",
            "subMetricName": "Loan Inquiry Identification",
            "justification": "Agent correctly identified the customer's loan-related query.",
            "messageIds": ["msg_001"],
            "timestamps": ["2025-10-17T10:00:00Z"],
            "source": "agent",
            "isQualified": "YES",
            "failureReason": ""
          },
          {
            "subMetricId": "sm_002",
            "subMetricName": "Loan Eligibility Explanation",
            "justification": "Agent provided loan eligibility information.",
            "messageIds": ["msg_002", "msg_004"],
            "timestamps": ["2025-10-17T10:00:10Z", "2025-10-17T10:00:35Z"],
            "source": "agent",
            "isQualified": "YES",
            "failureReason": ""
          }
        ]
      }
    }
  ]
}

The Agent Platform contract strictly defines the response format, and no one can modify it. Quality AI only consumes and maps the response.

Audit Logs (By AI Agent V2)

For By AI Agent V2 (Artemis) metrics, the Audit Screen records an audit log for each evaluation so you can review and debug agent calls. The log lists one entry per sub-metric evaluation:

Column	Description
Timestamp	Date and time of the evaluation call.
Request Payload	The payload sent to the agent API.
Response	The response returned by the agent.
Sub-metric	The sub-metric evaluated in the call.
Status	Outcome of the call, Success or Failed.
View Payload	Opens the full request and response, including the trace, for debugging.

Managing Evaluation Metrics

Edit and Delete Evaluation Metrics

Steps to edit and delete existing Evaluation Metrics:

Select an AI Agent metric.
Select Edit to update the required metric details and fields.

When you update a By AI Agent V2 connection field (Project Key, Project ID, Deployment ID, or Channel ID), the system records a change log entry, for example: “Project ID was updated from {old value} to {new value} for metric {metric name} of type By AI Agent.”

Delete Evaluation Metrics

Before deleting a metric:

Remove it from all associated evaluation forms (for example, Chat Form – COMMON, New Points Based).
Reassign any linked attributes (for example, Agent AI Metric Attribute-1) to a different metric.

The system allows deletion only after you resolve all dependencies and save the changes.

​When to Use This Metric

​Prerequisites

​Choose a Version: V1 or V2

​Configure By AI Agent Metric

​Step 1: Navigate to Metric Configuration

​Step 2: Create the Parent Metric

​Step 3: Connect to the Agent Platform

​By AI Agent V1

​By AI Agent V2 (Artemis)

​Step 4: Test Connection and Fetch Sub-Metrics

​Step 5: Configure Sub-Metrics

​Step 6: Configure Custom Field Propagation

​Setting up Response Format

​Example Use Case: UDAP Compliance

​Evaluation Flow

​Request Metadata in Execute API

​Response Format for Sub-metrics

​Sample Response

​Audit Logs (By AI Agent V2)

​Managing Evaluation Metrics

​Edit and Delete Evaluation Metrics

​Delete Evaluation Metrics

When to Use This Metric

Prerequisites

Choose a Version: V1 or V2

Configure By AI Agent Metric

Step 1: Navigate to Metric Configuration

Step 2: Create the Parent Metric

Step 3: Connect to the Agent Platform

By AI Agent V1

By AI Agent V2 (Artemis)

Step 4: Test Connection and Fetch Sub-Metrics

Step 5: Configure Sub-Metrics

Step 6: Configure Custom Field Propagation

Setting up Response Format

Example Use Case: UDAP Compliance

Evaluation Flow

Request Metadata in Execute API

Response Format for Sub-metrics

Sample Response

Audit Logs (By AI Agent V2)

Managing Evaluation Metrics

Edit and Delete Evaluation Metrics

Delete Evaluation Metrics