Skip to main content
A dataset’s questions and its grading config (acceptance criteria, similarity metrics, thresholds) are independent. EvaluationSettings is the grading config half on its own: build it once, then run it against any dataset by id, instead of every dataset carrying its own copy. Passing evaluation_settings_id is entirely optional. Omit it and a run grades against the dataset’s own bundled config, exactly as if this feature didn’t exist.

Programmatic builder

builder() parameters

publish() sends the config to AgentX and returns an EvaluationSettings object with .id, which you pass as evaluation_settings_id to client.evaluations.run().

Configuring the judge

judge_prompt/judge_model apply to every scoring path, native dashboard runs and SDK/custom-agent runs alike:
judge_prompt is a raw template: {input}, {output}, and {expected} are substituted in. Everything else the judge needs (chain of thought, capabilities/references, criteria, per-question judge_guideline, delegation notes) is appended automatically after it, so a custom prompt can restructure the grading philosophy without ever losing that context. Omit judge_prompt to keep the default rubric, or judge_model to keep the default (gpt-5.5).

Running against a dataset

The same evaluation_settings_id can be reused across as many dataset_ids as you want. Build it once, grade any dataset with it going forward.

Fetching an existing config

Next steps

Build Dataset

Create the test cases this config will grade

Quick Start

Run an evaluation end to end