Seedance 2.0 is ByteDance Seed’s standard model for multimodal audio-video creation. It combines text, images, videos and audio in a joint generation architecture, with separate creative workflows for reference-led scenes, video editing and video extension. It is useful when the brief needs both a coherent performance and specific visual or sonic information from prepared materials.
Images can define the subject’s appearance, the visual style and the composition. Video references can guide action, camera movement and effects. Audio can guide voice timbre, music or dialogue. Define the role of each material, then describe the scene that should result. The manufacturer emphasizes control over performance, lighting, shadows and camera language.
For a product story, prepare a product picture, a reference for the camera move and an audio cue. A brief might be: “Preserve the blue glass vase from Image 1. Use the slow sideways tracking movement from Video 1. The vase sits on a sunlit shelf, with soft instrumental music based on Audio 1.” The intended output is a newly staged scene that combines selected reference information.
Reference inputs can combine image and audio, image and video, video and audio, or all three. Audio-only input and text-plus-audio without image or video are not supported. Traditional text-to-video, first-frame generation and first-and-last-frame generation are also documented. If fixed opening and closing compositions are important, use the dedicated endpoint workflow: naming a reference image as an endpoint inside an omni-reference prompt is only an indirect way to guide it.
The model can replace a subject, add or remove objects, change elements and redraw or repair parts of a video. Describe the specific change and identify the source footage. For an addition, include appearance time and position; for a removal or replacement, state the object precisely and name what should remain.
For example: “Replace the desk lamp in Video 1 with the brass lamp in Image 1. Keep the camera movement, desk arrangement and lighting direction.” The desired result is an edited version of the scene with the intended substitution. Inspect the unchanged areas as well as the new object, particularly through occlusion, movement and shot changes.
Seedance 2.0 can extend a video forward or backward, and connect up to three supplied clips with generated transitions. Specify the temporal direction and the new event. For a bridge, order the clips and describe the transition between each pair, such as a camera entering a doorway in one shot and arriving in the next environment.
A straightforward extension typically returns the continuation developed around the source footage; include a clear instruction if the final result should also repeat the original segment. When completing a connection between two or three clips, the documented workflow can include both original material and new transition content. This is useful for developing an opening or ending, or connecting prepared scenes without leaving the joining action unspecified.
The standard edition documents MP4 at 24 fps and durations from 4 to 15 seconds. The output levels are 480p, 720p and 1080p with 8-bit color depth, plus 4K with 10-bit color depth. The supported ratios are 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16. Adaptive framing and automatic duration selection are also documented. The Fast edition has its own narrower 480p/720p output specification.
The 4K output uses H.265/HEVC encoding. Ten-bit encoding preserves additional tonal gradations and smoother color transitions, which matters for material with subtle light or color gradients. Check that the intended playback and editing environment can decode that format; some browsers and devices do not play it directly. A compatible container does not by itself ensure compatible video decoding.
The model can generate synchronized sound or a silent video, and it can return the last generated frame for a subsequent scene. Generated audio is mono. The 2.0 family does not support the separate two-stage Draft preview mode, so that preview feature should not be inferred from another Seedance edition.
The documented reference capacity is up to nine images, three videos and three audio clips. Direct reference-image or video uploads containing real human faces are not accepted in this documented producer profile; portrait work uses its supported portrait-asset workflow. Each video and audio clip must be 2–15 seconds long. All video references together must fit within 15 seconds, and all audio references together have their own 15-second total. Video files use MP4 or MOV at 24–60 fps, up to 200 MB each; audio files use WAV or MP3, up to 15 MB each. The listed image formats are JPEG, PNG, WebP, BMP, TIFF, GIF, HEIC and HEIF. Images must be smaller than 30 MB each, and the request body must not exceed 64 MB. In the documented reference-input profile, image width and height must each be strictly between 300 and 6,000 pixels, with a width-to-height ratio strictly between 0.4 and 2.5. Reference videos allow 300–6,000 pixels in each dimension and ratios of 0.4–2.5, inclusive, with 407,696–8,295,044 total pixels. MP4 or MOV videos use H.264/AVC or H.265/HEVC video and AAC or MP3 audio.
Order the files deliberately and refer to each by its media type and number: Image 1, Video 1 and Audio 1. The number follows the order among files of that type. Explain which traits to transfer and which source content should not define the new scene. Documented prompt languages include English, Spanish, Indonesian, Portuguese and Japanese. Keep the spoken language consistent within a dialogue; the guide advises against mixing languages except for proper names. For voice-guided work, separate the speaker, the exact line and the delivery direction.
Prepare first and last images with compatible framing. A mismatch between the input picture and the output dimensions can cause a crop or an abrupt visual change; matched dimensions and adaptive framing are documented remedies. Keep the description concentrated on the event and the reference roles. The manufacturer warns that long prompts can scatter information, causing details to be ignored. Review the resulting motion, reference continuity, audio performance and joins between scenes as distinct parts of the creative result.
For a complex scene, organize the brief as Shot 1, Shot 2 and Shot 3, specifying the camera, subject action, position and sound in order. The guide recommends one camera movement per shot and prioritizing slow, connected actions. Precise per-shot timestamps are unstable, so an event sequence is a better control than forcing several exact time windows.
The model also generates common text, including slogans, subtitles and speech bubbles. You can direct the text’s color, visual treatment, location and entrance. Use common characters rather than rare characters or special symbols, and review the wording as it moves. For subject references, clearly bind each asset to the intended character or object. Product viewpoints can supply different visual information; character-turnaround collages can confuse facial identity. A separate clear headshot and full-body image is the documented character-reference recommendation.
The guide documents unwanted subtitles, logos, duplicate characters and style drift. Clean source material, consistent labels and explicit constraints reduce those risks, but do not guarantee that unwanted text or duplicate figures disappear. More than four reference people is reported as a stability risk, distinct from the number of files the model accepts.
Video extension can create a jump or rollback at the join, and repeated continuations can compound image-quality degradation. Inspect the boundary frames and limit stacked extensions. A referenced voice can differ from the source timbre; narration may end with a click or abrupt cutoff, for which an audio fade is a documented remedy. Chinese polyphonic, uncommon or similarly shaped characters can be pronounced incorrectly. For a precise animated effect, such as a countdown, a motion reference is more informative than a verbal request alone. These are concrete reasons to check identity, text, motion and sound separately when selecting the clip.
", "aboutText": "Seedance 2.0 is ByteDance Seed’s standard model for multimodal audio-video creation. It combines text, images, videos and audio in a joint generation architecture, with separate creative workflows for reference-led scenes, video editing and video extension. It is useful when the brief needs both a coherent performance and specific visual or sonic information from prepared materials.\n\n### Multimodal reference and directorial control\n\nImages can define the subject’s appearance, the visual style and the composition. Video references can guide action, camera movement and effects. Audio can guide voice timbre, music or dialogue. Define the role of each material, then describe the scene that should result. The manufacturer emphasizes control over performance, lighting, shadows and camera language.\n\nFor a product story, prepare a product picture, a reference for the camera move and an audio cue. A brief might be: “Preserve the blue glass vase from Image 1. Use the slow sideways tracking movement from Video 1. The vase sits on a sunlit shelf, with soft instrumental music based on Audio 1.” The intended output is a newly staged scene that combines selected reference information.\n\nReference inputs can combine image and audio, image and video, video and audio, or all three. Audio-only input and text-plus-audio without image or video are not supported. Traditional text-to-video, first-frame generation and first-and-last-frame generation are also documented. If fixed opening and closing compositions are important, use the dedicated endpoint workflow: naming a reference image as an endpoint inside an omni-reference prompt is only an indirect way to guide it.\n\n### Editing footage\n\nThe model can replace a subject, add or remove objects, change elements and redraw or repair parts of a video. Describe the specific change and identify the source footage. For an addition, include appearance time and position; for a removal or replacement, state the object precisely and name what should remain.\n\nFor example: “Replace the desk lamp in Video 1 with the brass lamp in Image 1. Keep the camera movement, desk arrangement and lighting direction.” The desired result is an edited version of the scene with the intended substitution. Inspect the unchanged areas as well as the new object, particularly through occlusion, movement and shot changes.\n\n### Extending and connecting a sequence\n\nSeedance 2.0 can extend a video forward or backward, and connect up to three supplied clips with generated transitions. Specify the temporal direction and the new event. For a bridge, order the clips and describe the transition between each pair, such as a camera entering a doorway in one shot and arriving in the next environment.\n\nA straightforward extension typically returns the continuation developed around the source footage; include a clear instruction if the final result should also repeat the original segment. When completing a connection between two or three clips, the documented workflow can include both original material and new transition content. This is useful for developing an opening or ending, or connecting prepared scenes without leaving the joining action unspecified.\n\n### Standard-edition output and 4K\n\nThe standard edition documents MP4 at 24 fps and durations from 4 to 15 seconds. The output levels are 480p, 720p and 1080p with 8-bit color depth, plus 4K with 10-bit color depth. The supported ratios are 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16. Adaptive framing and automatic duration selection are also documented. The Fast edition has its own narrower 480p/720p output specification.\n\nThe 4K output uses H.265/HEVC encoding. Ten-bit encoding preserves additional tonal gradations and smoother color transitions, which matters for material with subtle light or color gradients. Check that the intended playback and editing environment can decode that format; some browsers and devices do not play it directly. A compatible container does not by itself ensure compatible video decoding.\n\nThe model can generate synchronized sound or a silent video, and it can return the last generated frame for a subsequent scene. Generated audio is mono. The 2.0 family does not support the separate two-stage Draft preview mode, so that preview feature should not be inferred from another Seedance edition.\n\n### Reference preparation and substantive limits\n\nThe documented reference capacity is up to nine images, three videos and three audio clips. Direct reference-image or video uploads containing real human faces are not accepted in this documented producer profile; portrait work uses its supported portrait-asset workflow. Each video and audio clip must be 2–15 seconds long. All video references together must fit within 15 seconds, and all audio references together have their own 15-second total. Video files use MP4 or MOV at 24–60 fps, up to 200 MB each; audio files use WAV or MP3, up to 15 MB each. The listed image formats are JPEG, PNG, WebP, BMP, TIFF, GIF, HEIC and HEIF. Images must be smaller than 30 MB each, and the request body must not exceed 64 MB. In the documented reference-input profile, image width and height must each be strictly between 300 and 6,000 pixels, with a width-to-height ratio strictly between 0.4 and 2.5. Reference videos allow 300–6,000 pixels in each dimension and ratios of 0.4–2.5, inclusive, with 407,696–8,295,044 total pixels. MP4 or MOV videos use H.264/AVC or H.265/HEVC video and AAC or MP3 audio.\n\nOrder the files deliberately and refer to each by its media type and number: Image 1, Video 1 and Audio 1. The number follows the order among files of that type. Explain which traits to transfer and which source content should not define the new scene. Documented prompt languages include English, Spanish, Indonesian, Portuguese and Japanese. Keep the spoken language consistent within a dialogue; the guide advises against mixing languages except for proper names. For voice-guided work, separate the speaker, the exact line and the delivery direction.\n\nPrepare first and last images with compatible framing. A mismatch between the input picture and the output dimensions can cause a crop or an abrupt visual change; matched dimensions and adaptive framing are documented remedies. Keep the description concentrated on the event and the reference roles. The manufacturer warns that long prompts can scatter information, causing details to be ignored. Review the resulting motion, reference continuity, audio performance and joins between scenes as distinct parts of the creative result.\n\n### Shot planning and text direction\n\nFor a complex scene, organize the brief as Shot 1, Shot 2 and Shot 3, specifying the camera, subject action, position and sound in order. The guide recommends one camera movement per shot and prioritizing slow, connected actions. Precise per-shot timestamps are unstable, so an event sequence is a better control than forcing several exact time windows.\n\nThe model also generates common text, including slogans, subtitles and speech bubbles. You can direct the text’s color, visual treatment, location and entrance. Use common characters rather than rare characters or special symbols, and review the wording as it moves. For subject references, clearly bind each asset to the intended character or object. Product viewpoints can supply different visual information; character-turnaround collages can confuse facial identity. A separate clear headshot and full-body image is the documented character-reference recommendation.\n\n### Behaviours to inspect before an edit\n\nThe guide documents unwanted subtitles, logos, duplicate characters and style drift. Clean source material, consistent labels and explicit constraints reduce those risks, but do not guarantee that unwanted text or duplicate figures disappear. More than four reference people is reported as a stability risk, distinct from the number of files the model accepts.\n\nVideo extension can create a jump or rollback at the join, and repeated continuations can compound image-quality degradation. Inspect the boundary frames and limit stacked extensions. A referenced voice can differ from the source timbre; narration may end with a click or abrupt cutoff, for which an audio fade is a documented remedy. Chinese polyphonic, uncommon or similarly shaped characters can be pronounced incorrectly. For a precise animated effect, such as a countdown, a motion reference is more informative than a verbal request alone. These are concrete reasons to check identity, text, motion and sound separately when selecting the clip.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "eb0cc62c16f491492e6e07cfafee04c12de4fc182bcf916a0a433eeacd6ea69c", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "bytedance/seedance-2.0ByteDance Seedance 2.0 combines native audio-video generation with image, video and sound references. Direct new scenes, edit existing footage or extend a sequence; the standard edition includes documented 1080p and 10-bit 4K output.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Seedance 2.0 is ByteDance Seed’s standard model for multimodal audio-video creation. It combines text, images, videos and audio in a joint generation architecture, with separate creative workflows for reference-led scenes, video editing and video extension. It is useful when the brief needs both a coherent performance and specific visual or sonic information from prepared materials.
Images can define the subject’s appearance, the visual style and the composition. Video references can guide action, camera movement and effects. Audio can guide voice timbre, music or dialogue. Define the role of each material, then describe the scene that should result. The manufacturer emphasizes control over performance, lighting, shadows and camera language.
For a product story, prepare a product picture, a reference for the camera move and an audio cue. A brief might be: “Preserve the blue glass vase from Image 1. Use the slow sideways tracking movement from Video 1. The vase sits on a sunlit shelf, with soft instrumental music based on Audio 1.” The intended output is a newly staged scene that combines selected reference information.
Reference inputs can combine image and audio, image and video, video and audio, or all three. Audio-only input and text-plus-audio without image or video are not supported. Traditional text-to-video, first-frame generation and first-and-last-frame generation are also documented. If fixed opening and closing compositions are important, use the dedicated endpoint workflow: naming a reference image as an endpoint inside an omni-reference prompt is only an indirect way to guide it.
The model can replace a subject, add or remove objects, change elements and redraw or repair parts of a video. Describe the specific change and identify the source footage. For an addition, include appearance time and position; for a removal or replacement, state the object precisely and name what should remain.
For example: “Replace the desk lamp in Video 1 with the brass lamp in Image 1. Keep the camera movement, desk arrangement and lighting direction.” The desired result is an edited version of the scene with the intended substitution. Inspect the unchanged areas as well as the new object, particularly through occlusion, movement and shot changes.
Seedance 2.0 can extend a video forward or backward, and connect up to three supplied clips with generated transitions. Specify the temporal direction and the new event. For a bridge, order the clips and describe the transition between each pair, such as a camera entering a doorway in one shot and arriving in the next environment.
A straightforward extension typically returns the continuation developed around the source footage; include a clear instruction if the final result should also repeat the original segment. When completing a connection between two or three clips, the documented workflow can include both original material and new transition content. This is useful for developing an opening or ending, or connecting prepared scenes without leaving the joining action unspecified.
The standard edition documents MP4 at 24 fps and durations from 4 to 15 seconds. The output levels are 480p, 720p and 1080p with 8-bit color depth, plus 4K with 10-bit color depth. The supported ratios are 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16. Adaptive framing and automatic duration selection are also documented. The Fast edition has its own narrower 480p/720p output specification.
The 4K output uses H.265/HEVC encoding. Ten-bit encoding preserves additional tonal gradations and smoother color transitions, which matters for material with subtle light or color gradients. Check that the intended playback and editing environment can decode that format; some browsers and devices do not play it directly. A compatible container does not by itself ensure compatible video decoding.
The model can generate synchronized sound or a silent video, and it can return the last generated frame for a subsequent scene. Generated audio is mono. The 2.0 family does not support the separate two-stage Draft preview mode, so that preview feature should not be inferred from another Seedance edition.
The documented reference capacity is up to nine images, three videos and three audio clips. Direct reference-image or video uploads containing real human faces are not accepted in this documented producer profile; portrait work uses its supported portrait-asset workflow. Each video and audio clip must be 2–15 seconds long. All video references together must fit within 15 seconds, and all audio references together have their own 15-second total. Video files use MP4 or MOV at 24–60 fps, up to 200 MB each; audio files use WAV or MP3, up to 15 MB each. The listed image formats are JPEG, PNG, WebP, BMP, TIFF, GIF, HEIC and HEIF. Images must be smaller than 30 MB each, and the request body must not exceed 64 MB. In the documented reference-input profile, image width and height must each be strictly between 300 and 6,000 pixels, with a width-to-height ratio strictly between 0.4 and 2.5. Reference videos allow 300–6,000 pixels in each dimension and ratios of 0.4–2.5, inclusive, with 407,696–8,295,044 total pixels. MP4 or MOV videos use H.264/AVC or H.265/HEVC video and AAC or MP3 audio.
Order the files deliberately and refer to each by its media type and number: Image 1, Video 1 and Audio 1. The number follows the order among files of that type. Explain which traits to transfer and which source content should not define the new scene. Documented prompt languages include English, Spanish, Indonesian, Portuguese and Japanese. Keep the spoken language consistent within a dialogue; the guide advises against mixing languages except for proper names. For voice-guided work, separate the speaker, the exact line and the delivery direction.
Prepare first and last images with compatible framing. A mismatch between the input picture and the output dimensions can cause a crop or an abrupt visual change; matched dimensions and adaptive framing are documented remedies. Keep the description concentrated on the event and the reference roles. The manufacturer warns that long prompts can scatter information, causing details to be ignored. Review the resulting motion, reference continuity, audio performance and joins between scenes as distinct parts of the creative result.
For a complex scene, organize the brief as Shot 1, Shot 2 and Shot 3, specifying the camera, subject action, position and sound in order. The guide recommends one camera movement per shot and prioritizing slow, connected actions. Precise per-shot timestamps are unstable, so an event sequence is a better control than forcing several exact time windows.
The model also generates common text, including slogans, subtitles and speech bubbles. You can direct the text’s color, visual treatment, location and entrance. Use common characters rather than rare characters or special symbols, and review the wording as it moves. For subject references, clearly bind each asset to the intended character or object. Product viewpoints can supply different visual information; character-turnaround collages can confuse facial identity. A separate clear headshot and full-body image is the documented character-reference recommendation.
The guide documents unwanted subtitles, logos, duplicate characters and style drift. Clean source material, consistent labels and explicit constraints reduce those risks, but do not guarantee that unwanted text or duplicate figures disappear. More than four reference people is reported as a stability risk, distinct from the number of files the model accepts.
Video extension can create a jump or rollback at the join, and repeated continuations can compound image-quality degradation. Inspect the boundary frames and limit stacked extensions. A referenced voice can differ from the source timbre; narration may end with a click or abrupt cutoff, for which an audio fade is a documented remedy. Chinese polyphonic, uncommon or similarly shaped characters can be pronounced incorrectly. For a precise animated effect, such as a countdown, a motion reference is more informative than a verbal request alone. These are concrete reasons to check identity, text, motion and sound separately when selecting the clip.
POST /v1/videostext, image, audiovideo| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits bytedance/seedance-2.0 | Default— |
Fieldprompt | Typestring | RequirementRequired | Values & limits | Default— |
Fieldduration | Typeinteger | RequirementRequired | Values & limits 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 Minimum: 1 Maximum: 600 | Default— |
Fieldresolution | Typestring | RequirementOptional | Values & limits 480p, 720p, 1080p, 4K | Default— |
Fieldaspect_ratio | Typestring | RequirementOptional | Values & limits 1:1, 3:4, 9:16, 4:3, 16:9, 21:9, 9:21 | Default— |
Fieldgenerate_audio | Typeboolean | RequirementOptional | Values & limits false, true Conditions: At 480p and 720p, omitting generate_audio selects the audio-enabled price and false selects the no-audio price. At 1080p and 4K, the resolution price applies to either setting. Check has_audio in the result for the returned audio track. | Default— |
Fieldframe_images | Typearray | RequirementOptional | Values & limits Minimum items: 1 Maximum items: 2 Input content: Array of frame objects. Each has type=image_url, image_url containing url and frame_type=first_frame or last_frame. Each role appears once at most. Use public HTTPS URLs. Exact keys: type, image_url, frame_type Conditions: These keys apply to each frame object. Omit frame_images for a text-only request. | Default— |
Fieldinput_references | Typearray | RequirementOptional | Values & limits Input content: Array of image or audio reference objects. Set type to image_url or audio_url, and supply the matching URL object containing url. Video references remain unpriceable. Conditions: Omit frame_images to use reference mode. Use public HTTPS URLs. | Default— |
Fieldsize | Typestring | RequirementOptional | Values & limits 480x480, 480x640, 480x854, 640x480, 854x480, 1120x480, 720x720, 720x960, 720x1280, 720x1680, 960x720, 1280x720, 1680x720, 1080x1080, 1080x1440, 1080x1920, 1440x1080, 1920x1080, 2520x1080, 3840x2160, 2160x3840, 2160x2160, 2880x2160, 2160x2880, 5040x2160 Pattern: ^[1-9][0-9]*x[1-9][0-9]*$ | Default— |
Fieldseed | Typeinteger | RequirementOptional | Values & limits Minimum: -9,223,372,036,854,775,808 Maximum: 9,223,372,036,854,775,807 | Default— |
Fieldcallback_url | Typestring | RequirementOptional | Values & limits Pattern: ^https:// | Default— |
Fieldsession_id | Typestring | RequirementOptional | Values & limits | Default— |
Fieldtrace | Typeobject | RequirementOptional | Values & limits | Default— |
Fielduser | Typestring | RequirementOptional | Values & limits | Default— |
Text to video · A written prompt. · Required: model, prompt, duration
Provide a text prompt and a supported whole-second duration. Use an exact listed size, or a resolution and aspect ratio that resolve to listed dimensions.
model: Type: string · bytedance/seedance-2.0
prompt: Type: string · Maximum UTF-8 bytes: 10,000 · Non-whitespace required: Yes
Image to video · A written prompt and a frame image. · Required: model, prompt, duration, frame_images
frame_images is an array of objects with type=image_url, image_url containing url, and frame_type. Use a public HTTPS image URL; first_frame and last_frame may each appear once. Use a listed output size or compatible dimensions. Do not add video references.
Exact keys: type, image_url, frame_type
model: Type: string · bytedance/seedance-2.0
prompt: Type: string · Maximum UTF-8 bytes: 10,000 · Non-whitespace required: Yes
Reference to video · A written prompt and image or audio references. · Required: model, prompt, duration, input_references
input_references is an array. Each object has type=image_url or type=audio_url and a matching URL object containing url. Use public HTTPS links. Omit frame_images to select reference mode. Video references cannot be priced.
model: Type: string · bytedance/seedance-2.0
prompt: Type: string · Maximum UTF-8 bytes: 10,000 · Non-whitespace required: Yes
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, prompt, duration |
Parametermaterial_types | Contracttext, image, audio |
Parameteradditional_properties | Contractfalse |
Parameteroptional_controls | Contractresolution, aspect_ratio, generate_audio, frame_images, input_references, size, seed, callback_url, session_id, trace, user |
Lifecycle: submit_once_poll_original
GET /v1/videos/{public_id}
GET /v1/videos/{public_id}/content
The displayed rates estimate the cost before generation. The final charge is calculated from the cost recorded for the original generation. Measured output duration and forecast quantities are not the final billable quantity.
Tariff references do not add request options. Supported parameters are listed for the selected method.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Rate schedule | Forecast quantity | Billing unit | Billing conditions | Charge |
|---|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Forecast quantity— | Billing unit— | Billing conditions— | Charge Input · Input tokens · Estimate for comparison only — / 1K tokens Output · Output tokens · Estimate for comparison only — / 1K tokens Input · Cache read · Estimate for comparison only — / 1K tokens Input · Cache write · Estimate for comparison only — / 1K tokens Input · Cache write, 1 hour · Estimate for comparison only — / 1K tokens |
| ConfigurationVideo-token price | Rate schedule— | Forecast quantity— | Billing unitper 1,000 video tokens | Billing conditionsNo additional condition is declared in this pricing key. | Charge Output · Video-token price · Estimate for comparison only $0.014 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Rate schedule— | Forecast quantity— | Billing unitper 1,000 video tokens | Billing conditionsresolution: 1080p | Charge Output · Video-token price · Estimate for comparison only $0.0154 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Rate schedule— | Forecast quantity— | Billing unitper 1,000 video tokens | Billing conditionsinput: with_video_input; resolution: 1080p | Charge reference · Video-token price · Estimate for comparison only $0.0094 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Rate schedule— | Forecast quantity— | Billing unitper 1,000 video tokens | Billing conditionsresolution: 4k | Charge Output · Video-token price · Estimate for comparison only $0.008 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Rate schedule— | Forecast quantity— | Billing unitper 1,000 video tokens | Billing conditionsinput: with_video_input; resolution: 4k | Charge reference · Video-token price · Estimate for comparison only $0.0048 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Rate schedule— | Forecast quantity— | Billing unitper 1,000 video tokens | Billing conditionsinput: with_video_input | Charge reference · Video-token price · Estimate for comparison only $0.0086 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Rate schedule— | Forecast quantity— | Billing unitper 1,000 video tokens | Billing conditionsaudio: without_audio | Charge Output · Video-token price · Estimate for comparison only $0.014 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationEstimated generation cost | Rate schedule— | Forecast quantityone generation estimate | Billing unit— | Billing conditions— | Charge Output · Estimated generation cost · Estimate for comparison only $0.3024 estimate before generation This estimate is not an additional charge or a fixed rate for the completed generation. |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
Model-level reference schedules do not change method selection, quotes or charges. Active charges use the selected Ailoot method rates.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Billing conditions | Charge |
|---|---|---|
| ConfigurationVideo-token price | Billing conditionsNo additional condition is declared in this pricing key. | Charge Output · Video-token price $0.014 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Billing conditionsresolution: 4k | Charge Output · Video-token price $0.008 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Billing conditionsresolution: 1080p | Charge Output · Video-token price $0.0154 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Billing conditionsaudio: without_audio | Charge Output · Video-token price $0.014 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Billing conditionsinput: with_video_input | Charge reference · Video-token price $0.0086 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Billing conditionsinput: with_video_input; resolution: 4k | Charge reference · Video-token price $0.0048 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
| ConfigurationVideo-token price | Billing conditionsinput: with_video_input; resolution: 1080p | Charge reference · Video-token price $0.0094 per 1,000 video tokens The video-token rate is the primary price reference. Per-second headline estimates are separate references, not an extra charge. |
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\npython3 - <<'PY_REQUEST'\nfrom pathlib import Path\nPath('request.json').write_text('{"model":"bytedance/seedance-2.0","prompt":"A serene mountain landscape at sunset","duration":4,"resolution":"480p","size":"480x480","generate_audio":false}', encoding='utf-8')\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/videos \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\npython3 - <<'PY_RESULT'\nimport json\nfrom pathlib import Path\nr=json.loads(Path('result.json').read_text())\nprint(json.dumps(r,ensure_ascii=False,indent=2))\nprint('Keep the complete JSON and response headers; do not resubmit an unknown creation.')\nPY_RESULT\nsigned owned content URLs
GET /v1/videos/{public_id}GET /v1/videos/{public_id}/contentset -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\npython3 - <<'PY_STATUS_URL'\nimport json\nfrom pathlib import Path\nfrom urllib.parse import quote\nr=json.loads(Path('result.json').read_text())\nif not isinstance(r.get('id'),str) or not r['id']:raise SystemExit('Keep the original response and headers for reconciliation; no returned ID')\nPath('status-url.txt').write_text('https://api.ailoot.ai/v1/videos/'+quote(r['id'],safe=''))\nPY_STATUS_URL\ncurl --fail-with-body --silent --show-error "$(cat status-url.txt)" \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -D status-headers.txt -o status.json\npython3 - <<'PY_RESULT'\nimport json\nfrom pathlib import Path\nr=json.loads(Path('status.json').read_text())\nprint(json.dumps(r,ensure_ascii=False,indent=2))\nprint('Keep the complete JSON and response headers; do not resubmit an unknown creation.')\nPY_RESULT\nset -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\nexport AILOOT_API_KEY\npython3 - <<'PY_ASSETS'\nimport json,os,subprocess\nfrom pathlib import Path\nfrom urllib.parse import urljoin,urlsplit\nr=json.loads(Path('status.json').read_text())\nif r.get('status')!='completed':raise SystemExit('Keep the original ID and read its status; never recreate an unknown job')\nif not isinstance(r.get('data'),list) or not r['data']:raise SystemExit('Keep the complete original status; no completed outputs supplied')\nurls=[]\nfor i,u in enumerate(r.get('data',[])):\n if not isinstance(u,str):raise SystemExit('Keep the original response; unexpected asset shape')\n urls.append((str(i),u))\nfor label,path in urls:\n u=urljoin('https://api.ailoot.ai',path);z=urlsplit(u)\n if z.scheme!='https' or z.netloc!='api.ailoot.ai' or z.username or z.password:raise SystemExit('Use the actual returned Ailoot owned content URL')\n target=Path('owned-'+label+'.bin')\n subprocess.run(['curl','--fail-with-body','--silent','--show-error',u,'-H','Authorization: Bearer '+os.environ['AILOOT_API_KEY'],'-D',str(target)+'.headers','-o',str(target)],check=True)\nprint('All returned owned URLs saved; complete metadata, timing and usage remain in the JSON.')\nPY_ASSETS\nSave every completed video or returned file; retrieve every actual returned asset URL.
Keep every actual owned output and its returned measured metadata.
503 result_pending_check + originalid + X-Should-Retry:false; never replay original
| Field | Type | Meaning |
|---|---|---|
Fieldindex | Typeinteger | MeaningZero-based position of this video in the outputs list. |
Fieldcontent_url | Typestring | MeaningSigned HTTPS download URL for this completed video. |
Fieldsha256 | Typestring | null | MeaningSHA-256 digest of the original video bytes; null if unavailable. |
Fieldsize_bytes | Typeinteger | null | MeaningSize of the original video file in bytes; null if unavailable. |
Fieldduration_ms | Typeinteger | null | MeaningMeasured video duration in milliseconds; null if unavailable. |
Fieldwidth | Typeinteger | null | MeaningVideo width in pixels; null if unavailable. |
Fieldheight | Typeinteger | null | MeaningVideo height in pixels; null if unavailable. |
Fieldvideo_codec | Typestring | null | MeaningVideo codec identifier; null if not recorded. |
Fieldhas_audio | Typeboolean | null | MeaningWhether the video contains an audio track; null if not measured. |
Fieldaudio_codec | Typestring | null | MeaningAudio codec identifier; null when no identifier is recorded. |
| Response | Condition | Next step |
|---|---|---|
Response404 · not_found_error | ConditionVideo access is unavailable, or this video ID was not found. | Next stepCheck video access. For an existing video, use its original public ID and the same API key. |
Response401 · authentication_error | ConditionThe API key does not match the authenticated account. | Next stepCheck your API key and account access before submitting. |
Response400 · invalid_request_error | ConditionThe request could not be read, or the download index is invalid. | Next stepCorrect the request body. For a download, choose an output index returned by the original task. |
Response422 · price_unavailable | ConditionThe selected video configuration cannot be priced. | Next stepChoose a supported video configuration and complete its required options before submitting a corrected request. |
Response422 · invalid_request_error | ConditionA video input or original continuation task is invalid. | Next stepUse valid HTTPS inputs. For continuation, use your completed original public video ID with the same API key. |
Response402 · billing_error | ConditionThe available balance or limits do not allow a reservation. | Next stepCheck your available balance and limits before sending a new request. |
Response503 · server_error | ConditionVideo verification, storage or service access is temporarily unavailable. | Next stepWait for service availability. If you already have a video ID, check that original task instead of creating another generation. |
Response503 · result_pending_check | ConditionThe original video result and charge need checking. | Next stepKeep the returned video ID and check that task. Do not send a replacement generation request while it is being checked. |
Response503 · owned_result_unavailable | ConditionThe existing video download is temporarily unavailable. | Next stepCheck the same video task later and download its existing output. A new generation creates a separate operation. |
Response409 · video_not_ready | ConditionThe video content has not been published. | Next stepCheck the original task status. Download after it reports completed; if it reports failed, follow its charge-check notice. |
Ailoot Ultra bytedance/seedance-2.0
Use the method paths shown above.