LSF Seedance2.5 Production

Production · availability by tenant

LSF Seedance2.5 Production is deployed. Use the exact Production alias and output combinations enabled for your tenant; native-generation or standalone-enhancement access does not automatically grant Production access.

Submit one request to create a finished video with Seedance 2.5 creative controls and your selected Production tier. Optionally request a JPG last frame from the final result. The customer receives one public task and one final charge.

7.1 Product selection and outputs

Select Lite, Standard or Pro through model, not tool_version. Final named resolutions are 1080p, 2k and 4k when enabled. Final video format is MP4. Arbitrary resolution_limit, MOV, 6K and 8K are outside this Production contract.

7.2 Request fields

Keep output and generation controls inside metadata. Top-level mode is rejected. Do not send generic task_type, standalone metadata.video_url, customer-supplied duration measurements for input references, provider credentials, callbacks or routing fields. Video references belong in metadata.content.

The inherited reference limits are 30 images, 10 videos, 10 audio items and 50 total. Preserve item order for references such as @Image1, @Video1 and @Audio1. Editing requires a 4–30 second reference video; frame/edit/extend aspect ratio must remain adaptive.

7.3 Example A · Standard text to enhanced 1080p

POST /v1/videos
{
  "model": "<YOUR_PRODUCTION_STANDARD_MODEL_ALIAS>",
  "prompt": "A ceramic cup on a desk in soft daylight. The camera is still.",
  "metadata": {
    "duration": 5,
    "resolution": "1080p",
    "fps": 24,
    "scene": "common",
    "generate_audio": false,
    "return_last_frame": false,
    "client_request_id": "production-standard-001"
  }
}

A successfully accepted Production request returns HTTP 202. Save its public task identifier. Do not create a second enhancement request: the backend starts that stage automatically.

{
  "id": "<YOUR_TASK_ID>",
  "task_id": "<YOUR_TASK_ID>",
  "status": "queued"
}

This is a selected-field response illustration, not an exhaustive response schema. Query GET /v1/videos/{task_id} with the task-owning API key until the public task reaches a terminal state.

7.4 Example B · Lite 2K with an HTTPS video reference

POST /v1/videos
{
  "model": "<YOUR_PRODUCTION_LITE_MODEL_ALIAS>",
  "prompt": "Use @Video1 as a motion reference for a new product scene.",
  "metadata": {
    "duration": 5,
    "resolution": "2k",
    "fps": 60,
    "generate_audio": false,
    "content": [
      {
        "type": "video_url",
        "role": "reference_video",
        "video_url": {
          "url": "https://example.com/reference-video.mp4"
        }
      }
    ],
    "return_last_frame": false,
    "client_request_id": "production-lite-reference-001"
  }
}

metadata.duration requests the output duration; it is not the input-video duration. LSF validates the input video and measures its duration before the initial reservation.

7.5 Video URLs, assets and measured input duration

Provide URLs that remain accessible long enough for validation and processing. Private or loopback destinations, unsafe redirects and unsupported or unstable media access are rejected. Validation may require byte-range access; a server that cannot provide consistent media metadata may be unsuitable.

LSF’s measured input duration is the basis for this retail workflow. It is not a supplier-reported billed-input-seconds value. Customers do not submit a trusted Tin field or configure a media probe.

7.6 Example C · Pro 4K, asset video and enhanced last frame

POST /v1/videos
{
  "model": "<YOUR_PRODUCTION_PRO_MODEL_ALIAS>",
  "prompt": "Use @Video1 as a reference for smooth camera motion and lighting.",
  "metadata": {
    "duration": 5,
    "resolution": "4k",
    "fps": 24,
    "generate_audio": false,
    "content": [
      {
        "type": "video_url",
        "role": "reference_video",
        "video_url": {
          "url": "asset://<YOUR_VIDEO_ASSET_ID>"
        }
      }
    ],
    "return_last_frame": true,
    "client_request_id": "production-pro-asset-001"
  }
}

Do not include scene in a Pro request. Use only an asset ID that is authorized and Active. Virtual and real-human asset creation and verification remain distinct workflows; a real-human asset does not bypass its verification requirements.

Last-frame behavior

• return_last_frame=true is an output request. The JPG comes from the final delivered video.
• An input content item with role=last_frame is a generation constraint. It does not request extraction of the delivered video’s last frame.
• The requested outputs belong to the same public task. Do not submit a separate frame-extraction request or bill its internal stage as a second customer job.
• Use the returned last-frame URL only when present on a successful result, and store it promptly if it is needed for subsequent work.
• Reusing a frame in another request does not automatically create a documented parent/child work relationship or prove its original-media provenance. Maintain any application lineage in your own system.

7.7 Results and progress

GET observes the public workflow; it is not needed to trigger the next internal stage. Continue polling the original task through nonterminal states. A completed Production result is the final enhanced MP4 and, when requested and returned, the enhanced-result JPG.

Result URLs are temporary

Copy delivered video and image files into customer-controlled storage. The intermediate generation output is not the Production deliverable. A successful final video URL must not be replaced by an intermediate URL after a later error.

7.8 Pricing, reservation and reconciliation

Use the agreed tenant rate for the selected Production tier, resolution and input mode. The rate already reflects the tenant’s commercial terms. The current Production model does not apply an FPS multiplier.

A still image, a first/last-frame image or an audio-only reference does not by itself activate video-input pricing. Reference video, editing, extension and mixed inputs containing video do. Use the video-input rate for the same tier and resolution, not a rate from another tier.

Worked duration examples — no price quotation

At submission, LSF reserves an estimate using the requested / estimated output duration and validated video-input duration. If output duration is automatic, the estimate can be conservative. The final enhanced duration can exceed the requested value; the reservation is not a spending cap.

The accepted task freezes its applicable rate and input information. Terminal reconciliation settles the final amount once and refunds or collects the difference from the reservation as applicable. Repeated GET or an accepted identical replay does not create duplicate financial operations. Display rounding is not a substitute for the final balance or invoice record.

A Production job has one final customer charge, including the requested last-frame output. Failed tasks and uncertain outcomes must be reconciled against the original task; an unknown outcome is not proof that a refund is due or that no processing occurred.

7.9 Request rejection and safe recovery