Import and Export
Scorable evaluators are portable. You can export any evaluator as a YAML file, commit it to your own git repository, and import it back at any time in any organization, on any Scorable account, or without Scorable at all.
The YAML format
Every evaluator serializes to a single human-readable YAML file:
name: Response Quality
objective:
intent: "Checks whether the response directly and completely answers the user's question."
scoring_criteria: |-
You are evaluating whether the response answers the question directly and completely.
Score from 0 to 1:
1.0 — Fully answers the question, nothing missing.
0.5 — Partially answers the question.
0.0 — Does not address the question.
Response: {{ response }}
Question: {{ request }}
model: gpt-5.2
demonstrations:
- request: "What is the capital of France?"
response: "Paris."
score: 1.0
justification: "Direct and correct."
- request: "What is the capital of France?"
response: "I'm not sure, maybe Lyon?"
score: 0.0
justification: "Incorrect answer."name
Yes
Evaluator name
objective.intent
Yes
One-line description of what the evaluator measures
scoring_criteria
Yes
The scoring prompt; use {{ response }} and {{ request }} as placeholders
model
No
LLM to use for scoring (defaults to Scorable's recommended model)
demonstrations
No
Few-shot examples that guide the LLM on how to assign scores
calibration
No
Test cases used to validate the evaluator's scoring consistency
Both demonstrations and calibration are lists of objects with the same shape:
response
Yes
The LLM output being evaluated
score
Yes
Expected score in [0, 1]
request
No
The input that was evaluated (omit if the evaluator does not use {{ request }})
justification
No
Explanation for the assigned score
The format is stable. Files produced today will import correctly in future versions of Scorable.
Export an evaluator
Web UI
Open an evaluator → action menu (⋮) → Download YAML.
CLI
Import an evaluator
Web UI (from GitHub)
Open the Evaluators page.
Click GitHub in the top bar.
Install the Scorable GitHub App on your account or organization (one-time). You choose which repositories to grant access to.
Enter the owner and repository name, then click Load repository.
Evaluators found in the
.scorable/evaluators/directory are listed — click Import next to any of them.
CLI
Store evaluators in git
The convention is to keep evaluator YAML files under .scorable/evaluators/ in your git repository:
Export all evaluators and commit:
Restore from git in a new environment:
API reference
Export — GET /v1/evaluators/export/{id}/
Returns the evaluator as a text/yaml file download.
Authentication: API key required (Authorization: Api-Key <key>)
Direct YAML import — POST /v1/evaluators/import-yaml/
Import an evaluator from a YAML string. Handles demonstrations and calibration dataset creation in one request.
Authentication: API key required (Authorization: Api-Key <key>)
Request body:
Response: The created evaluator object (201).
Open format
Scorable evaluators are fully defined by their YAML: a name, an intent, and a scoring prompt. You can:
Keep the YAML in your own version-controlled repository.
Recreate any evaluator from the YAML without a Scorable account.
Run the prompt directly against any LLM if you want to bypass Scorable entirely.
The YAML format is open, documented here, and will not change in a breaking way.
Schema and editor support
A machine-readable JSON Schema is published at https://api.scorable.ai/schema/evaluator.json.
Add the following comment to any evaluator YAML to enable autocomplete and validation in VS Code (with the YAML extension) and most other editors:
Or configure your whole workspace once in .vscode/settings.json:
Last updated