LSF Video Enhancement improves footage you already have, with output options for playback and professional editing. Choose Lite, Standard or Professional, select your output resolution and format, and submit the source video through POST /v1/videos. Retrieve the result through GET /v1/videos/{task_id}.
10.1 Choose an enhancement tier
| Tier | Model selection | Mode-specific controls |
|---|---|---|
| Lite | Use <YOUR_VIDEO_ENHANCEMENT_LITE_MODEL_ALIAS>. Omit tool_version. | Common resolution, FPS and bitrate controls. Omit scene, enhance_style and bit_depth. |
| Standard | Use <YOUR_VIDEO_ENHANCEMENT_MODEL_ALIAS>. Omit tool_version or set standard. | scene and enhance_style supported. No bit_depth. |
| Professional | Use the same Standard / Professional alias and set tool_version to professional. | enhance_style and bit_depth supported; codec on enabled profiles. Omit scene. |
Lite uses its own model alias. Do not send tool_version="fast". Standard and Professional share one model alias.
Supported enhancement output bands
| Tier | Configured output bands | API selection |
|---|---|---|
| Lite | Up to 720p, 1080p, 2K, 4K | 240p / 360p / 480p / 540p / 720p / 1080p / 2k / 4k |
| Standard | Up to 720p, 1080p, 2K, 4K, 6K, 8K | The Lite values plus 6k and 8k, subject to your account settings. |
| Professional | Up to 720p, 1080p, 2K, 4K, 6K, 8K | The Standard values; tool_version=professional. For 6K ProRes, use the format settings below. |
Available output tiers and resolutions depend on the model alias and options enabled for your account. “Up to 720p” is a pricing label, not an API resolution value; do not send “≤720p” as metadata.resolution.
6K output formats
| Tier | 16:9 output | Encoding | File |
|---|---|---|---|
| Standard | 6144 × 3456 | H.264, 8-bit, 4:2:0 | MP4 |
| Professional | 6144 × 3456 | ProRes, 10-bit, 4:2:2 | MOV |
6K uses a 3456-pixel short side and preserves the source aspect ratio; the proportional longer side is rounded upward to an even pixel. Exact 16:9 produces 6144 × 3456. Standard omits codec and bit_depth. Professional 6K uses codec=prores, bit_depth=10 and output_format=mov. ProRes needs compatible editing software and can produce larger files than MP4.
Source requirements for 6K
Use one directly accessible HTTP(S) video with readable media information, a finite positive duration and a source frame rate greater than zero and no more than 120 FPS. Source dimensions must be at most 1440 pixels on the short side and 2560 on the long side, in landscape or portrait orientation. Supply the actual source duration in metadata.duration. Supported clip length depends on the file and processing requirements.
Set output fps from 15 to 120, including fractional values, or omit it to retain the source frame rate. Select resolution="6k", or a resolution_limit from 2161 to 3456; do not send both. A limit in this range selects the 6K price band. Lower limits use lower resolution bands, while 3457–4320 selects the 8K band.
10.2 Request fields
| Field | Required | Usage |
|---|---|---|
| model | Yes | Exact model alias provided for the selected LSF Video Enhancement tier. |
| metadata.video_url | Yes | Public direct HTTP(S) source-video URL; HTTPS recommended. No login, cookies or private network required. asset:// is not supported in metadata.video_url for LSF Video Enhancement. |
| metadata.duration | Yes | Finite positive source duration in seconds. Supply an accurate value for the initial charge estimate; final billing uses the actual enhanced output. |
| metadata.tool_version | Optional | On the Standard / Professional alias, standard is the default or choose professional. On the separate Lite alias, omit this field or use lite; do not use fast. |
| metadata.resolution | One resolution selector | String: 240p, 360p, 480p, 540p, 720p, 1080p, 2k or 4k; Standard / Professional also support 6k and 8k when enabled. Section 10.1 defines the 6k formats. Do not send pricing labels such as lte_720p. |
| metadata.resolution_limit | Alternative selector | Integer short-side pixel limit, mutually exclusive with resolution: 128–2160 for Lite; 128–4320 for Standard / Professional. For example, 720 selects a lower-resolution pricing tier. Use the exact values documented here rather than a label such as lte_720p. |
| metadata.fps | Optional | Finite JSON number from 15 to 120, including fractional values. Omit to preserve source FPS. Omission uses the highest FPS band only for the initial billing estimate. |
| metadata.bitrate_level | Optional | low, medium or high. Omission preserves the service default behavior. |
| metadata.bitrate | Optional | Integer 10–150000 kbps. Use either bitrate or bitrate_level in a request for clear output intent. |
| metadata.scene | Standard only | common, ugc, short_series, aigc or old_film. Set an explicit value when needed; omission leaves the default setting in effect. |
| metadata.enhance_style | Standard / Professional only | hd or natural. |
| metadata.bit_depth | Professional only | Use the bit depth supported by your selected output format. Professional 6K ProRes requires 10 with codec=prores. Values 8, 12 and 16 are not interchangeable alternatives for that format. |
| metadata.codec | Enabled Professional profile only | String; requires explicit bit_depth. Professional 6K uses prores with bit_depth=10. Standard / Lite omit codec. |
| metadata.output_format | Optional | Must match the enabled encoding. Standard 6K uses MP4; Professional 6K ProRes uses mov. See section 10.1. |
| metadata.client_request_id | Recommended | 1–64 characters from A–Z, a–z, 0–9 and . _ : - . Recommended for retries; use the same key, ID and saved payload. See section 4.1. |
Supply exactly one resolution selector. Unknown metadata and fields that do not apply to the selected tier are rejected. The recommendation to request no more than four times the source FPS is quality guidance, not an additional pricing tier.
Resolution and advanced controls
Lite supports outputs through 4K; Standard and Professional include account-enabled higher-resolution profiles. Section 10.1 lists the 6K output formats. metadata.codec and output_format are accepted only with a compatible, enabled encoding combination; codec requires an explicit bit_depth and is Professional-only. Use the documented format settings for the selected resolution. ProRes ignores bitrate and bitrate_level; omit both for ProRes.
Standalone Video Enhancement does not accept metadata.return_last_frame, including false. Omit the field. MOV, 6K and 8K output does not include a requested last-frame image. Supported ProRes 6K does not imply availability of EXR sequences, FFV1 16-bit or HEVC 12-bit profiles.
10.3 Request examples
A. Standard · 1080p
POST /v1/videos
{
"model": "<YOUR_VIDEO_ENHANCEMENT_MODEL_ALIAS>",
"metadata": {
"video_url": "https://example.com/input-video.mp4",
"duration": 5,
"tool_version": "standard",
"scene": "aigc",
"resolution": "1080p",
"fps": 24,
"client_request_id": "enhance-standard-001"
}
}
B. Lite · 2K
POST /v1/videos
{
"model": "<YOUR_VIDEO_ENHANCEMENT_LITE_MODEL_ALIAS>",
"metadata": {
"video_url": "https://example.com/input-video.mp4",
"duration": 5,
"resolution": "2k",
"fps": 60,
"client_request_id": "enhance-lite-001"
}
}
C. Professional · 4K
POST /v1/videos
{
"model": "<YOUR_VIDEO_ENHANCEMENT_MODEL_ALIAS>",
"metadata": {
"video_url": "https://example.com/input-video.mp4",
"duration": 5,
"tool_version": "professional",
"resolution_limit": 2160,
"fps": 24,
"enhance_style": "natural",
"bit_depth": 10,
"client_request_id": "enhance-pro-001"
}
}
Professional rejects scene. Lite rejects scene, enhance_style and bit_depth. LSF Video Enhancement does not require a generation prompt.
A top-level prompt value (text, empty string or null) may be present but is ignored by LSF Video Enhancement. It does not affect processing or billing. Other unknown top-level fields remain unsupported.
Standard 6K MP4 example
{
"model": "<YOUR_VIDEO_ENHANCEMENT_MODEL_ALIAS>",
"metadata": {
"video_url": "https://example.com/source-video.mp4",
"duration": 10,
"tool_version": "standard",
"resolution": "6k",
"fps": 24,
"client_request_id": "enhance-standard-6k-001"
}
}
Standard must omit codec and bit_depth. It uses the H.264 8-bit MP4 profile. Do not add a codec field merely to restate that default.
Professional 6K ProRes example
{
"model": "<YOUR_VIDEO_ENHANCEMENT_MODEL_ALIAS>",
"metadata": {
"video_url": "https://example.com/source-video.mp4",
"duration": 10,
"tool_version": "professional",
"resolution": "6k",
"fps": 24,
"codec": "prores",
"bit_depth": 10,
"output_format": "mov",
"client_request_id": "enhance-pro-6k-001"
}
}
Professional omits scene. ProRes does not use bitrate or bitrate_level; omit those controls. No generation prompt is required. Source audio may be re-encoded or resampled; there is no audio-format or channel-layout request parameter.
10.4 Task lifecycle and result
After submission, poll GET /v1/videos/{task_id} every 30 seconds or longer. Continue with the same task ID through queued and in_progress, and stop at completed or failed. If a connection is interrupted, resume GET polling; do not submit another POST only because polling was interrupted.
Typical create response:
{
"id": "task_xxx",
"task_id": "task_xxx",
"object": "video",
"model": "<YOUR_VIDEO_ENHANCEMENT_MODEL_ALIAS>",
"status": "queued",
"progress": 0
}
Illustrative completed response; returned values depend on the actual output:
{
"id": "<YOUR_TASK_ID>",
"task_id": "<YOUR_TASK_ID>",
"object": "video",
"model": "<YOUR_VIDEO_ENHANCEMENT_MODEL_ALIAS>",
"status": "completed",
"progress": 100,
"metadata": {
"client_request_id": "enhance-standard-001",
"video_url": "https://example.com/enhanced-video.mp4",
"duration": 5.084,
"resolution": "1080p",
"fps": 24,
"tool_version": "standard"
}
}
Download from metadata.video_url or use the authenticated original-file route below, and store the result promptly. Access is temporary with no uniform guaranteed retention period. metadata.duration and metadata.fps are JSON numbers; resolution and tool_version are strings. An expiry value may be included when known; an already expired URL may be omitted. A successful HTTP response is not proof that the entire media file downloaded.
Download the original video
When status is completed, download the file with a key authorized to read the task:
curl --fail --show-error \
'https://ai-api.lightspeedfuture.com/v1/videos/<YOUR_TASK_ID>/content' \
--header 'Authorization: Bearer <LSF_API_KEY>' \
--output result.mov.part
Rename the temporary file after the transfer completes and your integrity checks pass. Keep your API key on your backend; do not forward the LSF Bearer token to an external media URL. If the transfer fails, download the same task result again without creating a new video. Result access is temporary; save files promptly. Resumable downloads are not guaranteed.
Output file information
| Optional response field | Meaning |
|---|---|
| metadata.requested_encoding | Requested codec, bit depth, file format and result type; not a measurement of the file. |
| metadata.output_metadata | Available details about the output file, such as codec and bit depth. |
| metadata.delivery_contract | Available media specifications and compatibility information. |
| metadata.delivery_contract.media | Dimensions, frame rate, frame count, pixel format and duration when available. |
Allow optional fields to be absent and additional fields to appear. Check the downloaded file in your intended software when exact format compatibility matters.
Use result.mp4.part for MP4 output.
10.5 Initial estimate and final billing
LSF Video Enhancement prices may be displayed per minute or per billable second. Convert a per-minute rate to a per-second rate by dividing by 60; do not divide a per-second quote again. Billing rounds the output duration reported in your task result up to a whole second, with no one-minute minimum. Use your agreed account rate. The existing FPS bands are:
| Output FPS band | Multiplier |
|---|---|
| Up to 30 | 1 |
| More than 30, up to 60 | 2 |
| More than 60, up to 120 | 4 |
-
With an explicit fps, the initial reservation uses the declared source duration rounded up to a whole second and the requested FPS band.
-
If fps is omitted, the initial charge estimate uses the highest FPS band. Processing preserves the source frame rate, and the final charge uses the actual output FPS.
-
Final charge = agreed base rate per second × rounded-up reported output seconds × actual-output FPS multiplier. If quoted per minute, divide that rate by 60 first. Only the output is charged; source seconds are not added separately. The price agreed when you submit stays fixed; any difference from the initial estimate is charged or returned once. The same FPS bands apply to 6K output.
-
For example, 5.084 output seconds become 6 chargeable seconds. If the final output is 24fps, the final FPS multiplier is 1 even when fps omission caused a highest-band initial estimate.
-
Repeated GET requests do not create tasks or duplicate charges. Replays do not reprice an already accepted task.
For example, 10 chargeable output seconds at 60 FPS use one sixth of the agreed per-minute base rate, multiplied by 2. The minute unit is a price display convention, not a minimum duration or a change to the rounding rule. Confirmed failed enhancement tasks release their reservation; a network timeout alone does not establish failure.
6K prices
| Output at up to 30 FPS | Base USD per billable second | Equivalent USD per output minute |
|---|---|---|
| Standard 6K H.264 MP4 | 0.052 | 3.12 |
| Professional 6K ProRes 10-bit MOV | 0.520 | 31.20 |
Your agreed account rate applies. Multiply by 2 for output above 30 through 60 FPS, or by 4 above 60 through 120 FPS. There is no one-minute minimum. For example, a reported 2.006-second output is billed as three seconds: Standard 6K at up to 30 FPS costs USD0.156 at the listed base rate, before account-specific terms. Use the applicable account rate for other resolutions.
Audio and editing
Audio may be re-encoded or resampled, with a small difference at the end of a compressed track. Retain your original soundtrack and check the downloaded result in your editor when precise timing or an unchanged track is required. ProRes 10-bit output requires compatible software. Bit depth alone does not guarantee HDR, additional source detail or lossless preservation.
10.6 Input and error checklist
Use a direct public HTTP(S) source that needs no cookies, private headers or private-network access and remains stable throughout processing. Avoid short expiry, redirect chains, anti-bot checks and hotlink protection. Browser playback alone does not prove processing compatibility. Follow the media limits confirmed during onboarding.
An active enhancement task can cause another submission for the same account user to return HTTP 409 with mediakit_task_in_progress. Poll the existing task and submit the next intended job when it has finished; reusing an ID is not a way to increase concurrency.