https://gateway.omnia-voice.com/v1 with your workspace API key. Launching a job
is an admin-gated action.
1. Upload a training file
Fine-tuning takes a training file (JSONL). Upload it withPOST /v1/fine_tuning/files:
trainingFileId. You
can also prepare data as a managed dataset; see
Datasets & formats.
2. Create the job
Create a job withPOST /v1/fine_tuning/jobs. Only baseModel is required; you
supply training data as a trainingFileId (or inline training).
GET /v1/fine_tuning/jobs/{id} to follow its status
(queued → running → succeeded/failed/cancelled), events, and, once
finished, its trained_tokens and the resulting model.
Fields
Supervised hyperparameters
All supervised hyperparameters are optional with sensible defaults; you only set what you want to override.Training schedule
Training schedule
Sequence handling
Sequence handling
LoRA
LoRA
3. Track the job
List jobs withGET /v1/fine_tuning/jobs, and poll a single job with
GET /v1/fine_tuning/jobs/{id} to watch its status and events:
queued → running → succeeded (or failed /
cancelled). Events and checkpoints are available while the job runs. Cancel
or delete a job with DELETE /v1/fine_tuning/jobs/{id}.
Billing happens once, on completion, from the trained-token count. Because
trained_tokens isn’t known until the run finishes, the create-time gate uses an
estimated-token budget: a workspace can’t launch training it can’t pay for. A
job that fails or is cancelled is not billed.Next
Deploy the model
Once the job succeeds, deploy it to a dedicated endpoint.