Create a Model Entity
Create a Model Entity that references your FileSet to enable customization jobs.
Prerequisites
- Created a FileSet containing your model checkpoint (refer to Create a Model FileSet).
- Set the
NMP_BASE_URLenvironment variable.
Create the Model Entity
Example Response
Note: spec is initially null and will be auto-populated by the Models Controller.
Wait for Model Spec Auto-Population
The platform’s Models Controller automatically analyzes your model files and populates the spec field with metadata like architecture, parameter count, and layer information. This is required before running customization jobs.
Example Model Spec
Verify the Model Entity
Before using in a customization job, verify everything is set up correctly:
Using the Model Entity in Customization Jobs
After your Model Entity is ready (has a populated spec), reference it in a customization job. Jobs are submitted to a backend (automodel shown here; unsloth is also available):
Refer to create-job for complete job creation details.
Post-Training Output
After a customization job completes, the output depends on the fine-tuning regime (training.finetuning_type):
- LoRA training (
finetuning_type: "lora"): An adapter is attached to this Model Entity. The adapter contains only the trained LoRA weights. - Full-weight training (
finetuning_type: "all_weights"): A new Model Entity is created containing the complete fine-tuned model weights. This new entity has abase_modelfield linking back to the original.
For LoRA jobs, you can list adapters attached to a model: