Overview
The production counterpart of Simulation Results. Returns production evaluation sessions with their eval outcomes, newest first, whether those conversations arrived as uploaded transcripts or as live traces. No evaluation id required.Endpoint
Authentication
Query parameters
All filters are optional.string
Substring match on the evaluation run’s name, e.g.
Compliance V3.
Case-insensitive.string
Keep only sessions scored by the named eval, e.g.
Tone check. Substring match,
case-insensitive.boolean
default:"false"
Return only sessions with at least one failing eval, showing only the failing outcomes.
string
ISO 8601 timestamp. Sessions started at or after this moment.
string
ISO 8601 timestamp. Sessions started at or before this moment.
boolean
default:"false"
Include the conversation turns for each session.
integer
default:"0"
Number of sessions to skip.
integer
default:"50"
Sessions per page. Capped at 500.
run vs eval: a run is one batch job that scored N evals over M conversations
(“Compliance V3”). An eval is a single scoring criterion (“Tone check”). run is the
production analogue of simulation on the simulations endpoint.Example request
Response
array
The sessions on this page.
integer
Sessions matching the filters, across all pages.
integer
integer
Production sessions have no agent, scenario or persona. Those concepts exist only
for simulations, so the keys are absent rather than
null. Use
Simulation Results for simulation runs.What’s excluded
Sessions with no eval outcomes don’t appear. An evaluation creates one session per uploaded document, and the transcript parser then fans out into child sessions that carry all the outcomes, leaving the parent as a bookkeeping row with nothing to report.total
counts only sessions that actually have results.
Failures only
Withfailed_only=true, outcome_summary still describes the whole session, so
len(eval_outcomes) equals outcome_summary.failed_count and is deliberately smaller
than total_evaluations.