Changelog

Evaluation sets can now hold multifile items, so you can measure the accuracy of an extractor that runs over a package of files rather than a single document.

• fileIds on POST /evaluation_sets/{id}/items — pass an ordered array of 2–50 unique file IDs instead of fileId. Exactly one of fileId or fileIds must be provided per item. Multifile items are only supported on evaluation sets attached to a JSON-schema extractor.
• files on EvaluationSetItem and EvaluationSetItemSummary — an ordered array of file summaries, populated for multifile items and null otherwise.
• file is now nullable — null for multifile items, matching the file / files convention on ExtractRun.

When you run the set, each multifile item is evaluated as one multifile extraction run with a single expectedOutput covering the whole package. See Add a multifile item.