Seedance 2.0 is a video generation model from ByteDance. It supports text-to-video, image-to-video with first and last frame control, and multimodal reference-to-video. It is particularly strong at preserving character consistency,...
Endpoints:
1
Context:
0
Input:
text, image
Output:
video
Visual comparison
Endpoint pricing chart
Compare published endpoint pricing visually.
Effective price by endpoint
USD per generation for video tokens. Lower is better.
Only directly comparable published units are charted.
Server-rendered comparison
Provider endpoints
Video prices use OpenRouter’s dedicated pricing SKUs, including resolution-specific per-second units. Missing speed data never removes an endpoint.
$0.000007 per generation (video tokens without audio)
Speed measurements
500-token response
Not applicable
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Uptime (30 min)
Insufficient recent data
Context
0
Model format
unknown
Max output
N/a
1 parameters
frequency_penalty
Endpoint data fetched .
Seedance 2.0 deployment guide
How to choose a Seedance 2.0 inference provider
Seedance 2.0 is indexed here as a video model by ByteDance, with 1 provider endpoint from Seed. The comparison preserves each exact OpenRouter routing tag so pricing and performance observations can be connected to the route an application would actually request.
Match the endpoint to the workload
The model publishes a 0-token context window. It accepts text, image input and returns video output. 1 distinct supported parameters appear across the listed routes. Confirm limits on the specific endpoint rather than assuming every host exposes the same configuration.
Compare video billing units directly
At least one generation is published consistently across the listed endpoints, allowing a direct price chart for video tokens. Other charges remain in the table using OpenRouter’s exact billing labels.
Verify route format and availability
Published endpoint formats include unknown. Availability, rate limits, and regional support can change independently of catalog pricing, so confirm the selected routing tag before production deployment.