Suno API Pricing: Every Operation and Your Monthly Cost

Suno API pricing on reAPI starts with a clear billing unit: a completed song-generation request costs $0.06, or 60 credits, and covers two returned takes. That works out to $0.03 per returned track if you count both. Editing, stem separation and exports are separate operations with separate fees.^[1]

The useful budget is the one for your whole workflow. A product that keeps both takes has a different cost per usable song from one that discards a take, regenerates it and exports the selected result to WAV. The table below lists all 18 asynchronous Suno operations, followed by explicit monthly scenarios. Prices were checked on reAPI's public model pages on September 14, 2026.

TL;DR

• Song generation costs $0.06 per completed request, covering two takes. A $0.03-per-track calculation does not change the billing unit.^[1]
• The full family has 18 asynchronous operations. Vocal separation has three price options under one model ID.^[2]
• Sound FX lists a raw $0.0125 rate but deducts 13 whole credits, equivalent to $0.013. Budget with the debit.^[1]
• V6, V6 Mini and V6 Wild cost the same for the same operation. A shorter requested song does not lower that fixed fee.^[3]
• Task polling does not consume credits; failed generations are refunded under the public documentation.^[3]

Suno subscription prices and API prices buy different things

A Suno subscription is an account plan for its music product. The official product page lists plans with creation credits, downloads and feature access. Those subscription credits belong to Suno's product and should not be substituted for reAPI credits in an API budget.^[4]

reAPI prices its own API operations in credits, with 1 credit equal to $0.001. The Suno model page is the public rate card for these calls.^[1] A monthly Suno subscription payment does not top up a reAPI account, and a reAPI payment is not a Suno consumer subscription.

This distinction also prevents a misleading comparison: a subscription's advertised song allowance is not a per-request API quote. Account access, allowed downloads and API operations are different units. Compare them only after defining what the application actually needs to do. The official API status guide explains the access and rights boundaries.

Suno API pricing for all 18 asynchronous operations

The table gives the billed USD equivalent and the whole-credit debit for each completed request. There are 20 rows because suno-vocal-separation has three options; it remains one operation in the 18-operation family. Model IDs and option values follow the public reference.^[1][2]

These rates describe separate operations, not a bundle that runs automatically after a song. If you request a WAV file and stems, add the applicable calls. A cheap asset operation can also require an existing task or another valid source; its price does not include creating that source.^[2]

For stem separation, choose the type deliberately. The default is separate_vocal. split_stem_advanced uses stem_name to select the requested instrument, while split_stem is the full separation option. Do not attach the cheapest separation price to all three modes.^[2]

The four synchronous helper endpoints are outside this asynchronous table. If your workflow also calls style boosting, timestamped lyrics, persona creation or voice checks, consult their entries in the complete Suno reference and include any applicable charges. “18 operations” is the async scope, not a claim that every possible Suno-related call is in the table.

Why Sound FX shows $0.0125 and 13 credits

The operation selector lists $0.0125, while the billing table displays $0.013 and 13 credits. The fractional raw amount is rounded up to a whole-credit debit. Both values appear on the public page; they describe different stages of the price display.^[1]

For a hypothetical 1,000 completed sound requests, use 13,000 credits, equivalent to $13. Using the raw figure would produce $12.50 and understate that debit by $0.50. These are arithmetic examples using the displayed rate, not measured monthly bills.

Two returned tracks are not always two usable songs

The Suno API price per song depends on which denominator you mean. A completed suno-music request covers two returned takes. The production request checked for this series returned two audio URLs and two track records, matching the documented song-generation behavior.^[2]

There are two useful calculations:

• Returned-track cost: $0.06 divided by two is $0.03.
• Selected-song cost when you keep one take: the request still costs $0.06.

Neither calculation includes another paid attempt. If a completed request produces valid audio that you decide not to use, count it in your creative budget. Do not categorize every unwanted musical result as a technical failure or assume it qualifies for the documented failed-task refund.

The distinction becomes more important when an application promises one finished song to a customer. Count the completed generations needed to deliver that song, then add its chosen edits and exports. This article does not invent a rejection rate, retry rate or average number of attempts; those depend on your own acceptance criteria.

The three V6 variants share the same operation price

V6, V6 Mini and V6 Wild do not introduce separate prices for a given operation. The V6 documentation also describes flat pricing without a duration or output-length multiplier.^[3]

Choose a variant for the result you need. Mini's positioning around speed does not make it a discounted billing tier. Likewise, requesting a shorter custom-mode track changes the creative target within the supported limits, not the fixed song-generation charge.

For variant selection and version migration, use the Suno V6 API guide. Keep any evaluation budget separate from the operating budget: if you send the same brief to several variants, each completed request is a call to pay for.

Budgeting 1,000 or 10,000 songs a month

The following scenarios are explicit arithmetic assumptions. They use the $0.06 completed song-request rate, exclude additional attempts and follow-up operations, and assume the rate does not change. They are not discounts, observed customer invoices or promises of creative acceptance.^[1]

The first pair counts everything returned. The second pair assumes one selected song from every request. Neither assumes that a new attempt is necessary. If your application needs more attempts, add them using the same request rate.

For a more complete example, suppose you select one song from each of 1,000 completed requests, export all 1,000 to WAV and run basic vocal separation on 250 selected songs:

This example adds only the operations the application requested. Replace the quantities with your actual counts, and change the separation rate if you choose another mode.

For each completed job, record the operation, any price-affecting option and whether the output was selected. That gives you both the API bill and the cost per accepted song. A single “songs generated” counter cannot explain the difference.

To turn this budget into a first authenticated request, follow the Suno API key guide.

FAQ

How much does the Suno API cost on reAPI?

A completed song-generation request costs $0.06 for two takes. Other asynchronous operations have their own prices, from $0.001 for the listed low-cost helpers to $0.25 for full stem separation.^[1]

Is the price per song or per request?

The charge is per completed request. $0.03 per returned track is the arithmetic result when both takes from a $0.06 song request are counted; you do not buy a single take for that amount.^[1]

Is Suno V6 Mini cheaper than V6 or Wild?

No, not for the same operation on reAPI. The public V6 documentation states that all three variants have the same operation price.^[3]

Are polling and failed tasks charged?

Polling does not consume credits. The public docs state that failed generations are refunded. A completed result you choose not to use is different from a failed task.^[3]

How far does a $0.10 test balance go?

At $0.06 per song request, it funds one completed request and leaves $0.04. It does not fund a second full-song request. This is a balance example; check your actual promotional eligibility and available credits.^[1]

Does the API price include commercial rights?

The price table states processing charges, not a rights grant. Suno's current terms contain separate commercial-use conditions. Read the official-access and rights explanation and confirm the agreement covering your output before commercial use.

Budget the calls your application actually makes

Start with the generation requests, decide whether your output target counts both takes or only selected songs, then add the editing and export calls. Use whole-credit debits where the displayed raw rate is fractional. That makes Suno API pricing a budget you can reconcile with actual jobs, without assuming every returned track becomes a finished deliverable.

References

1. reAPI. Suno public rate card. Retrieved September 14, 2026 from reapi.ai/models/suno.
2. reAPI. Suno API: operations and output formats. Retrieved September 14, 2026 from reapi.ai/docs/suno.
3. reAPI. Suno V6: pricing dimensions and task handling. Retrieved September 14, 2026 from reapi.ai/docs/suno-v6.
4. Suno. Consumer product plans. Retrieved September 14, 2026 from suno.com.