models

Black Forest Labs: FLUX Video Edit

Markdown · JSON

Black Forest Labs: FLUX Video Edit

FLUX Video Edit [fast] transforms an existing clip through a written edit instruction. Add, remove or replace elements, change the setting or style, and revise existing dialogue while working within the documented source-length, framing and audio constraints.

About the model

This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.

FLUX Video Edit [fast] is Black Forest Labs’ prompt-guided workflow for changing an existing video. It receives one source clip and an instruction describing the edit, then returns an edited MP4. The source establishes the shot: its duration, framing, camera movement and timing provide the starting structure. Use the prompt to identify what should become different, rather than writing a completely new scene description that leaves the intended change unclear.

Name the change and its position

The documented edits include removing, adding or replacing objects and characters, rebuilding the setting, restyling a clip, changing visible text and revising dialogue or sound. Start with the target and the operation. An original instruction could remove a bag from a chair while retaining the seated person and the room, or replace a plain mug with a blue enamel mug without changing the hand’s action. If several similar objects are visible, distinguish the target by its position, appearance or role.

For an addition, describe location, scale and relevant action. A tall red lamp beside the sofa is more specific than an unspecified extra lamp somewhere in the shot. For a replacement, identify what becomes what and the movement or contact that should remain. The maker’s prompting guide recommends the shortest instruction that fully names the change, adding detail where the edit requires it. Preserve source features deliberately instead of asking for a general improvement whose scope cannot be evaluated.

Settings, styles and rough animation

A setting change can rebuild the visible environment while retaining the action. The producer demonstrates replacing a climbing surface with a different structure and specifying the new contact points, so the character’s hands and feet still have a meaningful surface. In a practical scene, describe the changed surroundings and the geometry the existing movement relies on. A new background is easier to assess when the original action has an explicit relationship with it.

The guide also shows transforming a rough animation into a finished visual treatment. Name which blockout objects become the intended vehicles or props, then retain their paths, speeds and camera relationship. For restyling, describe the resulting materials, surfaces, light and reflections as well as the aesthetic. A clay-like scene and a photographic-looking scene need different visible cues even when they follow the same action.

A further revision can use the first edited result as its new source. Keep the original and each selected stage, and give the next pass one clear purpose. The documented example follows a rough preview through a finished setting and then another lighting treatment. After each pass, compare the revised clip with the previous source and check that the features you meant to retain are still present.

Dialogue must fit existing time

The workflow carries source audio through unless the instruction requests a dialogue or sound change. A silent source returns a silent result, so it supplies no existing speech to revise. For a dialogue edit, quote the intended line, identify the speaker and fit the new words to the time occupied by the source line. The guide reports a longer replacement being cut when it exceeded the available speech interval. Writing more words does not create extra speaking time inside the existing shot.

Review the audible line alongside the visible performance. Keep a copy of the source wording and intended replacement so an omitted word, mistimed phrase or unwanted sound change can be identified. The useful result is the revised spoken moment inside the edited scene, not an assumed faithful transcript merely because the render completed.

Source limits and inherited output

The exact producer profile requires a video and an edit prompt. The instruction is one to 4,096 characters after surrounding whitespace is removed. The clip is supplied through a URL or encoded MP4, with a maximum length of fifteen seconds and a fifty-MiB input limit. Each side must be at least 160 pixels, and the normalized clip must contain at least seventeen frames at 24 fps, roughly seven-tenths of a second. Overlength sources are rejected rather than silently trimmed; undersized sources can fail during processing.

The documented flow uses 24-fps processing and follows the source length and aspect ratio. Inputs above the 720p profile are downscaled; the maker gives a 1920×1088 source returning as 1248×704. Duration, resolution and aspect ratio are not independent output settings in this editing profile. Its sampling recipe is handled internally, and fields such as mode, version, seed or generate_audio are not accepted in the stated request contract.

A video used only as motion or style inspiration for a newly generated shot is a different workflow. This editor does not accept an image reference, audio-only input, masks or a request to extend the clip. Prepare the actual video to alter and retain its selected duration before writing the edit. After asynchronous processing, the producer returns the edited MP4 through a temporary signed delivery link, valid for about one hour. Save the result and compare the changed object, surrounding frames, timing and audio with the source before using the clip in a longer edit.

Ailoot Ultra · Video POST /v1/videos black-forest-labs/flux-video-edit

black-forest-labs/flux-video-edit

Black Forest Labs /black-forest-labs/flux-video-edit

Overview

FLUX Video Edit [fast] transforms an existing clip through a written edit instruction. Add, remove or replace elements, change the setting or style, and revise existing dialogue while working within the documented source-length, framing and audio constraints.

Accepted inputs
Text · Images · Audio · Video
Results
Video

Available in Ailoot · inputs & methods

Ailoot Ultra · Video POST /v1/videos
Input types
text, image, audio, video
Output types
video
FieldTypeRequirementValues & limitsDefault
FieldmodelTypestringRequirementRequiredValues & limits
black-forest-labs/flux-video-edit
Default—
Fieldinput_referencesTypearrayRequirementRequiredValues & limits
Minimum items: 1
Maximum items: 1
Default—
FieldpromptTypestringRequirementRequiredValues & limits
Minimum length: 1
Default—
Method parameters and lifecycle
ParameterContract
Parametercontent_typeContractapplication/json
ParameterrequiredContractmodel, input_references, prompt
Parametermaterial_typesContracttext, image, audio, video
Parametermaterial_conditionsContractUse exactly one actual completed owned video asset content URL with its returned signature. The asset owner, type and stored byte witness must match the request.

Lifecycle: asynchronous_job_then_owned_outputs

GET /v1/videos/{request_id} · actual returned id or polling_url

GET /v1/videos/{request_id}/content

Pricing

How the final charge is calculated

The displayed rates estimate the cost before generation. The final charge is calculated from the cost recorded for the original generation. Measured output duration and forecast quantities are not the final billable quantity.

Tariff references do not add request options. Supported parameters are listed for the selected method.

Fast mode
Not specified When fast mode is selected
Flex mode
Not specified When flex mode is selected
Maximum reasoning effort
Not specified When maximum reasoning effort uses the default adjustment

Estimated rates for comparison

Prices by configuration

Match each charge to the conditions shown. Use one rate for each set of alternative configurations.

ConfigurationRate scheduleForecast quantityBilling unitBilling conditionsCharge
ConfigurationBase token ratesRate scheduleBase rateForecast quantity—Billing unit—Billing conditions—Charge
Input · Input tokens · Estimate for comparison only — / 1K tokens
Output · Output tokens · Estimate for comparison only — / 1K tokens
Input · Cache read · Estimate for comparison only — / 1K tokens
Input · Cache write · Estimate for comparison only — / 1K tokens
Input · Cache write, 1 hour · Estimate for comparison only — / 1K tokens
ConfigurationVideo priceRate schedule—Forecast quantity—Billing unitper video secondBilling conditionsNo additional condition is declared in this pricing key.Charge
Output · Video price · Estimate for comparison only $0.06 per video second
ConfigurationEstimated generation costRate schedule—Forecast quantityone generation estimateBilling unit—Billing conditions—Charge
Output · Estimated generation cost · Estimate for comparison only $0.06 estimate before generation

This estimate is not an additional charge or a fixed rate for the completed generation.

Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →

Example requests

Ailoot Ultra · Video

Use actual input and retain the complete result
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
: "${AILOOT_INPUT_REFERENCES_JSON:?Set the actual documented input value}"
export AILOOT_INPUT_REFERENCES_JSON
: "${AILOOT_PROMPT:?Set the actual documented input value}"
export AILOOT_PROMPT
python3 - <<'PY_REQUEST'
import json,os
from pathlib import Path
request={'model': 'black-forest-labs/flux-video-edit', 'input_references': '${ACTUAL_OWNED_INPUT_REFERENCES}', 'prompt': '${ACTUAL_EDIT_PROMPT}'}
request['input_references']=json.loads(os.environ['AILOOT_INPUT_REFERENCES_JSON'])
request['prompt']=os.environ['AILOOT_PROMPT']
Path('request.json').write_text(json.dumps(request,ensure_ascii=False),encoding='utf-8')
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/videos \
  -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \
  --data-binary @request.json -D response-headers.txt -o response.bin
# Retain the complete response and headers, every actual output, original returned identifiers and all usage fields. Recover the original operation without submitting creation again.

Receive and save results

Ailoot Ultra · Video

  • GET /v1/videos/{request_id}
  • GET /v1/videos/{request_id}/content
Save all completed assets
GET all completed assets
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
: "${AILOOT_STATUS_FILE:?Set the actual completed status JSON file}"
export AILOOT_STATUS_FILE
python3 - <<'PY_REQUEST'
import json,os
from pathlib import Path
from urllib.parse import urlsplit,urljoin
f=Path(os.environ["AILOOT_STATUS_FILE"])
if not f.is_file():raise SystemExit("Choose the actual completed status file")
r=json.loads(f.read_text())
if r.get("status")!="completed" or not isinstance(r.get("data"),list) or not r["data"]:raise SystemExit("Wait for a completed status with asset paths")
urls=[]
for x in r["data"]:
    if not isinstance(x,str) or "\n" in x or "\r" in x:raise SystemExit("Invalid asset path")
    u=urljoin("https://api.ailoot.ai",x)
    z=urlsplit(u)
    if z.scheme!="https" or z.netloc!="api.ailoot.ai" or z.username or z.password:raise SystemExit("Use the actual Ailoot asset paths from status")
    urls.append(u)
Path("asset-urls.txt").write_text("\n".join(urls)+"\n")
PY_REQUEST
index=0
while IFS= read -r asset_url; do
  curl --fail-with-body --silent --show-error "$asset_url" \
    -H "Authorization: Bearer $AILOOT_API_KEY" -o "video-${index}.mp4"
  index=$((index + 1))
done < asset-urls.txt
Keep all completed results

Save every completed video or returned file; retrieve every actual returned asset URL.

Retain the complete response and headers, every actual output, original returned identifiers and all usage fields. Recover the original operation without submitting creation again.

If the original response needs checking

Keep X-Client-Request-ID, X-Ailoot-Task-Id and actual returned id/polling_url. Continue the original job; do not submit creation again.

Response fields
FieldType
FieldidType
FieldstatusType
Fielddata[]Type
Fieldoutputs[]Type

Aliases

Model aliases

Ailoot Ultra black-forest-labs/flux-video-edit

Method path aliases

Use the method paths shown above.

Related caller IDs

black-forest-labs/flux-video-edit

FAQ · Black Forest Labs: FLUX Video Edit
What inputs and results are available?

POST /v1/videos · black-forest-labs/flux-video-edit: text, image, audio, video → video

Which fields does the request use?

POST /v1/videos · black-forest-labs/flux-video-edit: model, input_references, prompt

More details

Connect Ailoot to Claude Code, OpenCode, Hermes or your own app.

The company and its project portfolio

The company and its project portfolio: millions of customers; monthly sales in the billions.

Buy tokens at a discount.

Subscription discounts for regular use. Promo codes offer up to 50% off token purchases.

Subscription
Choose a discounted plan for your regular requests.
Promo code: up to 50% off
Enter your code at checkout. The price updates to reflect the current promotion.
Spending in your history
The model, tokens and amount are recorded for each request.

Choose a subscription · View model prices

Connect the API to a product you sell.

Use Ailoot in SaaS, apps and bots under its official service offer and licence agreement. Request a reseller licence for resale.

Commercial application
Add text, image, video and audio generation to paid features in your service.
Reseller licence
Send a description of your project and how you provide access. Request written terms for use and resale.
Documents on the website
The service offer, licence agreement and data processing policy are available before you connect.

Request a reseller licence · Service offer and licence agreement