Volcengine · VIDEO

Video Lip Sync API

Create video with Video Lip Sync.

Available through Sorceress API

Video Lip Sync model artwork

Using Video Lip Sync in your workflow

Sorceress brings Volcengine models into a shared API catalog. Select this model explicitly, check its supported inputs, and keep your API key on your server. Model capabilities differ; the schema and options on this page describe this entry rather than every model from the same brand.

  • Explore motion and scene concepts.
  • Automate video generation with a saved job that your application can track.

Pricing and availability

Cost scales with audio length. lite and basic cost the same. Charged only on success.. Successful work is billed in Sorceress credits. Defaults and optional inputs can affect the total.

Mode

lite (default)1099 credits

basic1099 credits

Inputs and supported options

videoUrlstring · required

https URL of the source video (MP4/MOV). Use file_upload publicUrl for a local clip.

audioUrlstring · required

https URL of the replacement voice clip. Max 180 seconds. Use speech_generate or file_upload.

modestring · optional

lite (default, faster frontal speaker) or basic (scene cuts / harder shots). Same price.

separateVocalboolean · optional

Split vocals from the driving audio before sync (default false).

openScenedetboolean · optional

basic mode only: detect scene cuts.

alignAudioboolean · optional

lite mode: loop the video if audio is longer (default true).

alignAudioReverseboolean · optional

lite mode: reverse-loop when alignAudio is true.

audioSecondsnumber · optional

Clip length in seconds (1–180). Optional — probed from audioUrl when omitted.

API request template

Replace placeholders and choose valid values from the input contract.

POST /api/v1/tools/lip_sync
Authorization: Bearer $SORCERESS_API_KEY
Content-Type: application/json

{
  "videoUrl": "<videoUrl>",
  "audioUrl": "<audioUrl>"
}
Read the endpoint reference →

Completion, results and billing

Save the job identifier returned by asynchronous requests and poll the jobs endpoint until the job succeeds or fails. Do not resubmit a generation just because it is still processing. Chat returns a completed reply and usage details. A multi-step workflow can include separately billed successful steps even if a later step fails. Keep returned asset links with your project, and consult each action for its output format.

Coding agents can discover the current catalog and input requirements from the Sorceress agent instructions. Use a Sorceress key; provider credentials stay on the server.