Seedance 2.0 Mini API Status: Is It Available for Developers?
Seedance 2.0 Mini appears to be gaining attention because users are seeing or discussing lighter Seedance-style video generation inside ByteDance creative products such as Dreamina and Jianying/CapCut-related workflows. That is a useful launch signal. It is not the same thing as a published API model ID, a public pricing page, or an official route that developers can call in production.
Current status as of June 14, 2026
| Question | Current status | What EvoLink users should do |
|---|---|---|
| Is Seedance 2.0 Mini real? | Media and client-side signals suggest a Mini-style tier may exist or be rolling out in consumer creative apps | Track it as a serious upcoming route, but separate app access from API access |
| Is the public API live? | Not confirmed in the public sources reviewed for this article | Do not hard-code seedance-2.0-mini in production yet |
| Is there a confirmed model ID? | Not publicly confirmed | Wait for official API docs, provider console evidence, or EvoLink route confirmation |
| Is pricing available? | Not publicly confirmed | Do not build cost models from screenshots or secondary reports |
| Will EvoLink support it? | EvoLink is preparing to support it after API route, pricing, and limits are verified | Use this page as the status entry until the model page launches |
What is confirmed
On EvoLink, the confirmed production path is still the documented Seedance 2.0 family:
| Confirmed route family | Best current use | Why it matters while waiting for Mini |
|---|---|---|
| Seedance 2.0 | Higher-control video generation and reference-heavy workflows | Use it as the quality baseline |
| Seedance 2.0 Fast | Faster iteration and lower-latency draft workflows | Use it as the speed baseline |
| Seedance 1.5 Pro | Existing cinematic route with a simpler workflow | Keep it as a fallback when 2.0 controls are not required |
| Other EvoLink video models | Sora, Kling, Wan, Veo, HappyHorse, and other routes | Compare output quality and cost inside one API gateway |
This is enough to plan a launch-day evaluation. It is not enough to announce Seedance 2.0 Mini API availability.
What is not confirmed yet
The following details should stay out of production documentation until first-party or EvoLink-verified evidence exists:
- the final public API model ID
- whether the route is named
seedance-2.0-mini - text-to-video, image-to-video, reference-to-video, or editing support
- output duration, resolution, and audio behavior
- pricing unit and SKU
- queue behavior, concurrency, rate limits, and failed-task billing
- whether access is public, beta, allowlist, or region-limited
If those details appear in consumer app UI, media coverage, or social posts, treat them as demand signals. They still need API verification before they belong in a production integration guide.
Why Seedance 2.0 Mini matters
The search demand around Mini is logical. If ByteDance exposes a lighter Seedance tier for API users, developers will want to know whether it solves one of three jobs:
| Possible Mini job | What teams would measure | EvoLink routing implication |
|---|---|---|
| Lower-cost drafts | Cost per accepted clip and retry rate | Use Mini for rough cuts, then route premium clips to Seedance 2.0 |
| Faster iteration | Queue time and generation latency | Use Mini for prompt exploration and short-form ad variants |
| Higher throughput | Batch stability and failure behavior | Use Mini for scaled creative pipelines if quality is good enough |
This is exactly where a unified API gateway helps. If Seedance 2.0 Mini becomes available through EvoLink, teams should be able to compare it against Seedance 2.0 Fast and other video routes without changing authentication, billing, or the surrounding orchestration layer.
Seedance 2.0 Mini vs Seedance 2.0 Fast
Do not assume Mini and Fast are the same thing. A Fast version is usually a speed-oriented variant of a known model. A Mini tier, if officially exposed, may be optimized for cost, throughput, latency, smaller jobs, or a different product surface.
| Dimension | Seedance 2.0 Fast | Seedance 2.0 Mini |
|---|---|---|
| Public developer route | Available through current documented Seedance 2.0 Fast routes on EvoLink | Not yet confirmed as a public API route |
| Best current role | Faster Seedance 2.0 iteration | Watchlist route for lower-cost or lighter workflows |
| Pricing certainty | Use live EvoLink pricing once selecting the route | Not confirmed |
| Model ID certainty | Confirmed by current route configuration | Not confirmed |
| Production recommendation | Safe to evaluate now | Wait for API verification |
When Mini becomes verifiable, the most useful comparison will not be benchmark-only. It should compare accepted-output cost, latency, retry rate, and the quality difference between Mini, Fast, and standard Seedance 2.0.
What EvoLink will verify before launch
Before EvoLink treats Seedance 2.0 Mini as a production route, the team should verify:
- The exact API model ID.
- Supported modes: text-to-video, image-to-video, reference-to-video, editing, or another surface.
- Pricing and billing unit.
- Duration, resolution, aspect ratio, and audio limits.
- Queue behavior, retry behavior, and failed-task billing.
- Region or account restrictions.
- Whether the route should live on a dedicated model page or inside the Seedance 2.0 family page first.
That verification prevents a common launch mistake: publishing a model page that ranks for API terms before the API can actually be used.
What to use now
If your team needs a video API today, start from the available routes:
- Use Seedance 2.0 when reference control and output quality matter.
- Use Seedance 2.0 Fast when iteration speed matters more than maximum control.
- Use the Seedance model family page to compare Seedance routes.
- Keep Seedance 2.1 release watch on the radar if your roadmap depends on upcoming Seedance changes.
The safe production pattern is to build your video workflow around verified routes now, then add Mini as a controlled routing option once the API is confirmed.
Sources and verification notes
- ByteDance Seedance 2.0 official page
- Seedance 2.0 model card
- Volcengine ModelArk model documentation
- Volcengine Seedance 2.0 guide
Community posts, app UI reports, and media references are useful for demand monitoring. They are not used here as proof of public API availability, pricing, or model ID.
FAQ
Is Seedance 2.0 Mini API available now?
Is Seedance 2.0 Mini available in Dreamina or Jianying?
There are client-side and media signals suggesting a Mini-style Seedance experience may be visible in consumer creative products. That does not confirm public API access.
What is the Seedance 2.0 Mini model ID?
seedance-2.0-mini until the route is verified by official docs, provider console evidence, or EvoLink configuration.Will EvoLink support Seedance 2.0 Mini?
EvoLink plans to support Seedance 2.0 Mini after API route, pricing, and production limits are verified. Until then, this article tracks status rather than announcing availability.
Should I wait for Seedance 2.0 Mini before building video workflows?
No. Build against verified routes such as Seedance 2.0 or Seedance 2.0 Fast, then add Mini later as a routing option if it proves cheaper, faster, or useful for drafts.
Is Seedance 2.0 Mini cheaper than Seedance 2.0 Fast?
Pricing is not confirmed. A Mini name suggests a lighter tier, but production cost depends on listed price, failure rate, retry rate, output quality, and billing rules.
Is Seedance 2.0 Mini the same as Seedance 2.0 Fast?
Not confirmed. Fast is already part of the current Seedance 2.0 route structure. Mini may become a different tier, but its role should not be assumed before API documentation appears.
What should I monitor next?
Watch for an official API document, model ID, pricing table, route in provider consoles, or an EvoLink model page. Those are stronger signals than media mentions or app screenshots.
