Start model training
submit_training_jobStarts a model training job for a model version, using one training credit and returning a job ID to track completion.
Instructions
Submit a training job for a model version.
Each call starts a separate training job and spends one training credit;
get_training_status follows a job already submitted, by its job_id.
Track completion: Poll list_model_versions for the model and watch the target
version's status until it reaches TRAINING_COMPLETED or TRAINING_FAILED (same as the
web UI). This is the most reliable approach across MCP hosts.
Or pass the returned jobId to get_training_status with wait=true to block
until the job finishes. Run time depends on the plan and the data, from minutes
to several hours.
dataset_version_id can be omitted when the model version was created with
create_model_version in the same flow — the backend resolves target_feature,
file, and dataset from the model version record automatically. Omit it to train
on the model version's own dataset. Pass it only to override with a different
qa_cleaned or training version: an explicit dataset_version_id whose
version_type is raw (every upload starts as raw) is rejected with
400 INVALID_VERSION_TYPE.
Returns {jobId, modelVersionId, status}.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| model_version_id | Yes | ||
| dataset_version_id | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||