Sign in

v1

latestOpenAPI 3.0.32026-07-172892106.1 KB
fine-tuning

Create Fine Tuning Job

Create a new fine-tuning job, it will be queued for processing.

post/fine_tuning/jobs

Query parameters

dry_runboolean nullable
  • If true the job is not spawned, instead the query returns a handful of useful metadata for the user to perform sanity checks (see LegacyJobMetadataOut response).
  • Otherwise, the job is started and the query returns the job ID along with some of the input parameters (see JobOut response).

Request body

model'open-mistral-7b' | 'mistral-small-latest' | 'codestral-latest' | 'mistral-large-latest' | 'open-mistral-nemo' | 'ministral-3b-latest' required

The name of the model to fine-tune.

suffixstring nullable

A string that will be added to your fine-tuning model name. For example, a suffix of "my-great-model" would produce a model name like ft:open-mistral-7b:my-great-model:xxx...

validation_filesstring[] nullable

A list containing the IDs of uploaded files that contain validation data. If you provide these files, the data is used to generate validation metrics periodically during fine-tuning. These metrics can be viewed in checkpoints when getting the status of a running fine-tuning job. The same data should not be present in both train and validation files.

auto_startboolean

This field will be required in a future release.

Response

OK

OR

Example response

{
  "cost_currency": "[\"EUR\"]"
}