SpyBara
Go Premium

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

10 added, 32 removed.

2026
Wed 29 19:02 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

Evaluate agent workflows

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

The OpenAI Platform offers a suite of evaluation tools to help you ensure your agents perform consistently and accurately.

Use this page as the decision point for the evaluation surfaces that matter most for agent workflows.

Start with traces when you are still debugging behavior

Trace grading is the fastest way to identify workflow-level issues. A trace captures the end-to-end record of model calls, tool calls, guardrails, and handoffs for one run. Graders let you score those traces with structured criteria so you can find regressions and failure modes at scale.

Use trace grading when you want to answer questions like:

  • Did the agent pick the right tool?
  • Did a handoff happen when it should have?
  • Did the workflow violate an instruction or safety policy?
  • Did a prompt or routing change improve the end-to-end behavior?

Trace-grading workflow

  1. Open Logs > Traces in the dashboard.
  2. Inspect a representative workflow trace from an SDK-based app, or from an existing Agent Builder workflow during the transition window.
  3. Create a grader and run it against the selected traces.
  4. Use the results to refine prompts, tool surfaces, routing logic, or guardrails.

For code-first SDK workflows, start with Integrations and observability to get high-signal traces before you formalize graders.

Move to datasets and eval runs when you need repeatability

Once you know what “good” looks like, move from individual traces to repeatable datasets and eval runs. This is the right step when you want to benchmark changes, compare prompts, or run larger-scale evaluations over time.

If you need advanced features such as evaluation against external models, evaluation APIs, or larger-scale batch evaluation, use Evals alongside datasets.

[Getting started with evals: Datasets

  Operate a flywheel of continuous improvement using evaluations.](https://developers.openai.com/api/docs/guides/evaluation-getting-started)

[Working with evals

  Evaluate against external models, interact with evals via API, and more.](https://developers.openai.com/api/docs/guides/evals)

[Prompt optimizer

  Use your dataset to automatically improve your prompts.](https://developers.openai.com/api/docs/guides/prompt-optimizer)

[Cookbook: Building resilient prompts with evals

  Operate a flywheel of continuous improvement using evaluations.](https://developers.openai.com/cookbook/examples/evaluation/building_resilient_prompts_using_an_evaluation_flywheel)