Skip to main content

Documentation Index

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

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).

Scenarios

List, get, create, update, delete

# List scenarios for an agent
cekura scenarios list --agent-id 123

# Get one
cekura scenarios get 9876

# Create from a JSON file
cekura scenarios create --from-file my_scenario.json

# Update one
cekura scenarios update 9876 --from-file patch.json

# Delete
cekura scenarios delete 9876

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:
{
  "scenarios": [
    { "id": 101, "tags": ["regression"] },
    { "id": 102, "tags": ["smoke"] }
  ],
  "metric_ids_to_add": [55],
  "tool_ids_to_remove": [12]
}
Apply:
cekura scenarios bulk-update --from-file bulk.json

Generate scenarios

Cekura can generate scenario coverage from a description or an existing call.
cekura scenarios generate --agent-id 123 --description "Bookings flow — happy path and reschedules" --count 10
cekura scenarios generate-progress --progress-id <id>

Test profiles

A test profile bundles transport + mode settings (voice, text, SIP, livekit_v2, pipecat_v2, etc.) so you can reuse them across runs.
cekura test-profiles list --agent-id 123
cekura test-profiles create --from-file profile.json
cekura test-profiles update 7 --from-file patch.json

Personalities

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

# Enable / disable on a project
cekura personalities enable-for-project 742 --personalities 3,29
cekura personalities disable-for-project 742 --personalities 3

Dynamic variables

Dynamic variables let you parameterize a scenario at run time (e.g. customer name, account ID).
Manage variables on an agent:
cekura agents dynamic-variables list 123
cekura agents dynamic-variable-create 123 --from-file vars.json
Pass values inline when triggering a run:
cekura scenarios run-text \
  --agent-id 123 \
  --scenario-ids 101 \
  --dynamic-variables '{"customer_name":"Alex","account_id":"A-552"}'

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.