FAQ
Signup includes 10 free credits, enough for one full song. A full song costs 10 credits, a 30-second clip 1 credit, and a studio WAV master 20 credits. Packs are one-time purchases: 50 credits for $5, 200 credits for $15, 500 credits for $30.
Credits are spent when a generation starts. If it fails, the credits go back to your balance (not a cash refund), once per failed run. Only finished songs keep their charge.
IronSound does not put an expiry date on credits. Your balance is what you were granted or bought minus what you spent. Credits have no cash value and are not transferable.
Polar is the reseller and merchant of record, so payment refunds go through Polar under its buyer terms. A credit return after a failed run is not a cash refund: the credits go back to your balance (not a cash refund).
No. One song generates at a time per account. Starting a second one returns the running job instead of spending more credits.
Every song comes with the mix (MP3, or WAV for studio WAVs) and a per-song license file you can keep with the track. You also get stems and a streaming master on full songs and studio WAVs (not 30-second clips). Vocals and drums are separated from the mix; bass and other are derived reference tracks, not separated stems. The streaming master aims at about -14 LUFS.
Not all four. Vocals and drums are separated from the mix; bass is an 80 Hz amplitude-modulated reference derived from the vocal envelope, and other is a side-channel residual. Those two are derived reference tracks, not separated stems. The README in the stems zip explains each file.
No. A clip ships the mix and its license file. Stems and the streaming master come with full songs and studio WAVs: stems and a streaming master on full songs and studio WAVs (not 30-second clips).
Full songs can be 1 to 4 minutes. The composer offers Auto, 1, 2, or 3 minutes, and the API accepts up to 4. Clips are 30 seconds, handy for a hook, a jingle, or testing an idea before you spend a full song.
You may use songs you generate, including commercially, under the per-song license. Full songs are made with YuE2-3B, self-hosted on IronSound-operated servers, when that engine is available; otherwise they fall back to Google Lyria 3.5. 30-second clips use Google Lyria 3 Clip, and studio WAV masters use Google Lyria 3.5. Lyria output carries an inaudible Google SynthID watermark; YuE2-3B output does not. Each song's license file names the engine that made it. Lyria tracks are also subject to Google Gemini paid API terms. Do not clone a specific artist's voice, submit copyrighted lyrics you do not own, or generate content that violates applicable law.
Your per-song license spells out what you can do: use the track, including commercially, subject to IronSound terms (and Google Gemini paid API terms on Lyria tracks). It covers the generated track only, not the model or its training data.
No. Do not clone a specific artist's voice and do not submit copyrighted lyrics you do not own. The composer refuses prompts that ask for voice cloning, a named artist, or a reference track.
Each license.txt carries a signature bound to the song ID, engine, and date. Anyone can check a song's stored license signature at /api/licenses/verify?songId=<id>, no account needed, once the song's license has been issued.
Yes. Songs stay on your account. There is no public feed and no Explore tab. Audio sits in private storage and streams only to the signed-in owner.
Sharing is off by default. If you opt a song in, its share page shows the title, the license signature, and a link that loads the song's prompt into someone else's composer. It does not stream your audio.
Lyria tracks (every clip and studio WAV, and full songs that fall back to Lyria) send your prompt to Google to generate audio. Full songs with vocals and no lyrics of your own send the prompt to Google Gemini to draft lyrics. IronSound does not sell your personal data.
Full songs are made with YuE2-3B, self-hosted on IronSound-operated servers, when that engine is available; otherwise they fall back to Google Lyria 3.5. 30-second clips use Google Lyria 3 Clip, and studio WAV masters use Google Lyria 3.5. Lyria output carries an inaudible Google SynthID watermark; YuE2-3B output does not. Each song's license file names the engine that made it.
Lyria tracks (Lyria 3.5 and Lyria 3 Clip) carry an inaudible Google SynthID watermark. Do not remove it. YuE2-3B tracks do not carry SynthID and are still labeled AI-generated.
Yes. An AI-generated badge sits on the player, the song page, and the download buttons. Exported streaming masters and stems carry AI-generated provenance in the WAV metadata, and license.txt names the engine.
Yes. The generate_song tool lives at /api/mcp/generate. A GET returns the public manifest. A POST runs with your signed-in IronSound session, or with a service key scoped to soundtrack generation, which can start clips only.
The same as the composer: full song 10 credits, clip 1 credit, studio WAV 20 credits. HTTP 402 means the account needs credits. HTTP 409 means a song is already generating and the response names that job.
More detail lives in the licensing guide, AI transparency, and agents pages. The terms of service are the legal source.