Skip to main content
GET
Get a combined report across results

Authorizations

X-CEKURA-API-KEY
string
header
required

API Key Authentication. It should be included in the header of each request.

Query Parameters

result_ids
string
required

Results to combine — comma-separated string (e.g. '5591,5592'), not a JSON array.

run_filters
string

Optional JSON-encoded filter object restricting which runs the report counts. Every aggregate in the response is computed over the matching runs only. Invalid JSON returns 400.

join is and (every filter must match) or or (any filter may match). Each item in filters has an id (the run field), an operator and a value.

Supported filters:

  • successequals with true or false
  • statusequals with one run status, e.g. "completed"
  • idequals or in with run IDs
  • scenariosin with scenario IDs
  • tagsin with scenario tags; a run matches if its scenario carries any of them
  • scenario_name, call_ended_reasonin with a list of values
  • metrics — no top-level operator; value is a list of metric conditions, each with the metric id and an operator: equals (with value), greaterThanOrEqual / lessThanOrEqual (with value), range (with min and max), or exists / notExists

Example — failed runs from two scenarios whose metric 101 scored at least 3:

ql
string
default:{-runs}

Field selection. {-runs} (the default) returns the aggregates only; {*} additionally embeds every run and can be very large.

agent_id
integer

Tenant scope. Supply one of agent_id, assistant_id, project_id when authenticating with a user session or OAuth bearer token; omit when using an API key already scoped to the tenant.

assistant_id
string

Tenant scope. Supply one of agent_id, assistant_id, project_id when authenticating with a user session or OAuth bearer token; omit when using an API key already scoped to the tenant.

project_id
integer

Tenant scope. Supply one of agent_id, assistant_id, project_id when authenticating with a user session or OAuth bearer token; omit when using an API key already scoped to the tenant.

Response

status
string
required

Always 'completed' — the report is computed on read, not queued.

success_rate
number<double>
required

Percentage of runs that passed, across every result in the report

total_runs_count
integer
required

Runs in the report, including those still executing

completed_runs_count
integer
required

Runs that reached a terminal state (completed, failed, timeout or cancelled)

success_runs_count
integer
required

Completed runs that passed

failed_runs_count
integer
required

Completed runs that failed

agent
integer
required

ID of the agent the results belong to

agent_version
any | null
required

Agent version every result ran against, or null when the results did not all run against the same version.

Example:

overall_evaluation
any
required

Aggregate evaluation across all runs in the report.

  • success_rate — percentage of runs that passed
  • metric_summary — keyed by metric ID. Every entry has id, name, type, score, errors (the scenarios whose runs failed the metric, with the failing run IDs) and overall_explanation. Enum metrics add enums (per enum value: score as a percentage, count and runs), numeric metrics add percentiles such as p50, and critical metrics add categories keyed by category ID
  • worst_performing_metricsbinary_adherence lists the IDs of binary metrics that did not pass on every run, lowest pass rate first
  • numeric_metrics — numeric metric averages with their percentiles, plus average ringing duration when available
  • enum_metrics — the metric ID of every enum evaluation, one entry per evaluated run
  • extra_metrics — derived figures such as average ringing duration and expected-outcome score

Example:

metrics
any
required

Metrics configured on the agent.

Example:

critical_categories
any
required

Critical-issue categories found across the runs, most critical first. Categories marked as not a bug and evaluations marked as wrong are excluded.

Example:

runs_by_tags
any
required

Keyed by scenario tag: the IDs of the runs whose scenario carries the tag and the success rate (percentage) of those runs.

Example:

latency_data
any
required

Response latency in milliseconds across all measured turns of all runs.

Example:

failed_reasons
any
required

Failure issues merged and deduplicated across the results, ranked by how many runs they affect.

Example:

performance_metrics
any
required

Per-metric performance across the runs, rubric metrics first. aggregate_unit is percent, value, score or an empty string. passed and threshold_text come from the project rubric; passed is null and in_rubric is false for metrics without a rubric rule. Enum metrics add enum_run_ids (run IDs per enum value), rating metrics add score_range_run_ids and expected-outcome metrics add review_required_run_ids.

Example:

runs
any

Every run in the report, keyed by run ID. Present only when ql selects it (e.g. {*}); the default {-runs} omits it.

Example: