Skip to main content
POST
Save a benchmark setup (Create a benchmark explains each setting). Saving samples the calls and spends no credit: the benchmark runs once it is started with start_or_resume_benchmark.

Parameters

Passed in the request body.
string
The email of the member of your organization this is for, recorded as the benchmark’s author, as who started it and as who gets the email when it is done. Defaults to the email of the person who created the API key, or for a key without one of the project’s creator. The response’s recorded_for_email gives the email recorded: tell the person, and send this to record another.
string
required
The benchmark’s name.
string[]
required
The call names the benchmark replays, as get_calls lists them.
object[]
The exploration deployments, as get_benchmark_candidates lists them. Each runs on a few examples first, and only those likely to meet an optimization objective run the full benchmark (steps of a benchmark).
object[]
The deployments that skip the exploration and go straight to the full benchmark, as get_benchmark_candidates lists them. A deployment is in one list only.
integer[]
The evaluators whose verdicts the recommendation counts, as get_evaluators lists them. This list and evaluators_for_reference together must include every always-used evaluator, and starting needs at least one evaluator.
integer[]
The evaluators that score and show the answers without counting in the recommendation. An evaluator is in one list only.
object
required
How the benchmark samples, replays and compares. Only period has no default.
string
The saved setup this one replaces, keeping its recorded person. Omit it to save a new setup.
string
An id you choose for this request. Sending it again after a timeout returns the setup it saved instead of saving another.
The response also carries blockers (what prevents the usual next step), in plain words. It is empty when the usual workflow applies.