SEEDANCE 2.5 API PRICING / BILLING MODEL
Pricing launches with the Seedance 2.5 API.
Public per-second rates are not published yet. Here is the confirmed billing model and what drives cost, so you can plan the integration now and verify the final rate in the provider console at launch.
PRICINGSTATUS + BILLING MODEL
Provider-mediated access · Rates pending
Estimated rates launch alongside the Seedance 2.5 API.
- Billing modelPer second of output video
- Native audioIncluded at no extra charge
- Content filter off+10% (1.1x multiplier)
- Public rate cardLaunches with the Seedance 2.5 API
Facts confirmed from the EvoLink API documentation. Verify the final rate card in the provider console before production. Last fact update: 2026-07-09.
COST DRIVERSWHAT MOVES THE BILL
Plan the request before rates are public.
| Driver | Effect on cost |
|---|---|
| Duration | Longer output costs more — billing is per second. Start with 4–8s tests. |
| Resolution | Launch tiers are 480p and 720p. Higher tiers are pending provider confirmation. |
| Content filter | Leaving it on is free; turning it off adds ~10%. |
| References | Image / video / audio references are inputs; they do not carry a separate per-reference fee. |
Billing is per second of output. Native audio is free. Treat 1080p / 4K as pending until provider docs confirm support.
PROVIDER HANDOFFWHEN YOU ARE READY
Recommended next step: create a provider key only after the request is prepared.
The best conversion moment is after the user understands status, knows the billing model, and has code or an agent prompt ready.
Q&APRICING
Q.01How much does the Seedance 2.5 API cost?
Public per-second rates are not published yet — they launch alongside the API. Billing is per second of output video, and native audio is included at no extra charge. Verify the final rate in the provider console before production.
Q.02Why is there no price calculator?
Because there is no confirmed public rate to calculate from. Showing an invented number would be misleading. This page explains the billing model instead, and a calculator returns once rates are public.
Q.03What should agents do about pricing?
Treat cost as unpublished, surface it as an estimate to the human, and verify provider billing before live traffic.
AGENT NOTECONTEXT
Agents should read /llms-full.txt and /openapi.json, treat cost as unpublished, and ask the human to verify provider billing before live calls. Last fact update: /llms-full.txt · /openapi.json · 2026-07-09.