Get the JSON report, with the execution trace
Available once lifecycle.report.status is REPORT_STATUS_AVAILABLE, which can precede cleanup. One entry
per accepted task with
its conversation, the per-turn trajectory (tool calls with arguments, outputs, status and timing; the tools the
agent could see; token usage), and the result of every grader by name. Failed tasks are included with an error
and no scores.
Responses are large for big batches; send Accept-Encoding: gzip. Visible to the user who created the run
and to the eval admins Moveworks designates for the org; any other id answers 404 RESOURCE_NOT_FOUND.
Authentication
OAuth 2.0 client-credentials bearer from POST /oauth/v1/token (same as the Conversations API). The token is issued to one org and bound to one user; the run executes in that org and its conversations run as that user. If the eval config names a source_org, it must be the same org. An org that is not enabled for the Eval API sees 404 NOT_FOUND (“API not found”) on every route. An enabled org whose credential is not entitled to run evals receives 403 REQUEST_ACCESS_DENIED. submitted_by.email_addr is the email of the user the credential is bound to.
Path parameters
Response
One entry per accepted task, in task-file order. Includes failed tasks.