Is the score shapes your org has declared — each name's data type, its numeric…
Is the score shapes your org has declared — each name's data type, its numeric bounds and its allowed categories.
GET /v1/eval/rubrics
| Address | https://api.hanzo.ai/v1/eval/rubrics |
| Method | GET |
| Operation | get_eval_rubrics |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Is the score shapes your org has declared — each name's data type, its numeric bounds and its allowed categories.
Requires a validated principal; 403 without one, and the listing is filtered on the validated org.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
limit | query | integer | — | Limit caps the rows returned. It defaults to 100 and is capped at 500; a non-positive or unparseable value falls back to the default rather than failing,… |
Response
| Status | Body | Meaning |
|---|---|---|
200 | scoreConfigList | ok |
200 body — 8 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | scoreConfigView[] | — | Data is the caller org's rubrics, bounded by limit. |
data[].categories | body | string[] | — | Categories is the closed set of labels a CATEGORICAL score may carry. |
data[].createdAt | body | string | — | CreatedAt is when the rubric was first declared. |
data[].dataType | body | string | — | DataType is NUMERIC, CATEGORICAL or BOOLEAN, and is authoritative — a score recorded under this name cannot claim a different one. |
data[].maxValue | body | number | — | MaxValue is the inclusive ceiling a NUMERIC score must stay under, absent when unbounded. |
data[].minValue | body | number | — | MinValue is the inclusive floor a NUMERIC score must clear, absent when unbounded. |
data[].name | body | string | — | Name is the score name this rubric governs. |
data[].updatedAt | body | string | — | UpdatedAt is when it last changed. |
Failure carries the platform error shape — see Errors.
Examples
hanzo evals rubrics getimport { Configuration, EvalApi } from 'hanzoai';
const api = new EvalApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getEvalRubrics();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).get_eval_rubrics()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.EvalAPI.GetEvalRubrics(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::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::get_eval_rubrics(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.EvalApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new EvalApi(client).getEvalRubrics();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/eval/rubrics \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches eval through the evals tool, which names its 16 operations with its own verbs — this one among them, under a name only the door 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"
}
}
}'How is this guide?