Skip to main content
Experimental. Fine-tuning’s operations, fields, and limits can change between releases.
Use this page to look up values you send to or read from the fine-tuning operations. For how a run works, see Fine-tuning.

Models and dataset

Settings

Every setting is optional on create and is validated against its bound. Omit a setting to take its default: an explicit null for name, settings, or a setting, an unknown setting, or a value of the wrong type returns 400 invalid_request. A job reports the settings it runs with in settings. A step or a held-out check that loses more than half of its rollouts is a bad round; three bad rounds in a row (one for a baseline) fail the attempt.

Job status and phase

progress.lastEventAt is the last time the job reported anything, heartbeats included. progress.rollouts counts the current step’s rollouts by status. progress.ingestErrors counts progress updates from the run that could not be read and were skipped.

Timeline events

listFineTuningJobEvents returns the timeline in order, filtered by type. Each event has seq, occurredAt, and type; the other fields apply by type and are null otherwise.

Rollouts and groups

A group is the rollouts of one task in one step. listFineTuningJobRolloutGroups needs split and step, and filters by spread, status, and task name q, sorted by sortBy (group, task, meanReward, stdReward) and sortDirection. spread is flat when every scored rollout got the same reward, so the group teaches nothing, and mixed otherwise. It is null while any rollout of the group is queued or running, or when none is scored, so spread=flat on a running step returns fewer groups than you might expect. For listFineTuningJobRollouts, step needs split, status needs split and step, and updatedAtGte takes no other filter.

Metrics

Metric names are exactly as reported. train/ metrics come from a step’s rollouts, eval/ from a held-out check. A run can report further metrics; read any of them with the name parameter.

Checkpoints

listFineTuningJobCheckpoints returns the checkpoints by step, and a job reports its latest as latestCheckpoint.

Cost states

billedCostUsd is a usage estimate for the run, not a bill. The live estimate while a run works is the cost/total_usd metric.

Paging, following, and idempotency

Pass nextCursor back as cursor with the same filters and limit until it is null. A cursor expires after one hour, and a rollout-groups walk through a step that is still running can skip or repeat groups; it is complete only once the step has no queued or running rollouts. total is always null except for rollout groups. createFineTuningJob requires Idempotency-Key. Renaming is safe to repeat. cancelFineTuningJob accepts an optional Idempotency-Key; send one so a retry that lands after a resume cannot cancel the resumed run. resumeFineTuningJob is not safe to retry blindly: a retry after the resumed run settles starts another attempt, which adds training cost, so read the job first.

Errors

A failed job’s failure.reason is one line, such as The training run reached its 24-hour limit., The training compute stopped., or the run’s own error. See Troubleshooting.