merged artifact path, which is required before exporting to deployment formats like GGUF, MLX, MNN, or QNN.
Method + Path
Authentication
Include your PIN API token or JWT in theAuthorization header as a Bearer token.
Path parameters
string
required
The model identifier (e.g.,
md_abc123def456).Request body
No request body is required.Request example
Response
Returns a standard PIN success envelope with the merge status.integer
required
0 on success, nonzero on error.object
required
string
Human-readable message (empty on success).
Example response
Merge process
- The system validates that the model exists and is not already merging.
- It generates a temporary Python script using PEFT’s
merge_and_unloadto fuse the adapter into the base weights. - The merged weights are saved to the model’s
mergedartifact directory. - On success, the model status returns to
readyandartifact_paths.mergedis updated.
Errors
Notes
- If you call
POST /v1/models/:id/exportbefore merging, the export service automatically triggers a merge first. - For models trained with full-parameter methods (
pretrain,qat,distillwithmode=full), no merge is needed because the output is already full weights.