Create evaluators

Saves a reusable judge for the caller's org — the judge model and the written criteria it grades against — and answers 201 with it.

POST /v1/eval/evaluators

Addresshttps://api.hanzo.ai/v1/eval/evaluators
MethodPOST
Operationpost_eval_evaluators
AuthAuthorization: Bearer $HANZO_API_KEY

Saves a reusable judge for the caller's org — the judge model and the written criteria it grades against — and answers 201 with it.

Like a dataset, the NAME is the key: re-posting a name edits that judge rather than adding a second one. Requires a validated principal; 401 without one.

Request

4 fields, body application/json (required).

FieldInTypeRequiredDescription
criteriabodystring—Criteria is the written standard the judge applies; over 64 KiB is refused.
modelbodystring—Model is the model that will do the grading.
namebodystringyesName is the judge's org-unique handle, matching ^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$.
scoreNamebodystring—ScoreName is the name the resulting scores are filed under.

Response

StatusBodyMeaning
201eval.evaluatorViewcreated
defaultproblem-detailsrefused

201 body — 6 fields.

FieldInTypeAlwaysDescription
createdAtbodystring—CreatedAt is when the judge was first defined.
criteriabodystring—Criteria is the written standard the judge applies.
modelbodystring—Model is the model that does the grading.
namebodystring—Name is the judge's org-unique handle.
scoreNamebodystring—ScoreName is the name the resulting scores are filed under.
updatedAtbodystring—UpdatedAt is when it last changed.

Failure carries the platform error shape — see Errors.

Examples

hanzo eval evaluators create --name <name>
import { Configuration, EvalApi } from 'hanzoai';

const api = new EvalApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postEvalEvaluators({ name: "<name>" });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import EvalApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = EvalApi(client).post_eval_evaluators(name="<name>")
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.EvalAPI.PostEvalEvaluators(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, eval_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = eval_api::post_eval_evaluators(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.EvalApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new EvalApi(client).postEvalEvaluators();
curl -X POST https://api.hanzo.ai/v1/eval/evaluators \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "name": "<name>"
     }'

MCP reaches eval through the eval tool, which names its 16 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_eval_datasets"
         }
       }
     }'

Eval API · All Hanzo APIs · Interactive reference

Was this page useful?