bench_id to select an exact spec version. agent_name with
benchmark_name selects that agent’s latest version; agent_id identifies ownership
but does not select a spec by itself.
1. Start a baseline
options (training options
describes each): val_num_tasks,
val_trajectories_per_task, val_max_concurrent_trajectories,
val_final_wait_timeout_seconds, reasoning_effort, temperature, top_p,
top_k, trajectory_timeout_seconds, max_output_tokens_per_turn,
max_output_tokens_per_trajectory, and max_turns_per_trajectory. Other options return
422. Use list_options to read evaluation defaults, or omit options to use them.
Training and standalone evaluation both default to 200 turns per trajectory.
An evaluation runs the spec’s test tasks; pass task_split="all" to include its
train tasks. Omit val_num_tasks to run every selected task. To evaluate a
ready deployment owned by the spec’s agent, pass deployment_id= instead of
base_model_slug; it uses the deployment’s sampling, token, and turn settings, so those
options return 422.
After task diagnostics, run a small evaluation to check the managed model, grader,
and published reward before a larger held-out baseline.
2. Read the score
status is completed; failed or cancelled runs are terminal too.
Read the mean reward after completion. A failed run can contain graded trajectories without
a published mean. Count attempted, graded, failed, and unfinished tasks before comparing
means, and retrieve a trajectory with include_reward_components=True to check its native
score, ending, and failure. client.evals.runs.list(bench_id) lists the spec’s evaluations.
Open the agent’s Evaluation tab for the same scores. See Use the platform
for direct run links.
To read what the model said, take a trajectory ID from those rewards and read its steps.
Each step holds the conversation so far, so the last step is the full transcript:
client.trajectories.retrieve(tid, include_steps=True) returns every step in one response;
for long trajectories, page with steps.list.
3. Score a checkpoint
val_* overrides. Explicit evaluation
options take precedence. A base-model evaluation uses evaluation defaults, so pass
the same explicit options to runs you compare. A capped evaluation on a new spec
version may select different tasks. Report per-task scores and coverage alongside the
mean. Then deploy a checkpoint that meets your criteria.