Is There a Suno V6 API?Not from Suno — but v6 is callable here
Suno shipped v6, v6-wild and v6-mini on 9 September 2026 — to the web app, not to developers. The launch announcement says nothing about API access, and Suno still has no public self-serve API at any subscription tier. What changed on 9 September is our side: MusicAPI now serves all three v6 models. Pass sonic-v6, sonic-v6-wild or sonic-v6-mini as mv. They cost exactly what the models they replace cost.
Status verified 9 September 2026 · 75 free credits on signup · No card required
MusicAPI is an independent provider and is not affiliated with, endorsed by, or partnered with Suno. We expose Suno-compatible models through our own API, keys and billing — Suno itself publishes no self-serve API.
What Suno actually shipped on 9 September
Three models, two of them behind paid Suno tiers. The right-hand column is the one you came for, and it reads the same all the way down.
| Model | Who can use it | Developer access |
|---|---|---|
| v6 | Suno Pro and Premier subscribers | mv: sonic-v6 |
| v6-wild | Suno Pro and Premier subscribers | mv: sonic-v6-wild |
| v6-mini | All Suno users, including the free tier | mv: sonic-v6-mini |
Variants and tier gating per Suno's launch announcement, 9 September 2026. Availability column reflects the absence of any documented public endpoint as of 10 September 2026.
Most of what v6 headlined is already an endpoint here
v6 bundles several editing workflows into the Suno app. Those workflows are not new to APIs — four of them have shipped endpoints on MusicAPI today, running on v5-class models.
Suno lists for v6: “Build a mashup from multiple sources in one request”
Callable today — Mashup endpoint — combine two tracks into one composition
Suno lists for v6: “Update a single lyric without rebuilding the entire song”
Callable today — Replace-section — regenerate a specific time range and keep the rest of the track intact
Suno lists for v6: “Sample, isolate and build a new beat in a single workflow”
Callable today — Stem separation — 4-track basic or 12-track full isolation of an existing song
Suno lists for v6: “Edit part of an existing song using plain language”
Callable today — Extend and cover — continue a clip or re-render it in a new style from a text prompt
The gap is the model weights, not the capability. If your product needs section-level editing or stem isolation through an API, you do not have to wait for v6 to build it.
What you can call right now
A real request against v6. It runs on the free signup credits — no card, no subscription.
1# v6 is callable today. sonic-v6-wild and sonic-v6-mini work the same way.
2curl -X POST "https://api.musicapi.ai/api/v1/sonic/create" \
3 -H "Authorization: Bearer $MUSICAPI_KEY" \
4 -H "Content-Type: application/json" \
5 -d '{
6 "prompt": "late-night neo-soul, brushed drums, female vocal",
7 "mv": "sonic-v6"
8 }'Model selection is an explicit mv parameter on every request, so v6 arrived as additional accepted values and broke nothing: every older id is still valid and still costs the same. One caveat worth knowing — Suno retired v3.5 through v5.5 on its own platform, so a request naming one of them is served by v6 upstream. The value you send and read back does not change; the sound can.
How model changes reach you
v6 landed here the day Suno shipped it. That will not always be the case, so what we commit to is the mechanics rather than the timing:
- A new model arrives as a new
mvvalue. Existing calls are untouched. - It is written to the changelog before it ships, along with anything that could change what an existing integration receives.
- Pricing follows model cost. Newer, more expensive models consume proportionally more credits; the price per credit does not move because a model launched.
Until then, this page states the status as of 10 September 2026. If you are reading it much later and it still says “not yet,” check the changelog — that is the source of truth, this page is a snapshot.
Questions developers actually ask
- Is there a Suno V6 API?
- Not from Suno. Suno released v6, v6-wild and v6-mini on 9 September 2026 inside the suno.com web app, and it still has no public self-serve API at any subscription tier. MusicAPI does expose them: since 9 September 2026 sonic-v6, sonic-v6-wild and sonic-v6-mini are accepted values of the mv parameter on the generation endpoints.
- Does MusicAPI support Suno V6?
- Yes, since 9 September 2026. Pass mv as sonic-v6, sonic-v6-wild or sonic-v6-mini on the generation endpoints. All three cost the same as the model tier they replace — adding v6 did not change any price. The older mv values still work too: Suno retired v3.5 through v5.5 on its side and maps them onto v6.
- What can I call on v6 today?
- The full Suno-compatible surface, now on v6: generation, extend, cover, replace-section, mashup, stem separation, WAV conversion and timestamped lyric alignment. Several capabilities Suno marketed as new in v6 — mashups from multiple sources, regenerating one section of a song, isolating stems — have been callable on MusicAPI for months and are unchanged by the model switch.
- Did adding v6 break my existing integration?
- No. Model selection is an explicit mv parameter, so adding sonic-v6 did not change any existing call: every older mv value is still accepted and still costs the same. One thing to know is that Suno retired the older models on its own platform, so a request naming one of them is served by v6 upstream — the audio character can change even though your request and the mv you read back do not.
- Is MusicAPI an official Suno API?
- No. MusicAPI is an independent provider and is not affiliated with, endorsed by, or partnered with Suno. Suno publishes no public self-serve API at any subscription tier, so there is no official Suno API to be a reseller of. What MusicAPI provides is its own API, its own keys and its own billing, exposing Suno-compatible models including the v6 family.
Build on what ships today
A key takes a minute and costs nothing — 75 free credits on signup, no card, full commercial rights on every track. When v6 becomes callable, your integration picks it up as one new parameter value rather than a migration.