Short answer
Seedance 1.0 Pro may be worth shortlisting for short, multi-shot video workflows. AIMLAPI advertises 5–10-second, 1080p clips, text-to-video and image-to-video, and multi-shot continuity. These are claims about AIMLAPI’s offering—not confirmation of the same capabilities through TokenForge. Its displayed example requests 720p and does not demonstrate duration control or a complete image-input request. [AIMLAPI’s product page]
AIMLAPI’s image-to-video documentation currently displays a “Coming Soon” notice, even though it also describes a task-creation and result-retrieval workflow. That documentation does not, by itself, confirm that image-to-video access is operational. Confirm availability before planning a reference-guided pilot. TokenForge-specific access is also unconfirmed in its public Seedance guidance, which says to confirm availability, version, documentation, and terms. [AIMLAPI’s image-to-video documentation; TokenForge Seedance guidance]
What is verified about Seedance 1.0 Pro?
ByteDance’s official materials describe Seedance 1.0. The technical report associates that research model with the Volcano Engine model ID Doubao-Seedance-1.0-pro, but does not provide a Pro-versus-base feature comparison or specify how a third-party API serves it. [ByteDance Seedance page; technical report]
For Seedance 1.0, ByteDance reports text-to-video and image-to-video generation, multi-shot storytelling, and 1080p output. The technical paper reports 41.4 seconds to generate a five-second 1080p video on an NVIDIA L20. That is a hardware-specific research result—not a TokenForge latency estimate, hosted-service guarantee, or verified performance figure for every Pro API implementation. [ByteDance Seedance page; technical report]
| Evidence | What it supports | What it does not establish |
|---|---|---|
| ByteDance Seedance page and technical report | Seedance 1.0 capabilities and the reported Doubao-Seedance-1.0-pro model ID. |
A Pro-versus-base comparison, or TokenForge’s API behavior, limits, or service terms. |
| AIMLAPI Pro product page | AIMLAPI advertises a Seedance 1.0 Pro offering and describes its claimed capabilities. | TokenForge availability, pricing, identifiers, or request formats. |
| AIMLAPI image-to-video documentation | A “Coming Soon” notice and a described generation-task/result-retrieval flow. | That image-to-video access is currently operational. |
| TokenForge’s public Seedance guidance | TokenForge says to confirm availability, version, documentation, and terms. | That Seedance 1.0 Pro is enabled for your account or workload. |
Is it a fit for your video workflow?
AIMLAPI advertises 5–10-second, 1080p clips with text/image inputs and multi-shot continuity. On that description, it may be worth evaluating for short narrative clips where shot transitions matter. Treat reference-guided video as conditional: AIMLAPI’s product page advertises image-to-video, but its documentation still carries a “Coming Soon” notice despite describing a request and retrieval flow. Confirm that the image-to-video route is enabled before attempting a pilot. The advertised range is not a confirmed maximum or a TokenForge setting. AIMLAPI’s displayed example requests 720p; it does not show how to set clip duration or provide a complete image-input request. [AIMLAPI’s product page; image-to-video documentation]
If your workflow requires a single output longer than the advertised 5–10-second range, or a strict turnaround time, the supplied evidence is not enough to select it for that requirement. AIMLAPI’s page does not demonstrate longer-output controls or provide a latency benchmark. Separately, ByteDance’s 41.4-second result is for Seedance 1.0 on NVIDIA L20, not a hosted API timing commitment. Verify the exact Pro settings and measured turnaround with the provider you intend to use before relying on either. [AIMLAPI’s product page; Seedance technical report]
For a pilot, assess representative outputs for prompt adherence, motion stability, visual quality, and—when image-to-video access is confirmed—preservation of the reference subject and style. These dimensions appear in ByteDance’s Seedance 1.0 evaluation framework; they are useful evaluation criteria, not verified Pro results. [Seedance technical report]
Production API: confirm TokenForge details before coding
TokenForge’s public Seedance guidance says to confirm whether access is currently offered and which version is involved. Availability of Seedance 1.0 Pro through TokenForge remains unconfirmed in the information cited here. Do not use another provider’s endpoint or model ID as if it were TokenForge documentation. [TokenForge Seedance guidance]
Before integration, confirm for the specific model version and account:
- Availability and model ID: Is Seedance 1.0 Pro available, and what exact identifier should requests use?
- Endpoint and authentication: Which production endpoint and credential method apply?
- Input schemas: What are the complete text-to-video and image-to-video request formats, including how reference images are supplied?
- Job handling: Does generation return a completed result or an asynchronous job? If asynchronous, how do status checks, result retrieval, and timeouts work?
- Operational limits: What duration, resolution, aspect ratios, request limits, quotas, and concurrency rules are supported?
- Production terms: What availability, support, data-handling, retention, and usage terms apply?
Pricing and production trade-offs
The sources cited here do not establish a TokenForge price, billing unit, quota, or service-level commitment for Seedance 1.0 Pro. AIMLAPI’s pricing statements apply to its own offering; ByteDance’s hardware timing and claims about lower inference costs are not TokenForge customer prices or production guarantees. [AIMLAPI’s product page; TokenForge Seedance guidance]
For a cost estimate, obtain the applicable TokenForge rate and billing unit for the model version and output settings you plan to use. Confirm any retry or failed-job billing rules, and whether a subscription, minimum spend, or commitment applies. Keep API charges separate from any subscription charges; do not infer TokenForge terms from another provider’s pricing.
Bottom line
Shortlist Seedance 1.0 Pro for evaluation if short, multi-shot clips fit your workflow. For reference-guided clips, make any pilot conditional on confirming that the provider’s image-to-video route is operational; AIMLAPI’s documentation combines a “Coming Soon” notice with a described request flow, so access is not established by the documentation alone. Before a TokenForge production integration, confirm the exact version, availability, API contract, limits, and price. ByteDance’s research provides context for Seedance 1.0; AIMLAPI’s advertised Pro capabilities and example apply to AIMLAPI’s offering, not automatically to TokenForge.
Sources
Seedance 1.0: Exploring the Boundaries of Video Generation Models
Seedance 1.0 Pro API — AIMLAPI