- spans — one per pipeline step, with the
input, the modeloutput, and (if a reviewer approved or edited it) anapprovedOutput - feedback — free-text comments left by reviewers, attached to specific spans
spans[].approvedOutput is the human-validated output and feedback[] is the reviewer’s commentary.
List traces
Query parameters
string
The project slug. Required if
projectId is not provided.string
The project UUID. Required if
projectSlug is not provided.Response
Example
Get a trace with spans and feedback
Path parameters
string
required
The trace UUID.
Response
Reading evaluation outcomes
For each span:- If
approvedOutputisnull, the span has not been reviewed yet. - If
approvedOutputequalsoutput, a reviewer accepted the original output as-is. - If
approvedOutputdiffers fromoutput, a reviewer corrected the output. The corrected version is the ground truth.
feedback[] entries are attached to specific spans via spanId, so you can join them in client code to build per-step review records.
Delete a trace
Path parameters
string
required
The trace UUID.
Response
404 Not Found if no trace with the given ID exists in the caller’s organization.