Verify that this server can reach LipDub and report which account it is using.

Call this first if any other LipDub tool fails with an authentication error, or when a user asks whether LipDub is set up.

Does not use credits and does not start anything.

Credit balance is not available through the API — direct the user to https://app.lipdub.ai to see it.

Start a LipDub 2 render: make the person in a source video appear to speak a different audio track, with matched lip movement.

USES CREDITS. Each render charges the account and cannot be undone or refunded. Cost scales with the length of the source video. Confirm with the user first, then call again with confirm_spend set to true.

Supply BOTH sides as direct, publicly downloadable URLs:

• video_url — a video of ONE person speaking, face clearly visible.

• audio_url — the audio you want them to appear to say.

LipDub 2 does NOT translate, transcribe or generate speech. If the user wants another language, produce that audio first with a separate text-to-speech or voice tool, host it at a URL, and pass that URL as audio_url.

Links must return the media file itself. Google Drive, Dropbox and YouTube share pages, and anything behind a login, will fail.

Returns immediately with a render_id — the render is NOT finished. Rendering takes about 7–15 minutes. Next step: call lipdub_wait_for_render with that render_id.

Check a LipDub render once, right now, and return its download link if it has finished. This does NOT wait — it answers immediately with whatever the current status is. To wait for a render to finish, use lipdub_wait_for_render instead.

Takes the render_id from lipdub_create_render.

Free and never rate-limited — check as often as you need.

status is one of:

• preparing — LipDub is downloading your source files (usually under 2 minutes)

• queued — waiting for a render slot

• rendering — generating the video

• succeeded — done; download_url is included

• failed — see failure_reason

download_url is a temporary signed link that expires. Give it to the user or download it promptly; do not save it for later.

If the render is not finished yet, prefer lipdub_wait_for_render — it waits for you instead of making you check repeatedly.

Wait for a LipDub render to finish, then return its download link. Use this straight after lipdub_create_render instead of checking in a loop — it uses far less context.

This call blocks for up to max_wait_seconds (default 240, maximum 600) while tracking the render for you. A typical render takes 7–15 minutes, so one call is often not enough.

If the render is still going when the wait is up, this returns normally with still_running set to true. That is NOT an error and NOT a failure — the render is fine and is still going. When it happens: tell the user it is still in progress, give them the render_id so they can come back to it, and call this tool again to keep waiting.

Waiting and status checks are free and never rate-limited.

List recent LipDub renders on this account, newest first.

Use this when:

• you have lost a render_id, for example because earlier conversation was trimmed away and a render is still running or already finished

• the user asks what they have rendered recently

Returns a short summary of each. Call lipdub_get_render with one of the returned render_ids to get its download link.

Free and never rate-limited.