List Checkpoints
Parameters
str
required
The ID of the fine-tuning job to list checkpoints for.
str
A cursor for pagination. Identifier for the last checkpoint ID from the previous pagination request.
int
Number of checkpoints to retrieve per page.
Response
Returns a paginated list ofFineTuningJobCheckpoint objects:
Examples
List All Checkpoints for a Job
Find Best Checkpoint by Validation Loss
Plot Training Progress
Monitor Checkpoint Metrics
Paginate Through Checkpoints
Auto-pagination
Export Checkpoint Data to CSV
Use Specific Checkpoint for Inference
Async Usage
Understanding Checkpoint Metrics
Training Metrics
- train_loss: Loss computed on the training batch
- train_mean_token_accuracy: Token-level accuracy on training data
Validation Metrics
- valid_loss: Loss on validation set (if provided)
- valid_mean_token_accuracy: Token-level accuracy on validation set
- full_valid_loss: Loss computed on the full validation set
- full_valid_mean_token_accuracy: Accuracy on the full validation set
Checkpoint Selection
- Lower validation loss generally indicates better generalization
- Monitor for overfitting: training loss decreasing while validation loss increases
- Each checkpoint is a fully usable model that can be deployed
Notes
- Checkpoints are created periodically during fine-tuning
- Each checkpoint is a snapshot of the model at a specific training step
- Checkpoint models can be used immediately for inference
- Not all fine-tuning jobs produce checkpoints (depends on training duration)
- Checkpoints are useful for:
- Monitoring training progress
- Selecting the best model based on validation metrics
- Recovering from overfitting by using an earlier checkpoint
- A/B testing different training stages
- Use the checkpoint with the lowest validation loss for best results
- Checkpoints consume storage but provide valuable model versioning