Skip to main content
POST
Try an unsaved evaluator on one logged call of a call name: the candidate deployment answers the call again, and the evaluator scores its answer against the baseline’s, which is the answer production logged unless you name a baseline deployment. If the verdict is what you expect, save the evaluator with set_evaluator and use it in a benchmark.
Spends a little credit.

Parameters

Passed in the request body.
string
required
“judge” or “deterministic”.
string
required
The judge’s instruction in words, or the check’s Python code.
string
required
A call name, as get_calls lists them: the test runs on one logged call of that name, drawn at random from the last 30 days.
object
required
The deployment that answers the call again, to be scored.
object
The deployment whose answer the candidate is compared with. Omit it to compare with the answer production logged.
The response also carries blockers (what prevents the usual next step), in plain words. It is empty when the usual workflow applies.