Public API
Pending
Not represented as generally callable.
Developer watch
Seedance 2.5 API
Model information and regional pricing are now public, but enterprise customers still cannot activate, test, or call Seedance 2.5. No catalog identifier is presented as a working API model.
Model cards
Published
China and global catalog information is visible.
Pricing
Published
Official regional token rates are documented.
Expected access
August 7
2026 estimate; not officially confirmed.
Current answer
What is actually known
Consumer access is live, and the Ark and ModelArk catalogs now publish Seedance 2.5 descriptions, examples, and pricing. The same first-party API documentation explicitly says Model Playground and API access will be available soon.
The China card slug doubao-seedance-2-5 and the global billing identifier dreamina-seedance-2-5-260628 describe published catalog and pricing records. They are not presented here as callable API model IDs while enterprise activation remains disabled.
Catalog visibility
Verified: model descriptions, examples, identifiers, and regional pricing are published.
Enterprise activation
Unavailable: enterprise customers can inspect the cards but cannot activate the model service.
Playground access
Unavailable: first-party documentation continues to describe Model Playground access as coming soon.
Production access
Pending: authentication, request fields, limits, errors, and a callable account workflow remain unverified.
Architecture
Prepare without guessing
You can design the application boundary now while leaving provider-specific values unset. Video generation should be modeled as a job rather than a synchronous text response.
- Keep provider, region, endpoint, and model ID in server-side configuration.
- Separate asset upload and validation from generation submission.
- Store a provider task ID and map provider states to your own job states.
- Support polling and webhooks without assuming either will launch first.
- Set per-user cost ceilings, concurrency limits, retries, and timeouts.
- Do not send keys, copyrighted references, or portrait assets from browser code.
Launch checklist
Verify before the first call
If the expected August 7 milestone is reached, first confirm it against first-party documentation. Then verify authentication, regional host, callable model identifier, request fields, accepted asset URLs, duration and resolution limits, output retention, moderation errors, cancellation, and billing.
A single successful playground result is not enough for production. Run a small test matrix covering text-only, image reference, rejected content, invalid assets, timeout behavior, duplicate submissions, and cost reporting.
API FAQ
Developer questions
Is the Seedance 2.5 API public?
No. Volcano Engine Ark and BytePlus ModelArk publish Seedance 2.5 model information and pricing, but first-party documentation says Playground and API access are coming soon. Enterprise customers cannot activate or call the model yet.
Why not publish an example request now?
The published card and billing identifiers are not proof of a callable model. A placeholder request can look runnable even when activation is disabled, so this page will add code only after first-party documentation publishes a verified Seedance 2.5 workflow.
Can I prepare my application before launch?
Yes. Keep the provider and model ID configurable, design video work as asynchronous jobs, validate uploaded assets separately, and add cost and retry limits before enabling production traffic.
When is enterprise API access expected?
Current launch information points to August 7, 2026, but that date is not confirmed in the first-party Ark or ModelArk documentation. Treat it as an expected milestone rather than a production deadline.
Will Ark console access guarantee API access?
No. The current rollout proves the distinction: model cards and prices are visible, while enterprise activation, Playground permission, and callable API access remain unavailable.
API alert
Get notified when a real endpoint is documented.
Pricing is already published. The alert now changes only when enterprise activation, Playground access, or a callable Seedance 2.5 API can be verified.