Tunova
Suno v4.5 · v5 · v5.5 · auto-refund on failure

The Suno API that doesn’t break.

Generate music programmatically with the newest Suno models. Async jobs, signed webhooks, automatic retries — and one simple rule: a failed render refunds itself. You’re billed only when a song actually delivers.

No card. 50 free tokens ≈ 5 songs. First song in minutes.

Request and response

request
# one call → 202 + a job_id curl https://s.serge.cc/api/generate \ -H "X-API-Key: $SUNOAPI_KEY" \ -H "Content-Type: application/json" \ -d '{"prompt":"calm rainy-night lofi","model":"v5.5"}'
response
HTTP/2 202 {"job_id":"8f3a1c2e-…","status":"queued", …} # ~2 min later — HMAC-signed webhook {"job_id":"8f3a1c2e-…","status":"complete", "clips":[{"audio_url":"https://…mp3","duration":187.4, …}]} # and when a render fails: {"job_id":"8f3a1c2e-…","status":"failed", "error":"render timeout", …} # → 10 tokens back on your ledger, automatically

That last line is the product: when a render fails, the refund posts itself — no ticket, no waiting, no asking.

Features

Newest models, day one

v4.5, v5 and v5.5 — selectable per request with the model param. New Suno models land here shortly after they ship.

"model": "v4.5" | "v5" | "v5.5"

Billed on success only

Prepaid tokens; a failed render auto-refunds. Your balance is the hard spend cap, and every charge and refund is a line on a transparent statement.

failed render = 0 tokens

Async & dependable

Submit returns 202 + a job_id — poll it, or get an HMAC-signed webhook. Idempotency keys make retries safe; transient failures retry automatically.

202 → webhook → mp3

Agent-native (MCP)

Point Claude, Cursor or any MCP client at POST /mcp. Same API key, same billed-on-success rule.

generate_song · wait_for_song · check_song

Failed render? You don’t pay.

Every job settles against your ledger: render succeeds → 10 tokens. Render fails → automatic refund, same statement. No tickets. No “contact support for credits”.

entryreftokens
charge8f3a1c2e-…−10
refund8f3a1c2e-…+10

Pay per song. Only for songs that exist.

Starter

$10
1,000 tokens
100 songs$0.10 / song
billed only when the song renders

Plus +10%

$25
2,750 tokens
275 songs~$0.091 / song
billed only when the song renders

Pro +20%

$50
6,000 tokens
600 songs~$0.083 / song
billed only when the song renders

Max +30%

$100
13,000 tokens
1,300 songs~$0.077 / song
billed only when the song renders

No monthly plan. No expiring tokens. Top up when you need it — the balance waits for you. Pay with crypto — USDT, BTC and more via OxaPay; card payments coming. 1 song = 10 tokens · lyrics = 2.

50 free tokens on signup — no card.

Honest answers

Is this an official Suno product?

No. Tunova is an independent service, not affiliated with or endorsed by Suno. We run our own paid Suno accounts and absorb that operational risk ourselves.

What happens when Suno ships a breaking change?

It has happened before and it will happen again. We drive the real Suno app — the same path a human takes — so changes that kill reverse-engineered wrappers usually cost us hours, not weeks. Worst case: jobs queue and retry, and any render that still fails refunds automatically.

What if my render fails?

You get the tokens back, automatically. The refund posts to your ledger as its own statement line the moment the job settles — no ticket, no email, nothing to claim.

Can I use the tracks commercially?

Renders come from paid Suno plans, which carry commercial-use rights under Suno’s terms. Review Suno’s terms for your use case — we add no license of our own.

How do I pay?

Prepaid tokens, bought with crypto — USDT, BTC and more via OxaPay. Tokens never expire. Card payments are coming. Every account starts with 50 free tokens, no card.

How fast is a render?

Most songs deliver in about 1–3 minutes. If you pass a callback_url, the webhook fires as soon as the render settles — typically within seconds of finishing.

Suno API for developers — generate music via REST | Tunova