Is the examples in one of your datasets — the set is named in the path, because…

Is the examples in one of your datasets — the set is named in the path, because this collection only exists inside one.

GET /v1/eval/datasets/{name}/items

Eval → · All API references → · Six flows, four surfaces →


Address	`https://api.hanzo.ai/v1/eval/datasets/{name}/items`
Method	`GET`
Operation	`get_eval_datasets_by_name_items`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Is the examples in one of your datasets — the set is named in the path, because this collection only exists inside one.

Archived examples are included, so the caller sees the whole set rather than only what a run would use. Requires a validated principal; 403 without one, and the read is filtered on the validated org, so naming another tenant's dataset returns nothing rather than its contents.

Request

2 fields.

Field	In	Type	Required	Description
`name`	path	string	yes	Dataset is the set to read, from the path — this collection only exists inside one.
`limit`	query	integer	—

Response

Status	Body	Meaning
`200`	itemList	ok

200 body — 10 fields.

Field	In	Type	Always	Description
`data`	body	itemView[]	—	Data is the examples of the one dataset named in the path, archived ones included, so the caller sees the whole set rather than what a run would use.
`data[].createdAt`	body	string	—	CreatedAt is when the example was first written.
`data[].datasetName`	body	string	—	Dataset is the set this example belongs to.
`data[].expectedOutput`	body	object	—	Expected is the answer a correct model produces, which the judge grades against.
`data[].id`	body	string	—	ID is the example's handle, unique within the caller's org.
`data[].input`	body	object	—	Input is what the model under test is given, as it was written.
`data[].metadata`	body	object	—	Metadata is the free-form object stored with the example.
`data[].metadata.*`	body	object	—
`data[].status`	body	string	—	Status is ACTIVE or ARCHIVED.
`data[].updatedAt`	body	string	—	UpdatedAt is when it last changed.

Failure carries the platform error shape — see Errors.

Examples

hanzo evals datasets items get <name>

import { Configuration, EvalApi } from 'hanzoai';

const api = new EvalApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getEvalDatasetsByNameItems({ 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).get_eval_datasets_by_name_items(name='name')

cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)

resp, _, err := client.EvalAPI.GetEvalDatasetsByNameItems(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_datasets_by_name_items(&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).getEvalDatasetsByNameItems();

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/datasets/<name>/items \
  -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"
         }
       }
     }'

Eval API · All Hanzo APIs · Interactive reference

Is the examples in one of your datasets — the set is named in the path, because…

Request

Response

Examples

On this page