Legacy music model for basic song drafts and application prototypes
chirp-v3-0 is a legacy creation option in the Suno music series, suitable for turning theme descriptions or existing lyrics into listenable song drafts, and can also be used for instrumental music concepts. Its value lies in basic creation and compatibility with existing projects, rather than complex editing controls. Through this platform, you can submit music tasks and obtain audio URLs, song status, and related metadata.
Clarify capacity, inputs and outputs, and invocation methods before selecting a model.
Model positioning
Chirp v3.0/V3, legacy basic music generation
Inspiration creation
custom=false, use prompt to describe the theme and musical direction
Prompt range
Platform inspiration mode: up to 500 characters
Custom creation
custom=true, submit lyric, title, and style
Music format
Vocal songs; inspiration mode can set instrumental to request instrumental music
Audio delivery
The input audio format option is MP3, and the JSON result includes audio_url and song metadata
Invocation method
POST /suno/audios; model=chirp-v3-0; supports asynchronous tasks and callbacks
The above creation parameters and delivery methods are within this platform's invocation scope and do not indicate that this model has all the native editing capabilities of newer versions.
Core Capabilities
Learn what chirp-v3-0 can bring to your work.
Create music drafts from themes
When you do not have lyrics ready, use inspiration mode to describe the song's theme, mood, and genre, such as a warm birthday song or relaxed travel soundtrack. It is suitable for turning text concepts into listenable material first, then deciding whether the musical direction is appropriate, reducing the burden of preparing complete lyrics at the beginning of the creative process.
Organize song creation with existing lyrics
When lyrics are already available, switch to custom mode and submit the lyrics, title, and style separately. Lyrics can be organized into sections such as verses and choruses, while the style expresses the desired musical direction. This workflow is suitable for turning copy drafts into song samples, rather than arranging note by note or precisely controlling the singing.
Integrate creative results into applications
Generated results are delivered as song lists and metadata. Applications can use song IDs, titles, lyrics, statuses, and audio URLs to build listening pages. Asynchronous mode returns task IDs, making it easy to handle submission and result display separately; completed results can also be received through callbacks, without requiring the user interface to wait continuously.
Use Cases
Start with specific tasks to find where the model can be effective.
Music application prototypes
Build a basic flow for a song-generation application: users enter a theme, the application submits a chirp-v3-0 task, then displays the status and playable audio. The delivery goal is to validate whether theme input, task tracking, and the listening experience work smoothly, making it suitable for prototypes that do not yet involve singer identity reuse or detailed track editing.
Theme song samples
Use holiday greetings, event themes, or story lyrics as input, and combine them with the desired genre to generate song samples. Teams can listen and discuss how the lyrics and music fit together, then decide whether to revise the text or change the creative direction. The deliverable here is audio for discussion, rather than a final product that requires no review.
Background music direction exploration
Set the instrumental option in inspiration mode, and describe the visual mood and musical style to explore soundtrack directions for videos or presentation content. First listen to whether candidate material matches the atmosphere of the content, then edit and adapt it; if the task requires strict timing, arrange timing in the subsequent audio production stage.
How to choose this model
Choose based on task complexity, input materials, and expected results.
Consider it first when you have an existing legacy project
If your existing application already uses chirp-v3-0, or the task only requires a basic song draft, it is the choice for continuing the existing invocation approach. chirp-v3-5 is another version and should not be treated directly as the same endpoint. When comparing the two, it is recommended to audition them using the same theme and lyrics, and choose based on the actual finished product rather than assuming fixed differences in quality or speed.
Choose a relevant newer version when finer control is needed
If requirements include a clear preference for male or female vocals, consider chirp-v4-5 and later models that support this control; chirp-v3-0 is not suitable for tasks that rely on vocal_gender. For complex song editing, you should also choose based on the specific capabilities of the selected version; do not apply the controls and editing methods of newer versions to older versions simply because they share a music interface.
Get started
From a small-scale task to formal integration.
01
Prepare the task and materials
Define the goal, required inputs, and output requirements, using real business examples as a starting point.
02
Try it in the API testing area
Open the trial page, confirm the parameters supported by this endpoint, then submit a small-scale task to review the results.
03
Integrate according to the API documentation
Keep the complete model ID, use the request format specified in the documentation, and confirm billing rules on the Pricing page.
Usage limits
Before formal use, understand the output quality and scope of capabilities.
chirp-v3-0 is intended for basic generation and is not suitable for use as a complete music editing tool. Workflows such as Persona, clip replacement, and multitrack separation each require separate assessment of suitability; do not expect the older version to complete every operation simply because relevant options exist in the request.
Style descriptions and lyric sections are used to guide creation and do not constitute a precise singing schedule. When fixed shot timing, word-by-word alignment, or strict final length is required, audition the generated audio and perform post-production; the actual duration is determined by the duration in the completed result.
The audio, images, and videos in the results are different asset fields. The presence of a field does not mean that a usable file will be generated for each item. Applications should check success, the song state, and the actual audio_url, save the required audio after completion, and avoid displaying unfinished tasks directly as playable finished products.
Frequently Asked Questions
Answers to common questions about using chirp-v3-0.
Are chirp-v3-0 and chirp-v3-5 the same model?
No. chirp-v3-0 corresponds to the older V3 creation option, while chirp-v3-5 is a different version. When calling them, specify the exact model value separately. Existing projects can continue organizing workflows around the original model; to switch versions, it is recommended to compare actual listening results using the same theme and lyrics.
Can I use chirp-v3-0 without lyrics?
Yes. You can use inspiration mode, set custom to false, and describe the theme, mood, and musical direction in the prompt. In this mode, the platform accepts up to 500 characters. If you already have lyrics that need to be used, switch to custom mode and submit the lyrics, title, and style separately.
Can chirp-v3-0 generate instrumental music?
You can request instrumental music in inspiration mode through instrumental, and use the prompt to specify the desired genre and mood. This approach is suitable for exploring background music directions; after generation, you still need to listen and confirm whether the audio content fits the intended use before editing and adapting the duration.
Can I use vocal_gender to specify a male or female voice?
Do not rely on this parameter to control chirp-v3-0. vocal_gender is valid for models version 4.5 and above, and it is a preference control rather than a strict guarantee. If male or female voice preference is an important requirement of the task, choose a relevant model that supports this control.
How do I obtain chirp-v3-0 audio after submission?
Submit a generation request to /suno/audios and specify model. When async=true is set, you can first obtain task_id and then track the task, or set callback_url to receive the result. After completion, obtain the audio from audio_url in data, and also check the song status; do not judge generation success based on the task ID alone.
Model information · Updated: 2026-10-01. For call parameters and billing rules, see the API and pricing sections.