Create eval suite
Create an eval suite (named test cases + graders) attached to one flow or agent, optionally with initial cases. Suites created here are dashboard/API-managed; config-as-code suites converge via POST /eval/ensure instead.
Authentication
Request
Ordered grader configs applied to every case (suite-level graders).
Make this the default eval for its target (clears the flag on any other suite for the same target).
How captured (saved_from_run) cases replay. “next_step” (default) captures the first tool intent and stops; “continue” serves recorded toolMocks and runs past the first action.
For “continue”-mode replays, what to do when a tool call has no matching mock: “fail” (default, divergence is the signal) or “stub” (canned success so the run keeps going). A replay never reaches the real tool.
Response
Ordered GraderConfig[] applied to every case.
The judge-trust corpus (E6 calibration): how often the AI grader agrees with your reviews, surfaced as a plain fraction. Null until at least one verdict has been reviewed (POST /eval/scores/{scoreId}/review).
Provenance of the last Definition write. ‘sdk’ / ‘terraform’ mean the suite is managed in code (converged by ensure on deploy).
How captured cases replay: “next_step” (default when null) or “continue”.
Unmatched-call policy for “continue”-mode replays: “fail” (default when null) or “stub”.
Display name of the target flow/agent; null when the target row is gone.