Is your past runs and how they scored — the dataset and model, the judge model,…
Is your past runs and how they scored — the dataset and model, the judge model, how many examples were attempted and how many scored, the average score,…
GET /v1/eval/runs
| Address | https://api.hanzo.ai/v1/eval/runs |
| Method | GET |
| Operation | get_eval_runs |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Is your past runs and how they scored — the dataset and model, the judge model, how many examples were attempted and how many scored, the average score, and when it happened.
Requires a validated principal; 403 without one, and rows are filtered on the validated org. These records come from the metastore rather than the datastore, so they are readable on a deployment with no telemetry wired — but a run's traces and scores are not.
Request
2 fields.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
datasetName | query | string | — | Dataset narrows to the runs against one dataset. |
limit | query | integer | — |
Response
| Status | Body | Meaning |
|---|---|---|
200 | runs | ok |
200 body — 10 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | runRecord[] | — | Data is the caller org's runs, bounded by limit. |
data[].avgScore | body | number | — | AvgScore is the mean over the scored examples. |
data[].createdAt | body | string | — | CreatedAt is when the run first landed. |
data[].dataset | body | string | — | Dataset is the set that was scored. |
data[].items | body | integer | — | Items is how many examples were attempted. |
data[].judgeModel | body | string | — | JudgeModel is the model that graded. |
data[].model | body | string | — | Model is the model under test. |
data[].runName | body | string | — | RunName is the run's label. |
data[].scored | body | integer | — | Scored is how many produced a real score. |
data[].updatedAt | body | string | — | UpdatedAt is when the record last changed. |
Failure carries the platform error shape — see Errors.
Examples
hanzo evals runs getimport { Configuration, EvalApi } from 'hanzoai';
const api = new EvalApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getEvalRuns();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_runs()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.EvalAPI.GetEvalRuns(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_runs(&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).getEvalRuns();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/runs \
-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?