Submit a replay task result
Submit the result of a replay task.
Authorizations
Enter your API key (e.g. dai_sk_test_key_001)
Headers
Path Parameters
Cookies
Body
Typed body for POST /replay/tasks/{id}/submit.
Every field is validated here rather than at the database, so a bad value comes back as a 422 naming the field instead of a 500 from the column type.
The bounds are not cosmetic. eval_score must be 0.0–1.0 because the
preference-pair export downstream splits pairs on a score threshold: a
score outside that range would put every pair on the same side of the
split and silently skew the exported training data. eval_verdict is
pass/fail/review — the same vocabulary score_replay_result emits and
the batch passed/failed counters count — and status is the replay-task
lifecycle set. extra="forbid" matches the decision payload: a mistyped
field name should 422 rather than quietly mean "no value supplied".
ID of the trace produced by re-running the prompt.
Quality score for the replayed trace (0.0–1.0).
0 <= x <= 1Verdict for the replayed trace.
pass, fail, review Lifecycle state to record on the task.
pending, running, completed, failed, skipped Response
Successful Response