Hanzo
OpenapiMl

Change a deployed model in place

Applies a JSON merge patch to one of the caller org's deployed models and answers the updated resource — the way to change a model's image, replica count…

PATCH /v1/ml/models/{name}

Addresshttps://api.hanzo.ai/v1/ml/models/{name}
MethodPATCH
Operationpatch_ml_models_by_name
AuthAuthorization: Bearer $HANZO_API_KEY

Applies a JSON merge patch to one of the caller org's deployed models and answers the updated resource — the way to change a model's image, replica count or resource requests without tearing the deployment down.

The body is relayed to Kubernetes VERBATIM. That is deliberate and it is why this route is not a typed op: re-encoding a merge patch changes what it means, because an integer that round-trips through a generic decoder comes back a float. Merge-patch semantics apply as written — a null removes a field, and a list is replaced whole rather than merged.

Scoped to the caller's own tenant namespace, resolved from the validated org and project; a name the caller's tenant does not hold is a 404, never another tenant's resource. An empty body is refused, and a patch Kubernetes rejects comes back 422 with its reason rather than being silently dropped.

Request

1 field.

FieldInTypeRequiredDescription
namepathstringyes

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo ml models update <name>

ML API · All Hanzo APIs · Interactive reference

How is this guide?

On this page