Scores

A score is a single evaluation attached to a trace or an observation. Everything that judges quality on the platform produces one: evaluators running automatically, people reviewing work by hand in Annotations, and your own code through the SDK. The Source column tells you which produced a given score.

Each score carries a name, a data type, and a value. The name comes from whatever produced it, so an evaluator's answer_quality and a reviewer's helpfulness sit side by side in the same table. The data type says how to read the value: a number, one of a fixed set of categories, or true and false.

This page is the only place the whole project's quality signal sits in one table, which makes it where you go to compare across evaluators and reviewers rather than to judge a single request.

Following a score

A score means little on its own, so most columns lead somewhere.

Opening the trace a score belongs to lands on that trace's Scores tab, with the value alongside the comment whoever produced it left behind.

Opening the user shows their whole history: their traces, sessions, and every score they have accumulated.