Suno is a music-generation service that turns a written idea into songs. The documented automatic workflow accepts a short description of the intended music and an instrumental choice, then generates two songs. Use the brief to establish the theme, mood and musical direction you want to hear in the completed tracks.
Start with the role the music should play. A calm background for an explanation, an energetic opening for a short video or a reflective song about a journey each gives the brief a concrete purpose. Describe the intended mood and the musical features that matter to that purpose in a few clear phrases.
For a song with vocals, make the theme and language clear in the creative brief. Describe the idea the track should express and the tone the performance should convey. Listen to the completed result for how the vocal, words and arrangement work together. Retain the generated track information alongside the audio for review.
For an instrumental result, use the documented instrumental selection and describe the musical direction in the text. State the desired atmosphere and prominent instruments when those matter to the project. Review the finished track for the place it will occupy in the edit, including the sections that need to sit beneath speech or support a visual transition.
The automatic workflow produces two songs from the submitted idea. Treat them as distinct candidates and preserve both completed audio files. Listen to each through its opening, development and ending. Compare the actual tracks against the same purpose, including their mood, arrangement and suitability for the planned use.
Generation is organized as a task. Keep the returned task ID while checking its result and distinguish completed tracks from items still in progress. The documented result includes track-level information such as title, status, audio location and duration. Save the finished audio itself with the available metadata and the original brief.
For a video or presentation, audition the selected music against the real material. Check the opening, transitions and ending at the intended listening level. Mark the section that serves the edit and retain the full track for later changes. A suitable music excerpt is judged in context with the voice, images and pacing of the finished piece.
Keep the written idea, instrumental selection, model selection and all completed tracks together. When a candidate needs revision, identify the musical mismatch, such as an arrangement that is too dense beneath speech or an opening that develops too slowly. Preserve the useful direction and revise the part of the brief connected to that issue.
", "aboutText": "Suno is a music-generation service that turns a written idea into songs. The documented automatic workflow accepts a short description of the intended music and an instrumental choice, then generates two songs. Use the brief to establish the theme, mood and musical direction you want to hear in the completed tracks.\n\nStart with the role the music should play. A calm background for an explanation, an energetic opening for a short video or a reflective song about a journey each gives the brief a concrete purpose. Describe the intended mood and the musical features that matter to that purpose in a few clear phrases.\n\nFor a song with vocals, make the theme and language clear in the creative brief. Describe the idea the track should express and the tone the performance should convey. Listen to the completed result for how the vocal, words and arrangement work together. Retain the generated track information alongside the audio for review.\n\nFor an instrumental result, use the documented instrumental selection and describe the musical direction in the text. State the desired atmosphere and prominent instruments when those matter to the project. Review the finished track for the place it will occupy in the edit, including the sections that need to sit beneath speech or support a visual transition.\n\nThe automatic workflow produces two songs from the submitted idea. Treat them as distinct candidates and preserve both completed audio files. Listen to each through its opening, development and ending. Compare the actual tracks against the same purpose, including their mood, arrangement and suitability for the planned use.\n\nGeneration is organized as a task. Keep the returned task ID while checking its result and distinguish completed tracks from items still in progress. The documented result includes track-level information such as title, status, audio location and duration. Save the finished audio itself with the available metadata and the original brief.\n\nFor a video or presentation, audition the selected music against the real material. Check the opening, transitions and ending at the intended listening level. Mark the section that serves the edit and retain the full track for later changes. A suitable music excerpt is judged in context with the voice, images and pacing of the finished piece.\n\nKeep the written idea, instrumental selection, model selection and all completed tracks together. When a candidate needs revision, identify the musical mismatch, such as an arrangement that is too dense beneath speech or an opening that develops too slowly. Preserve the useful direction and revise the part of the brief connected to that issue.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "7f01830e4b50e58ee0f4ae9187c94f3e0e8d2c01f7e274bec5dd2ca34ed84b7e", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "suno-apiSuno creates music from a short written idea. The documented automatic workflow produces two songs and includes an instrumental choice, with completed audio and track metadata returned through the generation task.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Suno is a music-generation service that turns a written idea into songs. The documented automatic workflow accepts a short description of the intended music and an instrumental choice, then generates two songs. Use the brief to establish the theme, mood and musical direction you want to hear in the completed tracks.
Start with the role the music should play. A calm background for an explanation, an energetic opening for a short video or a reflective song about a journey each gives the brief a concrete purpose. Describe the intended mood and the musical features that matter to that purpose in a few clear phrases.
For a song with vocals, make the theme and language clear in the creative brief. Describe the idea the track should express and the tone the performance should convey. Listen to the completed result for how the vocal, words and arrangement work together. Retain the generated track information alongside the audio for review.
For an instrumental result, use the documented instrumental selection and describe the musical direction in the text. State the desired atmosphere and prominent instruments when those matter to the project. Review the finished track for the place it will occupy in the edit, including the sections that need to sit beneath speech or support a visual transition.
The automatic workflow produces two songs from the submitted idea. Treat them as distinct candidates and preserve both completed audio files. Listen to each through its opening, development and ending. Compare the actual tracks against the same purpose, including their mood, arrangement and suitability for the planned use.
Generation is organized as a task. Keep the returned task ID while checking its result and distinguish completed tracks from items still in progress. The documented result includes track-level information such as title, status, audio location and duration. Save the finished audio itself with the available metadata and the original brief.
For a video or presentation, audition the selected music against the real material. Check the opening, transitions and ending at the intended listening level. Mark the section that serves the edit and retain the full track for later changes. A suitable music excerpt is judged in context with the voice, images and pacing of the finished piece.
Keep the written idea, instrumental selection, model selection and all completed tracks together. When a candidate needs revision, identify the musical mismatch, such as an arrangement that is too dense beneath speech or an opening that develops too slowly. Preserve the useful direction and revise the part of the brief connected to that issue.
POST /v1/music/generationstextaudio, image, video| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits suno-api Conditions: Use this exact Ailoot routing selector. | Default— |
Fieldgpt_description_prompt | Typestring | RequirementRequired | Values & limits Conditions: Describe the musical idea or song theme. | Default— |
Fieldmv | Typestring | RequirementRequired | Values & limits chirp-fenix, chirp-crow, chirp-bluejay, chirp-auk, chirp-v4, chirp-v3-5 Conditions: Select an explicit documented Suno version; example uses chirp-crow (v5). | Default— |
Fieldmake_instrumental | Typeboolean | RequirementRequired | Values & limits Conditions: Set true for instrumental music or false for a song. | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, gpt_description_prompt, mv, make_instrumental |
Parameteroptional | Contract |
Parametermaterial_types | Contracttext |
Parameterconditions | ContractUse this exact Ailoot routing selector., Describe the musical idea or song theme., Select an explicit documented Suno version; example uses chirp-crow (v5)., Set true for instrumental music or false for a song. |
Lifecycle: submit_once_poll_original
GET /v1/music/generations/{request_id}
GET /v1/media/assets
GET /v1/media/assets/{asset_id}
The displayed rates estimate the cost before generation. The final charge is calculated from the cost recorded for the original generation. Measured output duration and forecast quantities are not the final billable quantity.
Tariff references do not add request options. Supported parameters are listed for the selected method.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Rate schedule | Forecast quantity | Billing quantity | Charge |
|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Forecast quantity— | Billing quantity— | Charge Input · Input tokens · Estimate for comparison only — / 1K tokens Output · Output tokens · Estimate for comparison only — / 1K tokens Input · Cache read · Estimate for comparison only — / 1K tokens Input · Cache write · Estimate for comparison only — / 1K tokens Input · Cache write, 1 hour · Estimate for comparison only — / 1K tokens |
| ConfigurationPer request | Rate schedule— | Forecast quantity— | Billing quantityone request | Charge Input · Estimate for comparison only $0.2 per request |
| ConfigurationEstimated generation cost | Rate schedule— | Forecast quantityone generation estimate | Billing quantity— | Charge Output · Estimated generation cost · Estimate for comparison only $0.2 estimate before generation This estimate is not an additional charge or a fixed rate for the completed generation. |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\ncat > request.json <<'JSON'\n{\n "model": "suno-api",\n "gpt_description_prompt": "古诗词",\n "mv": "chirp-crow",\n "make_instrumental": false\n}\nJSON\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/music/generations \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\n# Create once; retain id, polling_url, original task identifiers and every header.\nset -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\nexport AILOOT_API_KEY\npython3 - <<'PY_STATUS'\nimport json,os,subprocess\nfrom pathlib import Path\nfrom urllib.parse import urljoin,urlsplit\nr=json.loads(Path("result.json").read_text())\nu=urljoin("https://api.ailoot.ai",r["polling_url"])\np=urlsplit(u)\nif p.scheme!="https" or p.netloc!="api.ailoot.ai" or p.username or p.password:\n raise SystemExit("Unexpected returned polling URL; preserve the response")\nsubprocess.run(["curl","--fail-with-body","--silent","--show-error",u,"-H","Authorization: Bearer "+os.environ["AILOOT_API_KEY"],"-D","status-headers.txt","-o","status.json"],check=True)\n# Read this same original polling_url again while pending.\n# Preserve unknown/result_pending_check; do not repeat creation.\nPY_STATUS\nset -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\nexport AILOOT_API_KEY\npython3 - <<'PY_ASSETS'\nimport json,os,subprocess\nfrom pathlib import Path\nfrom urllib.parse import urljoin,urlsplit\nr=json.loads(Path("status.json").read_text())\nroles={}\ndef visit(v,path=""):\n if isinstance(v,dict):\n for k,x in v.items(): visit(x,path+"/"+k)\n elif isinstance(v,list):\n for i,x in enumerate(v): visit(x,path+"/"+str(i))\n elif isinstance(v,str):\n u=urljoin("https://api.ailoot.ai",v); p=urlsplit(u)\n if p.scheme=="https" and p.netloc=="api.ailoot.ai" and not p.username and not p.password and p.path.startswith("/v1/media/assets/") and p.path.endswith("/content"):\n roles.setdefault(u,[]).append(path)\nvisit(r)\nif not roles: raise SystemExit("No completed owned assets; retain the original status")\nmanifest=[]\nfor i,(u,paths) in enumerate(roles.items()):\n target=Path(f"asset-{i}.bin")\n subprocess.run(["curl","--fail-with-body","--silent","--show-error",u,"-H","Authorization: Bearer "+os.environ["AILOOT_API_KEY"],"-o",str(target)],check=True)\n raw=target.read_bytes()\n if not raw: raise SystemExit("Empty asset; retain original status and metadata")\n ext="glb" if raw[:4]==b"glTF" else "png" if raw[:8]==b"\\x89PNG\\r\\n\\x1a\\n" else "jpg" if raw[:3]==b"\\xff\\xd8\\xff" else "webp" if raw[:4]==b"RIFF" and raw[8:12]==b"WEBP" else "mp4" if raw[4:8]==b"ftyp" else "bin"\n name=f"asset-{i}.{ext}"\n if target.name!=name: target.rename(name)\n manifest.append({"file":name,"response_paths":paths,"bytes":len(raw)})\nPath("asset-manifest.json").write_text(json.dumps(manifest,indent=2))\nprint("Saved",len(manifest),"unique owned assets; every response role retained")\nPY_ASSETS\nDownload each returned image or save its Base64 contents
GET /v1/music/generations/{request_id}GET /v1/media/assetsGET /v1/media/assets/{asset_id}Keep every complete returned response, file and content part.
Retain the complete response and headers, original identifiers, every actual output and all usage/accounting fields. Save each unique owned asset and retain every role pointing to it.
Keep the returned public task or operation id and all headers. Read only the original task; unknown or result_pending_check does not authorize another creation.
| Field | Type |
|---|---|
Fieldid | Typestring |
Fieldpolling_url | Typestring |
Fieldprovider_task_id | Typestring |
Fielddata.task_id | Typestring |
Fielddata.status | Typestring |
Fielddata.data[].audio_url | Typestring |
Fielddata.data[].image_url | Typestring |
Fielddata.data[].image_large_url | Typestring |
Fielddata.data[].video_url | Typestring |
Ailoot Ultra suno-api
Use the method paths shown above.