Current model
Legacy model IDs
Older integrations may still send previous model IDs. These IDs remain accepted for backwards compatibility, but new integrations should usekugel-3.
Legacy requests may route through the current production model, but billing and Dashboard usage keep the requested
model_id visible for auditability. Use kugel-3 in new integrations for the clearest reporting.Example
- Python
- JavaScript
- cURL
Capabilities
Listing models
GET /v1/models returns canonical current models only. Legacy IDs are accepted for backwards compatibility, but they are not included in this endpoint response.
- Python
- JavaScript
- cURL