Skip to main content
POST
Run a kept eval set
Without run_id this starts a run of the set. With one it scores that run’s next cases. Each call scores up to 10 cases exactly as an unstored eval does, and keeps them. Each case counts as one answer against your monthly allowance, and the call is audited as assistant.eval_run. Call again with the run’s id until status is no longer running. Requires the owner, admin or editor role.
Off by default. These routes answer 404 unless the deployment has switched on ARUKZ_EVAL_HISTORY. See Answer quality evals.
string
required
The assistant (UUID). Another organization’s assistant returns 404.
string
required
The kept set to run. One that does not exist returns 404.
string
The run to continue, at most 64 characters. Absent starts a new run. A run that is already finished returns 409.

Response

The run so far, with every case scored.
string
required
The run.
string
required
The set it ran.
string
required
running, done or cannot_run. Treat a value you do not recognise as cannot_run.
string | null
required
Why it stopped, when it did.
integer
required
Cases in the set.
integer | null
required
Cases scored so far.
integer
required
Cases that passed.
string
required
Who started it.
string
required
When, RFC 3339.
string | null
required
When it finished, or null while it is running.
object[]
required
Each scored case, in order, as in Run an eval.
Last modified on November 11, 2026