Seedance asset:// ids vs Sume reference URLs

On BytePlus ModelArk you pass asset://<asset ID> in the content URL parameter to use a preset digital character or an authorized real-person asset. That scheme is a ModelArk concept tied to its asset library. A Sume request has no asset:// field: references go in input_references as image_url objects with a URL.

BytePlus details are from its portrait-videos page, read 2026-10-01; Sume details from the Video generation docs.

What does asset:// do on ModelArk?

The page describes two uses. Preset digital characters: each asset in the digital characters library has its own asset ID, which you pass as asset://<asset ID> to control a realistic-style character's look. Authorized real-person assets: after real-person verification and authorization, assets such as the person's image, video, and audio are added to the repository and each gets an asset ID used the same way.

What does a Sume reference look like?

A reference entry has "type": "image_url" and an image_url object holding the URL. Fields that take URLs such as callback_url must be HTTPS. Reference types are checked per model: only models whose supported_input_references lists a type accept it.

{
  "model": "seedance-2",
  "prompt": "A colossal solar flare beside a planet",
  "input_references": [
    {
      "type": "image_url",
      "image_url": { "url": "https://example.com/character-sheet.png" }
    }
  ],
  "resolution": "1080p"
}

How do I port a ModelArk character workflow?

Export or generate the character image you want, host it at an HTTPS URL, and send that URL as the reference. Consistency across shots comes from reusing the same reference image, not an id. The authorization step for a real person is part of BytePlus's asset library; the Sume docs I read do not describe an equivalent, so keep real-person consent on your side. For mapping other fields see fal Seedance 2.0 to Sume request mapping.