SEEDANCE 2.5 API PRICING / BILLING MODEL
Price the Seedance 2.5 request you plan to run.
The official BytePlus / Volcengine price sheet is upstream evidence, not a third-party provider quote. Check the recommended provider’s current price, then reconcile your budget against actual usage.
PRICINGSTATUS + BILLING MODEL
Live on EvoLink · API key access available · EvoLink route live
Use the live EvoLink console price for your exact workflow.
- EvoLink routeLive — current price shown in console
- Workflow IDsT2V / I2V / R2V
- Launch tiers4–30 seconds · 480p / 720p
- Official rate cardPublished upstream; not an EvoLink quote
The route is live. This independent site does not freeze an EvoLink unit quote without a published rate-card value; use the current console price and reconcile a short test before scaling. Last fact update: 2026-08-07.
COST DRIVERSWHAT MOVES THE BILL
Price the exact request you plan to run.
| Driver | Effect on cost |
|---|---|
| Duration | Longer clips cost more; read the per-duration rate for your workflow in the EvoLink console. |
| Resolution | 720p bills above 480p; take tier multipliers from the current console price, not assumptions. |
| Options | Do not assume audio, filters, or references are free — confirm option charges in the console. |
| Failures | Confirm failed-task billing behavior with a short live test before scaling. |
Keep the route price configurable and log actual usage. Do not hardcode an upstream rate as EvoLink billing.
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?
The EvoLink route is live; open EvoLink to see the current price for your workflow. Do not substitute the upstream official rate card for the EvoLink quote.
Q.02Why is there no fixed price calculator?
This independent page does not mirror a unit price without a published EvoLink rate-card value. Use the current console price and a short test job for an accurate production estimate.
Q.03What should agents do about pricing?
Read the current EvoLink price, keep it configurable, and ask the human to approve the projected spend before scaled traffic.
AGENT NOTECONTEXT
Agents should read /llms-full.txt and /openapi.json, use the live route, and ask the human to confirm the current EvoLink console price before scaled calls. Last fact update: /llms-full.txt · /openapi.json · 2026-08-07.