Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.roark.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

The Kore AI integration connects an app on the Kore AI Agent Platform to Roark for chat simulations. Roark talks to your app over the Agent Platform v2 HTTP API — bootstrapping a session, sending each persona turn through /runs/execute, and tearing the session down when the conversation ends.
Kore AI is a chat-only integration in Roark. It does not support voice simulations or importing live calls. To test voice agents, use one of our voice platform integrations.

​
Prerequisites

Before connecting, you’ll need from the Kore AI Agent Platform:
  • An App ID (UUID) for the agent app you want to test
  • An Environment name the app is deployed to (e.g. production)
  • An API key (x-api-key) with permission to create sessions and execute runs against that app
  • The base URL of your Kore tenant, if you’re on a non-default or self-hosted Kore domain. Most customers can leave this blank and Roark will use https://agent-platform.kore.ai/api/v2.
See the Kore AI Agent Platform API reference for where to find these in the Kore console.

​
Creating the Integration in Roark

1

Open the integration form

Navigate to Settings → Integrations, click Add Integration, and select Kore AI.
2

Fill in the configuration

FieldDescription
Integration NameFriendly name for this integration
API KeyYour Kore x-api-key. Stored encrypted at rest.
App IDUUID of the Kore agent app
EnvironmentEnvironment name the app is deployed to (e.g. production)
Base URL (optional)Override the Kore API base URL for enterprise or self-hosted deployments. Defaults to https://agent-platform.kore.ai/api/v2.
3

Save

On save, Roark stores the credentials encrypted and auto-provisions:
  • One Roark agent named after the integration
  • One KORE chat endpoint linked to the integration
The endpoint is immediately usable in run plans. Credentials never leave the integration — the endpoint references them by ID.
In edit mode, leave the API Key field blank to keep the existing key. Only fill it in if you want to rotate the credential.

​
How Conversations Are Driven

Each chat simulation runs through a three-leg session lifecycle against your Kore app:
PhaseRequest
BootstrapPOST {baseUrl}/apps/{appId}/environments/{env}/sessions — creates a session and returns a session reference.
Per turnPOST {baseUrl}/apps/{appId}/environments/{env}/runs/execute — sends the persona’s message as text input under the bootstrapped session, and reads the agent’s reply from outputs[0].content.
TeardownPOST {baseUrl}/apps/{appId}/environments/{env}/sessions/terminate — closes the session when the chat ends.
All requests are sent with your x-api-key in the header. The API key is decrypted in memory only for the lifetime of the chat session and is never logged.

​
What’s Not Supported

  • Voice simulations — Kore AI integrations are chat-only in Roark.
  • Live monitoring / call import — Roark does not pull historical conversations from Kore. Chat simulations are the way to evaluate your Kore app’s behavior in Roark.

​
Next Steps

Run Chat Simulations

Test your Kore app with persona-driven chats

Build Scenarios

Define the conversations to test

Metric Policies

Automate evaluation on every chat

Integration Overview

Explore other integrations