Models, Defaults, and Compatibility
Choose an explicit model when its capabilities or cost matter to your application. An accepted historical name is a compatibility alias, not a guarantee that the historical model still executes. Store the requested model and the model returned with the result; avoid deriving either from a display title.
Producer compose
Section titled “Producer compose”| Request value | Current selection | Length hint |
|---|---|---|
| Omitted | Lyria 3.5 | 60–180 seconds |
Lyria 3.5 | Lyria 3.5 | 60–180 seconds |
Lyria 3 Pro | Lyria 3 Pro | 1–180 seconds |
Lyria 3 preview | Deprecated alias for Lyria 3.5 | 60–180 seconds |
Both current models accept a BPM hint of 1–999. A hint does not promise exact
output timing. New integrations should use current names and omit the ignored
advancedMode field. See Producer.
Suno generation
Section titled “Suno generation”| Request value | Executes as | Standard song/derive price |
|---|---|---|
chirp-hawk | v6 Pro | 28 credits |
chirp-hawk-wild | v6-wild Pro | 28 credits |
chirp-goose | v6-mini | 25 credits |
| Omitted in the modern API | chirp-hawk, retaining the chirp-fenix pricing identity | 28 credits |
chirp-auk-turbo | chirp-goose | Requested-model pricing is preserved |
chirp-v4, chirp-auk, chirp-bluejay, chirp-crow, chirp-fenix | chirp-hawk | Requested-model pricing is preserved |
Documented underscore spellings are also accepted compatibility aliases.
suno/chirp-v3-5 is retired for new requests. Customer pricing can change the
standard charge; read the catalog and the task receipt.
The Legacy API has a separate default: ordinary generation selects chirp-goose.
Do not carry that default into a modern upload-extend/upload-cover integration.
See the Legacy migration guide for use_requested_model behavior.
Plan an upgrade
Section titled “Plan an upgrade”- Compare the new model’s accepted input ranges and capabilities, not just its name.
- Set the intended model explicitly and preview costs where quotes are supported.
- Keep already-submitted jobs on their original route, body, and idempotency key.
- Validate completed resources and final billing before moving new work.
This page describes the contract in this documentation version. The Changelog records customer-visible updates; account- or availability-dependent features should be enabled from their live availability response. Older change entries do not override the current product guide.