Sume wallet presets $50, $100, $500, $1,000: what each buys

A $50 Sume wallet top-up buys 17 whole 5-second Seedance 2.5 clips at 720p, or 80 Wan 3.0 clips at 720p, or 400 music generations, or about a million characters of text to speech. The dashboard's other presets, $100, $500 and $1,000, scale those numbers linearly, because 1 credit is $1 and there is no volume tier in the rates below. Teams can buy any amount from $10 to $1,000 on demand.

The question the presets answer is not price per unit, which does not move, but how much headroom to fund before a job returns a 402 insufficient_credits.

What does each preset buy?

The Video Router bills provider list times 1.25. At 720p in 16:9, Seedance 2.5 is $0.5778 a second, so a 5-second clip is $2.89, and Wan 3.0 is $0.125 a second, so a clip is $0.625. Sume's API pricing page lists Music at $0.125 a generation and TTS at $0.0475 per 1,000 characters.

Why is there no discount at higher presets?

I found none in the docs or on the pricing page. A $1,000 top-up buys exactly 20 times a $50 one, and the table shows it. Per-unit prices on Sume are set by the model's rate card, not by how much you load at once. If you are comparing it with a plan, that is the main structural difference: several vendor plans get cheaper per credit at higher tiers, a wallet at fixed rates does not.

What does a bigger balance not change?

It does not change what a clip costs, which model you can call or how many jobs run at once; concurrency is set by your plan, from 1 concurrent job on Free to 20 on Scale. It also does not turn a 5-second Seedance 2.5 clip at 720p into anything but $2.89. If a clip is priced in tokens, a longer clip or a different aspect ratio moves the number, so rerun the table for your own duration before you size a top-up.

How do I pick a preset?

Estimate one week of real jobs from the table, then fund about two weeks. A smaller top-up keeps cash free and costs nothing extra, because the price per unit is the same; a larger one reduces how often a bulk job stalls on a low balance. The API exposes GET /v1/balance, so a script can check the wallet before a batch, and GET /v1/usage shows what recent jobs drew.

The smallest purchase is covered in what $10 buys and what $10 buys job by job.

• Top-ups are a dashboard operation; there is no public top-up endpoint.
• When the balance is short, the API returns 402 insufficient_credits.
• Check the balance with GET /v1/balance before a large batch.