Skip to main content
This page shows how you can sync an evaluation that was run on your machine using calibrate-agent to the app for you to see it in the UI and share it easily with others. We currently support syncing your speech-to-text evaluations and LLM benchmarking results. You need to use the right API for importing the evaluation results, depending on the type of evaluation.

Pre-requisites

Depending on the evaluation type, you need to prepare the app for import.
Make sure you add the audio files in the same order in which they were kept locally. Nothing in a calibrate run records which uploaded file a row came from, so a row is paired with the dataset item in the same position. Copy the dataset ID from the URL as it will be used later.
Create an agent on Calibrate if you haven’t already and upload the tests against it. Make sure to keep the same name for each test case on Calibrate as the test_case_id in the dataset used for the offline evaluation run. Any row that matches no test refuses the whole import.Create the LLM judges used for the run on Calibrate with the same name. Calibrate maps each score to the evaluator that produced it.

Prepare the output folder

Only three kinds of file are read: each result folder’s results.csv or results.json, its metrics.json, and the leaderboard.

Authentication

Both the endpoints use the JWT key of your signed-in account on Calibrate to authenticate your request. Open Calibrate in your browser, open the network tab, and copy the Authorization header from any request made to Calibrate’s backend API. It starts with Bearer. Send X-Org-UUID as well, which indicates the ID of the workspace where you want to import the evaluations. It is the first part of the Calibrate URL you are looking at, .../a9f1d0d4-1afa-4adc-b93b-e6a395208f0e/datasets/....

Run the import

Speech to text

LLM benchmark

What comes back

Speech to text

The evaluation it stored, the providers it found in the archive, and how many rows each of them carries.

LLM benchmark

The benchmark it stored, the models it found, and how many tests each was scored on. unresolved_evaluators lists evaluators the results score against that are no longer in the workspace. Their scores and reasoning are stored either way, they just render without a name or rubric.

When an import is refused

Nothing is stored when any of these is true, so it is safe to try.