Hanzo AIDocs
Sign inAPI key

Delete datasets

Removes the named dataset of the caller's org AND all of its examples, in one transaction.

DELETE /v1/eval/datasets/{name}

Eval → · All API references → · Get started →

Addresshttps://api.hanzo.ai/v1/eval/datasets/{name}
MethodDELETE
Operationdelete_eval_datasets_by_name
AuthAuthorization: Bearer $HANZO_API_KEY

Removes the named dataset of the caller's org AND all of its examples, in one transaction.

This is not a detach: the examples are gone with the set, so a dataset cannot be resurrected by re-creating the name. A name this org does not have is 404 — never a silent success — and a name belonging to another tenant is the same 404, because the delete is predicated on the validated org. Requires a validated principal; 401 without one. Runs and scores already recorded against the dataset are telemetry events and are NOT deleted with it.

Request

1 field.

FieldInTypeRequiredDescription
namepathstringyesName is the dataset the URL names.

Response

StatusBodyMeaning
204—no content
defaultproblem-detailsrefused

Failure carries the platform error shape — see Errors.

Examples

hanzo eval datasets rm <name>
import { Configuration, EvalApi } from 'hanzoai';

const api = new EvalApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteEvalDatasetsByName({ 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).delete_eval_datasets_by_name(name='name')
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.EvalAPI.DeleteEvalDatasetsByName(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::delete_eval_datasets_by_name(&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).deleteEvalDatasetsByName();
curl -X DELETE https://api.hanzo.ai/v1/eval/datasets/<name> \
  -H "Authorization: Bearer $HANZO_API_KEY"

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?
PreviousReject signNextList items