Seedance 2.5 API: Fewer Restrictions, More Creative Freedom

Seedance 2.5 Less Restriction is a distinct PiAPI task type for permitted projects that need more room for reference-guided creative direction. Its documented product distinction is support for verified face assets after Private Asset Library review, alongside the same Seedance 2.5 video workflow.

It is a product option, not a promise that every request will be accepted. PiAPI content policy, applicable law, and rights and consent requirements still apply. Start with the Seedance 2.5 API, then use the current Seedance 2.5 API documentation for the live request contract.

Standard and Less Restriction at a glance

The two options use the same hosted model family and request shape. Choose the task type that matches the project and keep the rest of the request grounded in the current schema.

"Less Restriction" describes the selected PiAPI task type. It does not promise universal acceptance, and all requests remain subject to review. Use the label to choose a workflow, then make the request specific, rights-cleared, and easy to inspect.

When this option is useful

The option is most useful when identity, references, and creative direction need to stay consistent across a planned scene. Examples include:

• a character-led short film using a rights-cleared face asset that has passed review;
• an editorial or fashion concept with mature themes that remains within policy;
• a branded or narrative scene where one character must keep the same identity across references;
• a multimodal storyboard that combines an image, a short video reference, an audio cue, and a precise prompt.

The controllable parts of the workflow matter more than a label: use material you have the right to use, describe each reference's role, choose a sensible duration and aspect ratio, and review the returned video before treating it as final.

Prepare access and references

Keep the setup in a short, repeatable sequence:

1. Create a PiAPI account and an API key.
2. Decide whether the project needs seedance-2.5 or seedance-2.5-less-restriction.
3. If the request uses a face reference, upload it through the Private Asset Library.
4. Wait until the asset status is Active, then retain the verified asset_id or asset:// reference required by the current guide.
5. Use rights-cleared material and keep the request within the PiAPI content policy.

The library handles an asynchronous lifecycle: an upload starts in Processing, then becomes Active or Failed. Managed assets are useful for a recurring cast or product subject. For a one-off reference, the current guide also documents ephemeral URL handling; read that guide for retention and quota details rather than copying an older limit into a new integration.

Use the playground, then the API

The Seedance 2.5 playground is a practical place to check a prompt, task type, resolution, and reference order. Once the inputs are clear, carry the same values into an asynchronous task request.

This is a request example using a reviewed face asset. It is a schema example, not a claim that this article ran a live generation.

curl --request POST "https://api.piapi.ai/api/v1/task" \
  --header "X-API-Key: $PIAPI_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "model": "seedance",
    "task_type": "seedance-2.5-less-restriction",
    "input": {
      "prompt": "The fictional lead in @image1 walks through a rain-lit gallery, pauses beside a blue sculpture, and turns toward the camera in one continuous cinematic shot.",
      "duration": 8,
      "resolution": "720p",
      "aspect_ratio": "16:9",
      "image_urls": ["asset://asset-REVIEWED-CHARACTER"]
    }
  }'

The top-level model is seedance, while task_type selects the 2.5 variant. The prompt names @image1 because the first supplied image is the character reference. The current documentation also supports @video1 and @audio1 when the corresponding arrays are supplied. A placeholder that has no matching reference is rejected, so keep the numbering aligned.

The response contains a task_id and a status such as Pending, Processing, Completed, or Failed. Poll GET /api/v1/task/{task_id} until the task reaches a terminal status, then retrieve the returned video URL promptly. For webhooks, use the current unified webhook documentation rather than inventing a callback field.

A prompt template for a controlled scene

Use a small reference pack and give every asset one job:

Create one continuous 8-second cinematic scene.
@image1 is the fictional lead character; preserve the face, dark jacket, and silver bag.
The setting is a quiet gallery after rain. Begin with a medium tracking shot, move to a
gentle front-facing close shot, and keep the lighting cool and consistent.
Show the character crossing the room, stopping beside the blue sculpture, and looking
toward the camera. No logos, captions, duplicate subjects, outfit changes, or random text.

Specificity makes the result easier to review. Name the subject, action, camera, lighting, and exclusions in that order. If the image reference has a different shape from the requested output, remember that the reference image's aspect ratio takes precedence under the current 2.5 contract.

Duration, resolution, and pricing

The current 2.5 API reference accepts any integer duration from 4 to 30 seconds, with 5 seconds as the default when omitted. It lists 480p, 720p, and 1080p output; 4K is not available. The supported aspect ratios are 21:9, 16:9, 9:16, 4:3, 1:1, and 3:4.

The Less Restriction task is billed per generated second. The following rates were read from the live 2.5 pricing section on September 8, 2026; check the current pricing page before budgeting a production.

For example, an 8-second 720p output has a base generation charge of 8 x $0.385 = $3.08 before any input-reference component. The pricing section describes video-reference input at half the selected unit rate, so a request with video references depends on both the output duration and the input video duration. Read the live contract for the exact calculation and current limits before sending a long reference.

How 2.5 differs from 2.0

Seedance 2.5 is the current subject here, with the dedicated seedance-2.5 and seedance-2.5-less-restriction task types, 4-30 second output, and 480p, 720p, or 1080p resolution. Seedance 2.0 remains available for existing integrations with its own task variants and limits. Task names, reference behavior, duration, and pricing are version-specific, so use the Seedance 2.0 API guide when maintaining a 2.0 integration instead of copying a 2.0 request into a 2.5 workflow.

Content policy and responsible use

Less Restriction gives a permitted project more creative room while retaining the rules that govern the hosted service. Before you send a request:

• use only references for which you have the necessary rights and consent;
• keep prompts and source media within the PiAPI content policy;
• describe the intended subject and action clearly so the result can be reviewed;
• treat a rejected request as a signal to revisit the brief and inputs rather than repeatedly resubmitting the same material.

The policy page owns the full list of restrictions and enforcement details. This article explains the workflow and task selection; it is not a replacement for that policy or for the live API contract.

FAQ

What is Seedance 2.5 Less Restriction?

It is the seedance-2.5-less-restriction PiAPI task type. Its documented distinction is support for generation with face assets after they pass Private Asset Library review. It still uses the Seedance 2.5 request schema and PiAPI content policy.

Does Less Restriction mean every prompt is accepted?

No. The task type provides more room for permitted reference-guided work, but each request and its references still need to satisfy PiAPI policy, applicable law, and rights requirements.

Do I need a reviewed face asset for every request?

You need a reviewed face asset when you use a face reference in this workflow. Text-only requests and other supported references follow the current 2.5 schema. Upload a face asset, wait for Active, and use the verified reference documented by the Private Asset Library guide.

Which task type should I send?

Use seedance-2.5 for the standard workflow or seedance-2.5-less-restriction when a permitted project needs that task type's broader creative path and reviewed face-reference support. Keep the model value as seedance.

What resolutions and durations are available?

The current 2.5 reference accepts integer durations from 4 through 30 seconds and lists 480p, 720p, and 1080p. It also lists six aspect ratios: 21:9, 16:9, 9:16, 4:3, 1:1, and 3:4.

How is Seedance 2.5 billed?

Billing is per generated second, based on task type and resolution. Video references add an input-duration component described in the live pricing section. See current PiAPI pricing before estimating a production run.

Where can I read the current content policy?

Read the PiAPI content policy. It is the source for policy scope and enforcement; the API documentation is the source for request fields, limits, and status behavior.

Start with a reviewed reference workflow

Choose a permitted scene, prepare a clear reference, and test the request in the Seedance 2.5 playground. When the inputs are ready, read the Seedance 2.5 API reference and send the same task type, prompt, references, duration, resolution, and aspect ratio through your application.

Source note: product fields, limits, task types, and rates were checked against the Seedance 2.5 configuration and live API reference on September 8, 2026. The draft does not claim a live generation, conversion lift, or universal acceptance rate.