Completed your first bake? Your trained model is ready to use.
Model Path Format
Baked models are referenced using this path format:username- Your Bread username or team namerepo_name- The repository containing the bakebake_name- The specific bake configurationcheckpoint_number- Training checkpoint (usually final checkpoint)
Find your checkpoint number in the bake output or training logs. The final checkpoint represents the fully trained model.
Using Baked Models for Inference
API-Based Inference
Use your baked model through the Bread API with OpenAI-compatible endpoints:Key requirements:
BREAD_API_KEYenvironment variable must be set- Update
MODEL_NAMEto your baked model path:username/repo/bake/checkpoint - Base URL:
https://bapi.bread.com.ai/v1/chat/completions
Streaming Responses
Enable streaming for real-time response generation:Monitoring Training Metrics
You can retrieve detailed training logs for your bakes to analyze loss curves, learning rate schedules, and overall training performance.Get Metrics
Use the SDK to fetch training metrics:Downloading Model Weights
After your bake completes, you can download the model weights for local use or deployment. The API provides presigned URLs for secure, time-limited access to your model checkpoints.Get Download URL
Use the SDK to get a presigned download URL for your baked model:Download Specific Checkpoint
To download a specific checkpoint instead of the latest:Custom URL Expiry
Control how long the presigned URL remains valid (default: 1 hour, max: 7 days):Important Notes:
- Presigned URLs expire after the specified time (default: 1 hour)
- URLs provide direct access to model weights
- Download the weights promptly after receiving the URL
- Model weights are typically large files (several GB), ensure sufficient storage space
Configuration Requirements
Essential Settings
To use your baked model, you need three things:Your API Key
Our Base URL
Your Model Path
Common Issues
Model not found
Problem: Model path is incorrect or checkpoint doesn’t exist. Solution:Model doesn’t exhibit baked behavior
Problem: Student prompt wasn’t empty or bake didn’t complete. Solution:Best Practices
Test Before Production
Test Before Production
Always test your baked model thoroughly before deploying to production. Verify it exhibits the expected behavior consistently.
Version Your Models
Version Your Models
Use clear naming:
model_v1, model_v2, etc. Track which version is deployed where.Monitor Behavior
Monitor Behavior
Log model outputs in production to ensure baked behavior remains consistent over time.
Keep Training Data
Keep Training Data
Save stim and rollout outputs. Useful for debugging and iterative improvements.
Document Your Prompts
Document Your Prompts
Keep records of teacher/student prompts used for each model version. Essential for reproducibility.