Delete artifacts

Deletes one of the org's objects — an upload or a job's output — from the store: every artifact naming it then reads deleted, and its storage is no longer billed.

DELETE /v1/train/artifacts/{sha256}

Addresshttps://api.hanzo.ai/v1/train/artifacts/{sha256}
MethodDELETE
Operationdelete_train_artifacts_by_sha256
AuthAuthorization: Bearer $HANZO_API_KEY

Deletes one of the org's objects — an upload or a job's output — from the store: every artifact naming it then reads deleted, and its storage is no longer billed. A published object is 409 published, and one a job that has not ended reads or produced is 409 in_use. Another org's sha256 is not found, exactly as an unknown one is.

Request

1 field.

FieldInTypeRequiredDescription
sha256pathstringyesSHA256 names the object, from the path.

Response

StatusBodyMeaning
200train.deletedOutok
defaultproblem-detailsrefused

200 body — 2 fields.

FieldInTypeAlwaysDescription
deletedbodyboolean—Deleted is true.
sha256bodystring—SHA256 names the object deleted.

Failure carries the platform error shape — see Errors.

Examples

hanzo train artifacts rm <sha256>
import { Configuration, TrainApi } from 'hanzoai';

const api = new TrainApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteTrainArtifactsBySha256({ sha256: 'sha256' });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import TrainApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TrainApi(client).delete_train_artifacts_by_sha256(sha256='sha256')
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

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

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

let result = train_api::delete_train_artifacts_by_sha256(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.TrainApi;

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

var result = new TrainApi(client).deleteTrainArtifactsBySha256();
curl -X DELETE https://api.hanzo.ai/v1/train/artifacts/<sha256> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches train through the train tool, which names its 35 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_train_artifacts"
         }
       }
     }'

Train API · All Hanzo APIs · Interactive reference

Was this page useful?
Broken link or missing step? Drop it in #docs on Discord or open a PR.