Seedance 2.5 reference counts: Together's 30/10/10 vs Sume docs

Together AI's page for Seedance 2.5 says the model takes up to 30 images, 10 video clips and 10 audio clips in one pass, 50 in all, and generates 30-second audio-video clips. Sume's docs confirm seedance-2.5 accepts 4 to 30 seconds at 480p, 720p and 1080p, and that the Seedance 2.x models take audio and video references. The docs give no per-request counts for Seedance, so do not assume Together's numbers hold on Sume.

A quota on a vendor page is a statement about that vendor's endpoint. A router can pass fewer, or enforce its own caps.

What each source gives

The one model where Sume does state counts

For gemini-omni-flash-1.1, the Video Router docs set reference caps: up to 10 images and up to 3 videos, each up to 3 seconds, with no audio references. Those numbers are for that model only. They show that a router's caps can be far lower than a headline vendor figure, which is why you should not carry any one model's counts to another.

A test that settles it

Build the request you need with the real number of references and send it to a test key. Start with a small clip at 480p to keep the test cheap. If it passes, check the output for every reference you meant to use, since accepting a reference is not the same as using it well.

Also read supported_input_references from the catalog at submit time rather than copying this table. The docs tell you to check the catalog because limits differ by model and change as models are added.

Why the counts differ in kind

Together's figures describe the model on Together's endpoint. A Sume request passes through the Video Router, which validates fields before it forwards them. The router can accept fewer references than the model can use. Neither number is wrong. They answer different questions, so the one that governs your cost and success is the one on the platform you call.

For a design that needs many references, such as a character sheet plus a style board, count the references you need. If it is more than ten, test the request on Sume before committing, and have a plan to merge references into a single sheet if the cap is lower than hoped.

Cost of references

References are not free either. On Sume a reference video changes the Seedance token count: the pricing code adds 15 assumed seconds and then applies a 0.6 multiplier, as described in the post on reference video cost. A request with many video references should be priced before it is sent, not after.