Skip to main content
Setup steps and authentication are in the Overview. This page covers the inputs your evaluations consume.
An evaluator is the input to a run. The most important is a scenario — a structured test case describing what the simulated caller does and what the agent should achieve. Scenarios are paired with optional test profiles (transport / mode config), personalities (caller behavior), and dynamic variables (per-run overrides).

Scenarios

List, get, create, update, delete

Bulk update

The bulk-update payload is a single JSON object with a top-level scenarios list, plus any of metric_ids_to_add, metric_ids_to_remove, tool_ids_to_add, etc.
Prepare bulk.json:
Apply:

Generate scenarios

Cekura can generate scenario coverage from a description or an existing call.

Generate or improve scenario instructions

When you have a scenario shell and need Cekura to author (or rewrite) its instructions — for example, after you’ve added an expected_outcome and want the simulated caller’s script regenerated to match — use the instructions pipeline. It runs in the background and exposes a single progress endpoint.

Build a scenario from a transcript

Two flavors. create_from_transcript makes a brand-new scenario; update_with_transcript revises an existing one (useful when a production call exposes a scenario’s gap).

Scenario agent (interactive AI builder)

The scenario agent is an LLM-driven authoring loop — you describe an intent and it iterates on a scenario for you. Kicks off in the background.

Test profiles

A test profile bundles transport + mode settings (voice, text, SIP, livekit_v2, pipecat_v2, etc.) so you can reuse them across runs.

Personalities

Personalities define how the simulated caller behaves (interruptive, accented, polite, etc.). The catalog is platform-managed — you enable or disable items per project.

Dynamic variables

Dynamic variables let you parameterize a scenario at run time (e.g. customer name, account ID). Their values come from a test profile: attach one to the scenario, or pick profiles when you start the run. Each profile passed multiplies the run count.

See also

Agents

The agent under test that scenarios run against.

Runs & Results

Trigger evaluations using these scenarios.

Evaluator concepts

Conditional actions, mock tools, and design best practices.

API Reference

Full field reference for scenarios, test profiles, and personalities.