Asset Library

Asset Library operations use the LSF gateway and the tenant Bearer key. Access is scoped to the authorized library and media. No model, provider signing credentials or administrator routing fields are required.

8.1 Important Principles

• Asset Library requests use the Light Speed Future Bearer API key. Tenants do not need to implement provider-side credential signing.
• Asset Library requests do not require a model field. Routing, project selection, and backend authentication are handled by Light Speed Future automatically.
• Project routing fields are managed and injected by Light Speed Future on the backend. Tenants must not include project routing fields or similar project-related fields in API requests.
• If a request includes project-related fields, Light Speed Future may ignore, override, or reject them.
• CreateAsset is asynchronous. After upload, poll GetAsset or ListAssets. Only assets with Status=Active can be used for video generation.
• CreateAsset supports URL-based upload. Base64 upload is not supported.
• When an asset from the Asset Library is used for video generation, reference it in metadata.content as asset://asset-xxxxx.

8.2 Interface Groups

• Virtual asset library: for virtual character / virtual human assets.
• Real-human asset library: for real-human assets. Real-person verification must be completed before the asset can be used.

8.3 Virtual Asset Library Paths

• POST /v1/seedance/virtual/asset-groups/create
• POST /v1/seedance/virtual/asset-groups/list
• POST /v1/seedance/virtual/asset-groups/get
• POST /v1/seedance/virtual/asset-groups/update
• POST /v1/seedance/virtual/asset-groups/delete
• POST /v1/seedance/virtual/assets/create
• POST /v1/seedance/virtual/assets/list
• POST /v1/seedance/virtual/assets/get
• POST /v1/seedance/virtual/assets/update
• POST /v1/seedance/virtual/assets/delete

8.4 Real-Human Asset Library Paths

• POST /v1/seedance/real-human/validate-session/create
• POST /v1/seedance/real-human/validate-result/get
• POST /v1/seedance/real-human/asset-groups/list
• POST /v1/seedance/real-human/asset-groups/get
• POST /v1/seedance/real-human/asset-groups/update
• POST /v1/seedance/real-human/asset-groups/delete
• POST /v1/seedance/real-human/assets/create
• POST /v1/seedance/real-human/assets/list
• POST /v1/seedance/real-human/assets/get
• POST /v1/seedance/real-human/assets/update
• POST /v1/seedance/real-human/assets/delete

8.5 Typical Real-Human Workflow

1. Call validate-session/create to obtain H5Link and BytedToken.

2. Have the end user open the H5Link and complete real-person verification.

3. After verification succeeds, call validate-result/get to obtain GroupId.

4. Call assets/create to upload media under the verified group.

5. Poll GetAsset or ListAssets until Status=Active.

6. Reference the asset in /v1/videos via metadata.content using asset://asset-xxxxx.

8.6 Asset Library Examples

Example A: Start real-person verification

POST /v1/seedance/real-human/validate-session/create
{
  "CallbackURL": "https://example.com/callback"
}

Example B: Query real-person verification result

POST /v1/seedance/real-human/validate-result/get
{
  "BytedToken": "<YOUR_VERIFICATION_TOKEN>"
}

Example C: Upload an asset

POST /v1/seedance/real-human/assets/create
{
  "GroupId": "group-xxxxxxxx",
  "URL": "https://example.com/image.jpg",
  "AssetType": "Image",
  "Name": "real-human-look-1"
}

For detailed parameters, asset requirements, status polling, and error codes, refer directly to the official provider documentation for the relevant asset type.

8.7 Register and read a video asset

Use a virtual asset group already authorized for your account. A real-human asset uses the corresponding verified real-human workflow instead; do not move it into a virtual library to avoid verification.

POST /v1/seedance/virtual/assets/create
{
  "GroupId": "<YOUR_ASSET_GROUP_ID>",
  "URL": "https://example.com/reference-video.mp4",
  "AssetType": "Video",
  "Name": "reference-video"
}

Retain the returned asset identifier and query its status before generation:

POST /v1/seedance/virtual/assets/get
{
  "Id": "<YOUR_VIDEO_ASSET_ID>"
}

For an authorized real-human video asset, use POST /v1/seedance/real-human/assets/get with its Id. Use the matching library workflow and permissions, rather than assuming all asset paths are interchangeable.

Production can take asset:// directly in a video reference; customers do not need to fetch the temporary URL and probe it themselves. For a new direct-URL request, use a fresh access URL and keep it valid for the processing window.

Real-human rights and media reuse

Complete the required real-person verification and retain the necessary content rights. An enhanced video or extracted frame is not automatically verified as eligible original media for a later real-human verification flow. Check that use case with LSF before relying on it.