List artifacts — GET /v1/train/jobs/{id}/artifacts

Answers a job's artifacts — checkpoint, capability, lora, basis or merged, each named by the SHA-256 of its bytes — with a download address that lives ten minutes for each one stored.

GET /v1/train/jobs/{id}/artifacts

Addresshttps://api.hanzo.ai/v1/train/jobs/{id}/artifacts
MethodGET
Operationget_train_jobs_by_id_artifacts
AuthAuthorization: Bearer $HANZO_API_KEY

Answers a job's artifacts — checkpoint, capability, lora, basis or merged, each named by the SHA-256 of its bytes — with a download address that lives ten minutes for each one stored. One deleted, by the org or by retention, reads deleted and has none.

Request

1 field.

FieldInTypeRequiredDescription
idpathstringyesID names the job.

Response

StatusBodyMeaning
200train.artifactsOutok
defaultproblem-detailsrefused

200 body — 11 fields.

FieldInTypeAlwaysDescription
databodytrain.Download[]—Data is the job's artifacts.
data[].createdbodyinteger (int64)—Created is when it was registered, unix seconds.
data[].expiresbodyinteger (int64)—Expires is when URL stops working, unix seconds.
data[].jobbodystring—Job is the job that produced it; empty for an upload.
data[].kindbodystring—Kind is checkpoint, lora, capability, basis or merged, or dataset for an upload.
data[].metabodyany—Meta describes it: its base and revision, its modules, a basis's address.
data[].namebodystring—Name labels it.
data[].sha256bodystring—SHA256 is the hex digest of its bytes, and its name in the object store.
data[].sizebodyinteger (int64)—Size is its byte count.
data[].statebodystring—State is pending until its bytes are read back, then stored; deleted once the org deleted it or it outlived its retention unpublished.
data[].urlbodystring—URL fetches the bytes until Expires; absent until the artifact is stored.

Failure carries the platform error shape — see Errors.

Examples

hanzo train jobs artifacts get <id>
import { Configuration, TrainApi } from 'hanzoai';

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

resp, _, err := client.TrainAPI.GetTrainJobsByIdArtifacts(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::get_train_jobs_by_id_artifacts(&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).getTrainJobsByIdArtifacts();
curl https://api.hanzo.ai/v1/train/jobs/<id>/artifacts \
  -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.