Use this file to discover all available pages before exploring further.
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).
# List scenarios for an agentcekura scenarios list --agent-id 123# Get onecekura scenarios get 9876# Create from a JSON filecekura scenarios create --from-file my_scenario.json# Update onecekura scenarios update 9876 --from-file patch.json# Deletecekura scenarios delete 9876
from cekura import Cekuraclient = Cekura()# Listscenarios = client.scenarios.list(agent_id=123)# Get onescenario = client.scenarios.get(scenario_id=9876)# Createsc = client.scenarios.create( agent=123, name="Reschedule appointment", description="Caller wants to move their booking to next week", scenario_type="conversation", tags=["smoke"],)# Updateclient.scenarios.update(scenario_id=sc["id"], description="Updated wording")# Deleteclient.scenarios.delete(scenario_id=9876)
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.
Personalities define how the simulated caller behaves (interruptive, accented, polite, etc.). The catalog is platform-managed — you enable or disable items per project.
CLI
SDK
# Browse the catalogcekura personalities list# Enable / disable on a projectcekura personalities enable-for-project 742 --personalities 3,29cekura personalities disable-for-project 742 --personalities 3