Sync Lipsync
sync/lipsync/v2/proLipsync V2 Pro by Sync Labs - AI-powered video editing and transformation. Apply style transfer, motion control, lip-sync, and visual effects to existing videos with natural language instructions.
- Base price
- $5 / run
- Execution
- async
- Model type
- image
- Input fields
- 2
Try the model
Playground
Your output will appear here
Complete the inputs, then click Run.
Specifications
Pricing
- Base price
- $5 / run
Context & modalities
- Input
- Schema-defined
- Output
- image
Capabilities
- Chat
- Not supported
- Vision
- Not supported
- Reasoning
- Not supported
- Structured output
- Not supported
- Function calling
- Not supported
- Audio input
- Not supported
Access
- Provider
- Sync Labs
- Model ID
- sync/lipsync/v2/pro
- Execution
- async
- API
- Unified Run API
- Endpoint
- /v1/run
API README
Sync Lipsync
Sync Lipsync occupies a clearly bounded position in a image production pipeline under the route sync/lipsync/v2/pro. It is best evaluated as a named workflow endpoint rather than as a generic substitute for neighboring versions: planners can assign the route to a specific brief, record the chosen revision, and keep approval history tied to one predictable integration surface from intake through delivery.
A practical rollout of Sync Lipsync should begin with source-readiness checks, ownership of the submitted material, an agreed budget, and a written definition of the final pro deliverable. Before automation is enabled, the acceptance pass should verify that the returned asset opens correctly, fits the intended downstream toolchain, satisfies the project’s review criteria, and can be reproduced from the stored request and route identity sync/lipsync/v2/pro.
Highlights
- Distinct output behavior. For Sync Lipsync, for Sync Lipsync, visual effects to existing videos with natural language instructions In Sync Lipsync, this capability is applied through the exact sync/lipsync/v2/pro workflow with audio as a relevant request control; the audio control exposes the corresponding choice in this route; the audio control exposes the corresponding choice in this route.
- Creative control. For Sync Lipsync, for Sync Lipsync, video to video In Sync Lipsync, this capability is applied through the exact sync/lipsync/v2/pro workflow with video as a relevant request control; the video control exposes the corresponding choice in this route; the video control exposes the corresponding choice in this route.
- Workflow fit. For Sync Lipsync, for Sync Lipsync, uRL of the input audio In Sync Lipsync, this capability is applied through the exact sync/lipsync/v2/pro workflow.
- Production detail. For Sync Lipsync, for Sync Lipsync, uRL of the input video In Sync Lipsync, this capability is applied through the exact sync/lipsync/v2/pro workflow.
Pricing
| Configuration | Price |
|---|---|
| Per request | $5 |
When to Use
| Scenario | Why this model fits |
|---|---|
| Choose Sync Lipsync | Use it when the required deliverable is specifically the image result documented for sync/lipsync/v2/pro. |
| Match the source material | Select this route when your inputs naturally map to audio, video. |
| Use its distinguishing capability | For Sync Lipsync, visual effects to existing videos with natural language instructions In Sync Lipsync, this capability is applied through the exact sync/lipsync/v2/pro workflow with audio as a relevant request control; the audio control exposes the corresponding choice in this route |
| Plan repeatable production | For Sync Lipsync, video to video In Sync Lipsync, this capability is applied through the exact sync/lipsync/v2/pro workflow with video as a relevant request control; the video control exposes the corresponding choice in this route |
| Confirm cost and delivery | Use the pricing combinations below and the output contract above when budgeting or automating Sync Lipsync jobs. |
Prompt Guide
Build the request around the exact sync/lipsync/v2/pro schema. Start with required fields, then add only the controls needed for the intended output; keep URLs reachable and enum values exactly as shown in Technical Specs.
{
"audio": "https://static.sandbase.ai/examples/sync/lipsync/v2/pro/input_audio_1.mp3",
"video": "https://static.sandbase.ai/examples/sync/lipsync/v2/pro/input_video_0.mp4"
}
Technical Specs
| Specification | Value |
|---|---|
| Model ID | sync/lipsync/v2/pro |
| Execution mode | async |
| Required inputs | None marked required |
| Request fields | audio (string, optional); video (string, optional) |
| Output | url (string); content_type (string) |
Related Models
Start building
Send your first request
OpenAI-compatible endpoint with unified authentication and usage tracking.
# Preserve Unicode and shell metacharacters in the request body.
result=$(printf '%s' 'ewogICJtb2RlbCI6ICJzeW5jL2xpcHN5bmMvdjIvcHJvIiwKICAiYXVkaW8iOiAiaHR0cHM6Ly9zdGF0aWMuc2FuZGJhc2UuYWkvZXhhbXBsZXMvc3luYy9saXBzeW5jL3YyL3Byby9pbnB1dF9hdWRpb18xLm1wMyIsCiAgInZpZGVvIjogImh0dHBzOi8vc3RhdGljLnNhbmRiYXNlLmFpL2V4YW1wbGVzL3N5bmMvbGlwc3luYy92Mi9wcm8vaW5wdXRfdmlkZW9fMC5tcDQiCn0=' \
| base64 --decode \
| curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/run" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @-)
run_id=$(printf '%s' "$result" | jq -r .id)
for attempt in $(seq 1 120); do
status=$(printf '%s' "$result" | jq -r .status)
case "$status" in completed|failed|timeout) break ;; esac
sleep 2
result=$(curl --fail-with-body --silent \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
"https://api.sandbase.ai/v1/run/$run_id")
done
status=$(printf '%s' "$result" | jq -r .status)
[ "$status" = completed ] || { echo "Generation ended: $status" >&2; exit 1; }
printf '%s\n' "$result"Choose your model
Compare models
| Model | Context | Input / 1M | Output / 1M | Released |
|---|---|---|---|---|
Sync LipsyncThis model Sync Labs | — | — | — | Sep 2, 2025 |
Sync Labs | — | — | — | Apr 1, 2025 |
Sync Labs | — | — | — | Dec 10, 2025 |
Sync Labs | — | — | — | Apr 6, 2026 |
Sync Labs | — | — | — | Jan 13, 2025 |