SpyBara
Go Premium

guides/trace-grading.md 2026-07-27 17:02 UTC to 2026-07-28 23:01 UTC

2 added, 0 removed.

2026
Thu 30 03:02 Wed 29 22:58 Tue 28 23:01 Mon 27 17:02 Sat 25 05:59 Fri 24 19:01 Thu 23 03:02 Wed 22 20:02 Tue 21 15:00 Mon 20 21:59 Sat 18 22:00 Fri 17 19:58 Thu 16 17:00 Wed 15 16:58 Tue 14 21:58 Mon 13 21:58 Sat 11 07:01 Fri 10 23:02 Thu 9 17:03 Wed 8 22:02 Mon 6 22:58 Sat 4 16:59

Trace grading

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to the page URL.

Trace grading is the process of assigning structured scores or labels to an agent's trace—the end-to-end log of decisions, tool calls, and reasoning steps—to assess correctness, quality, or adherence to expectations. These annotations help identify where the agent did well or made mistakes, enabling targeted improvements in orchestration or behavior.

Trace evals use those graded traces to systematically evaluate agent performance across many examples, helping to benchmark changes, identify regressions, or validate improvements. Unlike black-box evaluations, trace evals provide more data to better understand why an agent succeeds or fails.

Use both features to track, analyze, and optimize the performance of groups of agents.

Get started with traces

  1. In the dashboard, navigate to Logs > Traces.
  2. Select a workflow. You'll see traces from SDK-based apps, and from existing Agent Builder workflows during the transition window.
  3. Select a trace to inspect your workflow.
  4. Create a grader, and run it to grade your agents' performance against grader criteria.

Trace grading is a valuable tool for error identification at scale, which is critical for building resilience into your AI applications. Learn more about our recommended process in our cookbook.

Evaluate traces with runs

  1. Select Grade all. This takes you to the evaluation dashboard.
  2. In the evaluation dashboard, add and edit test criteria.
  3. Add a run to evaluate outputs. You can configure run options like model, date range, and tool calls to get more specificity in your eval.

Learn more about how you can use evals here.