Evaluation Overview
Evaluation sets let you test the accuracy of your document processors reliably and repeatedly. An evaluation set is attached to a processor and holds items: files paired with the output you expect. An evaluation set run scores one processor version against those items and returns accuracy metrics, so you can verify that a configuration change improved results before you publish it. Evaluation sets can also be run against a workflow to score its end-to-end output; the pages below focus on processors.
Evaluation is fully available through the API and in Extend Studio:
Create a set, upload files, and add items with expected outputs, in Python, TypeScript, Java, Go, or Studio.
Start a run, poll it to completion, and read accuracy metrics.
The evaluation loop
- Create an evaluation set containing examples that represent the range of documents your processor needs to handle. Aim for coverage of layouts, vendors, and edge cases rather than volume.
- Run it against the processor version you are working on (the draft, or a published version).
- Review the results to confirm outputs match expectations and to find common errors. Per-field accuracy tells you which parts of a schema need work.
- Iterate on the processor configuration (field descriptions, rules, base processor) and rerun. Compare runs to confirm the change helped. Composer automates this step using your evaluation sets.
- Publish the improved version once the set passes your bar, and pin it in your workflows.
In Extend Studio
The Evaluation page in the Studio section lists your evaluation sets with options to create new sets and start runs.

Reference
- Evaluation endpoints: sets, items, and runs
- Processors: the saved, versioned entity a set is attached to
- Calculating Array Accuracy: how tables and lists are scored

