Suno V3 is an earlier-generation song creation model. Its official release highlights include audio quality, genre range, prompt adherence, and more natural endings. This platform invokes it as chirp-v3-0, making it suitable for turning brief themes into song concept drafts or continuing projects that already use this version. Creation and delivery follow the corresponding entry points on this platform and do not automatically include later-version editing workflows.
Submit requests to the public API at api.acedata.cloud using the documented parameters, then use the results in your application.
Input parameters and result formats vary by service. Use the public API for this model and follow its guide for generation, task retrieval and editing operations.
Clarify capacity, inputs and outputs, and invocation methods before selecting a model.
The creation parameters and delivery methods above are within this platform's invocation scope and do not mean this model includes all native editing capabilities of newer versions.
Learn what chirp-v3-0 can bring to your work.
V3's official introduction focuses on turning short text ideas into structured songs. First provide a clear theme and primary sound direction, then preview the melody, lyric delivery, and natural ending, making it suitable for completing an initial creative concept.
When you already have lyrics, you can 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 demos, rather than arranging note by note or precisely controlling the vocal performance.
Generated results are delivered as a song list and metadata, allowing applications to use the song ID, title, lyrics, status, and audio URL to build preview pages. Asynchronous mode returns a task ID, making it easy to handle submission separately from displaying results; completed results can also be received through callbacks, without requiring the user interface to keep waiting.
Start with specific tasks to find where the model can be effective.
Create a basic workflow for a song-generation app: users enter a theme, the app submits a chirp-v3-0 task, and then displays the status and playable audio. The delivery goal is to verify whether theme input, task tracking, and the listening experience work smoothly, making it suitable for prototypes that do not yet involve reusing singer identities or detailed audio track editing.
Use holiday greetings, event themes, or story lyrics as input, and combine them with the desired genre to generate song demos. 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, not a final product requiring no review.
Set the instrumental option in inspiration mode, and describe the mood of the visuals and the musical style to explore soundtrack directions for videos or presentation content. First preview whether candidate material matches the content's atmosphere, then edit and adapt it; if the task requires strict timing cues, the timing arrangement should be completed in a later audio production stage.
Choose based on task complexity, input materials, and expected results.
If an existing application already uses chirp-v3-0, or the task only needs a basic song draft, it is the choice for continuing the existing calling method. chirp-v3-5 is another version and should not be directly treated as the same entry point. 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 quality or speed differences.
If the requirements include clear male or female vocal preferences, 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, choose according to the specific capabilities of the selected version as well; do not apply the controls and editing methods of newer versions to older versions just because they share a music interface.
Arrange the input first, then connect it to the corresponding application workflow.
Prepare a clear theme, main mood, and instruments, and avoid cramming multiple creative goals into one prompt at first.
Explicitly select chirp-v3-0. Use prompt for theme creation; for custom creation, organize lyric, style, title according to this model's limits. Save task_id, retrieve audio_url after waiting for the completed result, and archive it together with the work ID and creation settings.
Design the task directly from the following inputs and acceptance priorities.
In inspiration mode, describe “an upbeat weekend getaway song, acoustic guitar, clear lead vocals, warm chorus,” and explicitly specify chirp-v3-0.
Listen for whether the theme and chorus are clear and whether the ending is natural; the older version is better suited to continuing projects that already use this model and does not inherently include the editing capabilities of newer versions.
Before formal use, understand the output quality and capability scope.
Answers to common questions when using chirp-v3-0.
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.
Yes. You can use inspiration mode, set custom to false, and describe the theme, mood, and musical direction in 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 separately from the title and style.
You can request instrumental music in inspiration mode through instrumental and use prompt to describe the genre and mood you want. 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 length.
Do not rely on this parameter to control chirp-v3-0. The valid range for vocal_gender is models 4.5 and above, and it is a preference control rather than a strict guarantee. If male or female voice preference is an important condition of the task, choose a relevant model that supports this control.
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; you can also set callback_url to receive the result. After completion, obtain the audio from audio_url in data, while also checking the song status. Do not judge generation success based only on the task ID.
Choose a development approach or application suited to this model and follow its setup guide.
↗Python SDK Integration Guide
SDK installation, authentication and examples↗TypeScript SDK Integration Guide
SDK installation, authentication and examples
↗
↗
↗This is only a basic call example. See the full docs for more parameters and advanced usage.
View Docs