Aleph 2.0 is Runway’s in-context video editing model. It transforms existing traditional or generated footage using a written instruction and optional keyframe guidance. Its intended workflow changes the requested part of a scene while preserving its surrounding composition, lighting and details, making it useful for a product replacement, wardrobe change, background transformation, relighting or visual restyling without recreating the whole scene from a text brief.
Start with a direct action and the transformation you want: add, remove, replace, change, relight or restyle. For a product substitution, identify the visible object and describe its replacement, then state which hand movement, camera motion and surrounding setting should remain. For a seasonal scene, describe the weather or light that should change. A concise, targeted instruction gives a clearer editing goal than a general request to improve the entire clip.
Keyframe guidance establishes how the edited result should look at a particular moment. Choose a frame that clearly shows the target: a wide view for a background change, or a closer view for a small feature or accessory. In Runway’s Edit Studio workflow, a still-frame edit can be previewed and refined before that selected version guides the video transformation. Compare the edited frame with the source for the subject details, edges and objects you intend to preserve, then use it as the visual direction for the clip.
The producer API supports source videos from 2 to 30 seconds and up to five optional keyframe images placed at specified timestamps. Keep each guiding image associated with its intended point in the source, and use a small number of clear changes rather than a collection of conflicting visual targets. Aleph 2.0 is distinct from the older Gen-4 Aleph model; the producer identifies its API model separately. A keyframe-guided edit is also different from asking a text-to-video model to create an unrelated shot.
Edit Studio’s documented preparation rules use conventional aspect ratios, source resolution between 480p and 1080p, and 24–30 frames per second, with no more than ten cuts or shot changes. It recommends 720p or 1080p source material; over-30-fps footage is downsampled and over-30-second uploads are trimmed in that interface. These are the preparation rules of the producer editing workflow. Choose a source segment that shows the complete event you want to edit and whose subject remains visible where the change must carry through.
The model can propagate a changed background, clothing, object, light or style across the footage. An extra-motion instruction is useful when the edit needs a new action that is absent from the source and would not follow from the keyframe alone, such as a visual effect developing over time. Many edits need no extra-motion brief because the model animates the keyframe adjustment within the existing scene. Describe a new motion specifically, and keep it separate from the visual change that the keyframe already establishes.
The producer editing workflow applies an edit to the complete video by default and can limit it to a selected timeline range. Retain the original clip so the selected result can be compared with the source and used for a focused follow-up. A practical review looks beyond the chosen frame: check the beginning, middle, end, any cut and the period when the target is briefly obscured. The useful artifact is a revised clip whose requested transformation remains consistent through time while the important unchanged elements retain their role.
MP4 is the default playback and sharing artifact. Runway’s eligible full-video Edit Studio workflow also offers ProRes as a MOV file with PCM audio, or a ZIP of individual PNG frames for compositing. ProRes profiles range from 422 Proxy through 4444 XQ. Edits limited to a timeline range return MP4, and the output format is chosen when generation starts rather than changed after the finished result. Select the producer export form for the subsequent editing task while keeping it separate from the model’s core visual-editing capability.
For a useful finished edit, compare the intended substitution, lighting or style with the keyframe and inspect surrounding details that were not meant to change. Preserve the successful version and revise the specific instruction or guiding frame responsible for a mismatch. Aleph 2.0’s role is transforming source footage through a clear visual target; producing a new soundtrack, changing an application’s behavior or finishing a separate broadcast delivery pipeline are additional tasks around the edited video.
", "aboutText": "Aleph 2.0 is Runway’s in-context video editing model. It transforms existing traditional or generated footage using a written instruction and optional keyframe guidance. Its intended workflow changes the requested part of a scene while preserving its surrounding composition, lighting and details, making it useful for a product replacement, wardrobe change, background transformation, relighting or visual restyling without recreating the whole scene from a text brief.\n\nStart with a direct action and the transformation you want: add, remove, replace, change, relight or restyle. For a product substitution, identify the visible object and describe its replacement, then state which hand movement, camera motion and surrounding setting should remain. For a seasonal scene, describe the weather or light that should change. A concise, targeted instruction gives a clearer editing goal than a general request to improve the entire clip.\n\nKeyframe guidance establishes how the edited result should look at a particular moment. Choose a frame that clearly shows the target: a wide view for a background change, or a closer view for a small feature or accessory. In Runway’s Edit Studio workflow, a still-frame edit can be previewed and refined before that selected version guides the video transformation. Compare the edited frame with the source for the subject details, edges and objects you intend to preserve, then use it as the visual direction for the clip.\n\nThe producer API supports source videos from 2 to 30 seconds and up to five optional keyframe images placed at specified timestamps. Keep each guiding image associated with its intended point in the source, and use a small number of clear changes rather than a collection of conflicting visual targets. Aleph 2.0 is distinct from the older Gen-4 Aleph model; the producer identifies its API model separately. A keyframe-guided edit is also different from asking a text-to-video model to create an unrelated shot.\n\nEdit Studio’s documented preparation rules use conventional aspect ratios, source resolution between 480p and 1080p, and 24–30 frames per second, with no more than ten cuts or shot changes. It recommends 720p or 1080p source material; over-30-fps footage is downsampled and over-30-second uploads are trimmed in that interface. These are the preparation rules of the producer editing workflow. Choose a source segment that shows the complete event you want to edit and whose subject remains visible where the change must carry through.\n\nThe model can propagate a changed background, clothing, object, light or style across the footage. An extra-motion instruction is useful when the edit needs a new action that is absent from the source and would not follow from the keyframe alone, such as a visual effect developing over time. Many edits need no extra-motion brief because the model animates the keyframe adjustment within the existing scene. Describe a new motion specifically, and keep it separate from the visual change that the keyframe already establishes.\n\nThe producer editing workflow applies an edit to the complete video by default and can limit it to a selected timeline range. Retain the original clip so the selected result can be compared with the source and used for a focused follow-up. A practical review looks beyond the chosen frame: check the beginning, middle, end, any cut and the period when the target is briefly obscured. The useful artifact is a revised clip whose requested transformation remains consistent through time while the important unchanged elements retain their role.\n\nMP4 is the default playback and sharing artifact. Runway’s eligible full-video Edit Studio workflow also offers ProRes as a MOV file with PCM audio, or a ZIP of individual PNG frames for compositing. ProRes profiles range from 422 Proxy through 4444 XQ. Edits limited to a timeline range return MP4, and the output format is chosen when generation starts rather than changed after the finished result. Select the producer export form for the subsequent editing task while keeping it separate from the model’s core visual-editing capability.\n\nFor a useful finished edit, compare the intended substitution, lighting or style with the keyframe and inspect surrounding details that were not meant to change. Preserve the successful version and revise the specific instruction or guiding frame responsible for a mismatch. Aleph 2.0’s role is transforming source footage through a clear visual target; producing a new soundtrack, changing an application’s behavior or finishing a separate broadcast delivery pipeline are additional tasks around the edited video.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "87448a6c26ba8e30d856e4880d16da47d26b1f8a357b1b9d818add2dcf86371b", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "runway/aleph-2Aleph 2.0 edits existing video through targeted text instructions and keyframe guidance. Use it to replace an object, change a background, wardrobe, lighting or style, while directing which details of the original scene should stay intact.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Aleph 2.0 is Runway’s in-context video editing model. It transforms existing traditional or generated footage using a written instruction and optional keyframe guidance. Its intended workflow changes the requested part of a scene while preserving its surrounding composition, lighting and details, making it useful for a product replacement, wardrobe change, background transformation, relighting or visual restyling without recreating the whole scene from a text brief.
Start with a direct action and the transformation you want: add, remove, replace, change, relight or restyle. For a product substitution, identify the visible object and describe its replacement, then state which hand movement, camera motion and surrounding setting should remain. For a seasonal scene, describe the weather or light that should change. A concise, targeted instruction gives a clearer editing goal than a general request to improve the entire clip.
Keyframe guidance establishes how the edited result should look at a particular moment. Choose a frame that clearly shows the target: a wide view for a background change, or a closer view for a small feature or accessory. In Runway’s Edit Studio workflow, a still-frame edit can be previewed and refined before that selected version guides the video transformation. Compare the edited frame with the source for the subject details, edges and objects you intend to preserve, then use it as the visual direction for the clip.
The producer API supports source videos from 2 to 30 seconds and up to five optional keyframe images placed at specified timestamps. Keep each guiding image associated with its intended point in the source, and use a small number of clear changes rather than a collection of conflicting visual targets. Aleph 2.0 is distinct from the older Gen-4 Aleph model; the producer identifies its API model separately. A keyframe-guided edit is also different from asking a text-to-video model to create an unrelated shot.
Edit Studio’s documented preparation rules use conventional aspect ratios, source resolution between 480p and 1080p, and 24–30 frames per second, with no more than ten cuts or shot changes. It recommends 720p or 1080p source material; over-30-fps footage is downsampled and over-30-second uploads are trimmed in that interface. These are the preparation rules of the producer editing workflow. Choose a source segment that shows the complete event you want to edit and whose subject remains visible where the change must carry through.
The model can propagate a changed background, clothing, object, light or style across the footage. An extra-motion instruction is useful when the edit needs a new action that is absent from the source and would not follow from the keyframe alone, such as a visual effect developing over time. Many edits need no extra-motion brief because the model animates the keyframe adjustment within the existing scene. Describe a new motion specifically, and keep it separate from the visual change that the keyframe already establishes.
The producer editing workflow applies an edit to the complete video by default and can limit it to a selected timeline range. Retain the original clip so the selected result can be compared with the source and used for a focused follow-up. A practical review looks beyond the chosen frame: check the beginning, middle, end, any cut and the period when the target is briefly obscured. The useful artifact is a revised clip whose requested transformation remains consistent through time while the important unchanged elements retain their role.
MP4 is the default playback and sharing artifact. Runway’s eligible full-video Edit Studio workflow also offers ProRes as a MOV file with PCM audio, or a ZIP of individual PNG frames for compositing. ProRes profiles range from 422 Proxy through 4444 XQ. Edits limited to a timeline range return MP4, and the output format is chosen when generation starts rather than changed after the finished result. Select the producer export form for the subsequent editing task while keeping it separate from the model’s core visual-editing capability.
For a useful finished edit, compare the intended substitution, lighting or style with the keyframe and inspect surrounding details that were not meant to change. Preserve the successful version and revise the specific instruction or guiding frame responsible for a mismatch. Aleph 2.0’s role is transforming source footage through a clear visual target; producing a new soundtrack, changing an application’s behavior or finishing a separate broadcast delivery pipeline are additional tasks around the edited video.
POST /v1/videostext, image, audio, videovideo| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits runway/aleph-2 | Default— |
Fieldinput_references | Typearray | RequirementRequired | Values & limits Minimum items: 1 Maximum items: 1 | Default— |
Fieldprompt | Typestring | RequirementRequired | Values & limits Minimum length: 1 | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, input_references, prompt |
Parametermaterial_types | Contracttext, image, audio, video |
Parametermaterial_conditions | ContractUse 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
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.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations. Apply the minimum-charge rule shown for that configuration.
| Configuration | Rate schedule | Forecast quantity | Charge component | Billing unit | Billing conditions | Minimum charge rule | Charge |
|---|---|---|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Forecast quantity— | Charge component— | Billing unit— | Billing conditions— | Minimum charge rule— | 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 price | Rate schedule— | Forecast quantity— | Charge component— | Billing unitper video second | Billing conditionsNo additional condition is declared in this pricing key. | Minimum charge rule— | Charge Output · Video price · Estimate for comparison only $0.56 per video second |
| ConfigurationGeneration minimum | Rate schedule— | Forecast quantity— | Charge componentMinimum charge | Billing unitminimum generation charge | Billing conditionsNo additional condition is declared in this pricing key. | Minimum charge ruleYes | Charge total · Generation minimum · Estimate for comparison only $1.12 minimum generation charge Minimum charge per generation; apply it as a minimum, not an extra fee. No minimum duration is implied. |
| ConfigurationEstimated generation cost | Rate schedule— | Forecast quantityone generation estimate | Charge component— | Billing unit— | Billing conditions— | Minimum charge rule— | Charge Output · Estimated generation cost · Estimate for comparison only $0.56 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 →
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\n: "${AILOOT_INPUT_REFERENCES_JSON:?Set the actual documented input value}"\nexport AILOOT_INPUT_REFERENCES_JSON\n: "${AILOOT_PROMPT:?Set the actual documented input value}"\nexport AILOOT_PROMPT\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\nrequest={'model': 'runway/aleph-2', 'input_references': '${ACTUAL_OWNED_INPUT_REFERENCES}', 'prompt': '${ACTUAL_EDIT_PROMPT}'}\nrequest['input_references']=json.loads(os.environ['AILOOT_INPUT_REFERENCES_JSON'])\nrequest['prompt']=os.environ['AILOOT_PROMPT']\nPath('request.json').write_text(json.dumps(request,ensure_ascii=False),encoding='utf-8')\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/videos \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o response.bin\n# Retain the complete response and headers, every actual output, original returned identifiers and all usage fields. Recover the original operation without submitting creation again.\nGET /v1/videos/{request_id}GET /v1/videos/{request_id}/contentset -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\n: "${AILOOT_STATUS_FILE:?Set the actual completed status JSON file}"\nexport AILOOT_STATUS_FILE\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\nfrom urllib.parse import urlsplit,urljoin\nf=Path(os.environ["AILOOT_STATUS_FILE"])\nif not f.is_file():raise SystemExit("Choose the actual completed status file")\nr=json.loads(f.read_text())\nif 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")\nurls=[]\nfor x in r["data"]:\n if not isinstance(x,str) or "\\n" in x or "\\r" in x:raise SystemExit("Invalid asset path")\n u=urljoin("https://api.ailoot.ai",x)\n z=urlsplit(u)\n 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")\n urls.append(u)\nPath("asset-urls.txt").write_text("\\n".join(urls)+"\\n")\nPY_REQUEST\nindex=0\nwhile IFS= read -r asset_url; do\n curl --fail-with-body --silent --show-error "$asset_url" \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -o "video-${index}.mp4"\n index=$((index + 1))\ndone < asset-urls.txt\nSave 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.
Keep X-Client-Request-ID, X-Ailoot-Task-Id and actual returned id/polling_url. Continue the original job; do not submit creation again.
| Field | Type |
|---|---|
Fieldid | Type |
Fieldstatus | Type |
Fielddata[] | Type |
Fieldoutputs[] | Type |
Ailoot Ultra runway/aleph-2
Use the method paths shown above.