PixVerse v5 is a video model for text-to-video and image-to-video creation. A written brief establishes the event, while an optional reference image supplies the starting appearance and composition. Use each generated shot for a defined purpose, such as introducing a subject, showing a gesture or revealing a visual detail.
Describe the action in observable terms. A hand opening a box, a figure crossing a courtyard or an object moving into light each gives the sequence an identifiable change. State which subject moves, what surrounds it and how the event should end. Keep the details that make the scene recognizable.
For image-led creation, choose a reference that already fits the intended composition. Keep distinctive features visible and provide room for the requested movement. Explain how the scene develops from that image. Retain the source with the completed video so continuity can be judged through direct comparison.
The documented model catalogue lists several frame shapes and resolution choices, with five- and eight-second duration options. Select the combination offered for the workflow and record its actual values. Plan the action and ending for the chosen shot length and destination frame.
Use camera direction to guide attention. A fixed viewpoint can emphasize a subject’s action, while a moving viewpoint can reveal a setting or detail. Explain the camera’s relationship to the subject so the motion serves the scene. Inspect the ending to see whether it leaves the intended information visible.
For a series of related shots, keep the recurring subject and setting descriptions consistent in the relevant briefs. Preserve each reference and selected model with its result. Assemble the completed clips in the intended order and inspect changes in appearance, lighting and spatial relationships across the edit.
Review each full video for the requested action, continuity and timing. Watch hands, faces, object outlines and material details when they are important to the scene. Check moments where subjects overlap or move into a different view. A useful shot remains readable beyond its strongest still frame.
Save the completed video with the prompt, source image and settings. When a candidate needs revision, identify the concrete mismatch and change the instruction connected to it. Keep successful composition and appearance choices stable so the next result can be compared against the same visual goal.
", "aboutText": "PixVerse v5 is a video model for text-to-video and image-to-video creation. A written brief establishes the event, while an optional reference image supplies the starting appearance and composition. Use each generated shot for a defined purpose, such as introducing a subject, showing a gesture or revealing a visual detail.\n\nDescribe the action in observable terms. A hand opening a box, a figure crossing a courtyard or an object moving into light each gives the sequence an identifiable change. State which subject moves, what surrounds it and how the event should end. Keep the details that make the scene recognizable.\n\nFor image-led creation, choose a reference that already fits the intended composition. Keep distinctive features visible and provide room for the requested movement. Explain how the scene develops from that image. Retain the source with the completed video so continuity can be judged through direct comparison.\n\nThe documented model catalogue lists several frame shapes and resolution choices, with five- and eight-second duration options. Select the combination offered for the workflow and record its actual values. Plan the action and ending for the chosen shot length and destination frame.\n\nUse camera direction to guide attention. A fixed viewpoint can emphasize a subject’s action, while a moving viewpoint can reveal a setting or detail. Explain the camera’s relationship to the subject so the motion serves the scene. Inspect the ending to see whether it leaves the intended information visible.\n\nFor a series of related shots, keep the recurring subject and setting descriptions consistent in the relevant briefs. Preserve each reference and selected model with its result. Assemble the completed clips in the intended order and inspect changes in appearance, lighting and spatial relationships across the edit.\n\nReview each full video for the requested action, continuity and timing. Watch hands, faces, object outlines and material details when they are important to the scene. Check moments where subjects overlap or move into a different view. A useful shot remains readable beyond its strongest still frame.\n\nSave the completed video with the prompt, source image and settings. When a candidate needs revision, identify the concrete mismatch and change the instruction connected to it. Keep successful composition and appearance choices stable so the next result can be compared against the same visual goal.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "f6e0a2da880102c1f0b4632454614c8d2772ea367e982a3aef73a6da651b5324", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "pixverse-v5PixVerse v5 creates short videos from text or images. Use a concrete action brief, a prepared reference when needed and the documented framing and resolution controls to develop a scene with a useful ending.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
PixVerse v5 is a video model for text-to-video and image-to-video creation. A written brief establishes the event, while an optional reference image supplies the starting appearance and composition. Use each generated shot for a defined purpose, such as introducing a subject, showing a gesture or revealing a visual detail.
Describe the action in observable terms. A hand opening a box, a figure crossing a courtyard or an object moving into light each gives the sequence an identifiable change. State which subject moves, what surrounds it and how the event should end. Keep the details that make the scene recognizable.
For image-led creation, choose a reference that already fits the intended composition. Keep distinctive features visible and provide room for the requested movement. Explain how the scene develops from that image. Retain the source with the completed video so continuity can be judged through direct comparison.
The documented model catalogue lists several frame shapes and resolution choices, with five- and eight-second duration options. Select the combination offered for the workflow and record its actual values. Plan the action and ending for the chosen shot length and destination frame.
Use camera direction to guide attention. A fixed viewpoint can emphasize a subject’s action, while a moving viewpoint can reveal a setting or detail. Explain the camera’s relationship to the subject so the motion serves the scene. Inspect the ending to see whether it leaves the intended information visible.
For a series of related shots, keep the recurring subject and setting descriptions consistent in the relevant briefs. Preserve each reference and selected model with its result. Assemble the completed clips in the intended order and inspect changes in appearance, lighting and spatial relationships across the edit.
Review each full video for the requested action, continuity and timing. Watch hands, faces, object outlines and material details when they are important to the scene. Check moments where subjects overlap or move into a different view. A useful shot remains readable beyond its strongest still frame.
Save the completed video with the prompt, source image and settings. When a candidate needs revision, identify the concrete mismatch and change the instruction connected to it. Keep successful composition and appearance choices stable so the next result can be compared against the same visual goal.
POST /v1/videostext, imagevideo| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits pixverse-v5 Conditions: Use this exact Ailoot routing selector. | Default— |
Fieldprompt | Typestring | RequirementRequired | Values & limits Conditions: Describe the scene and its motion. | Default— |
Fieldaspect_ratio | Typestring | RequirementOptional | Values & limits 16:9, 4:3, 1:1, 3:4, 9:16 Conditions: Use a listed selected-model aspect ratio. | Default— |
Fieldquality | Typestring | RequirementOptional | Values & limits 360p, 540p, 720p, 1080p Conditions: Use the listed selected-model quality value. | Default— |
Fieldmotion_mode | Typestring | RequirementOptional | Values & limits normal, fast Conditions: Use the listed selected-model motion mode. | Default— |
Fieldduration | Typeinteger | RequirementOptional | Values & limits 5, 8 Conditions: Use a listed duration; no unstated default. | Default— |
Fieldend_image | Typestring | RequirementOptional | Values & limits Conditions: An optional end frame selects a supported image mode. | Default— |
Fieldlip_sync_tts_content | Typestring | RequirementOptional | Values & limits Conditions: Optional selected-model speech content. | Default— |
Fieldlip_sync_tts_speaker_id | Typestring | RequirementOptional | Values & limits Conditions: Use an actual provider-supported voice ID; no voice ID is invented. | Default— |
Fieldimage | Typestring or array<string> | RequirementOptional | Values & limits Conditions: Use your actual publicly reachable image URL or base64 image; the selected model supports image input. | Default— |
Fieldnegative_prompt | Typestring | RequirementOptional | Values & limits Conditions: Describe content to avoid. | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, prompt |
Parameteroptional | Contractaspect_ratio, quality, motion_mode, duration, end_image, lip_sync_tts_content, lip_sync_tts_speaker_id, image, negative_prompt |
Parametermaterial_types | Contracttext, image |
Parameterconditions | ContractUse this exact Ailoot routing selector., Describe the scene and its motion., Use a listed selected-model aspect ratio., Use the listed selected-model quality value., Use the listed selected-model motion mode., Use a listed duration; no unstated default., An optional end frame selects a supported image mode., Optional selected-model speech content., Use an actual provider-supported voice ID; no voice ID is invented., Use your actual publicly reachable image URL or base64 image; the selected model supports image input., Describe content to avoid. |
Method aliases: /v1/videos/generations
Lifecycle: submit_once_poll_original
GET /v1/videos/{request_id}
GET /v1/videos/generations/{request_id}
GET /v1/videos/{request_id}/content
GET /v1/media/assets
GET /v1/media/assets/{asset_id}
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.
| Configuration | Rate schedule | Forecast quantity | Charge |
|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Forecast quantity— | 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 |
| ConfigurationEstimated generation cost | Rate schedule— | Forecast quantityone generation estimate | Charge Output · Estimated generation cost · Estimate for comparison only $0.2 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}"\ncat > request.json <<'JSON'\n{\n "model": "pixverse-v5",\n "prompt": "A cat is walking on grass."\n}\nJSON\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 result.json\n# Create once; retain id, polling_url, original task identifiers and every header.\nset -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\nexport AILOOT_API_KEY\npython3 - <<'PY_STATUS'\nimport json,os,subprocess\nfrom pathlib import Path\nfrom urllib.parse import urljoin,urlsplit\nr=json.loads(Path("result.json").read_text())\nu=urljoin("https://api.ailoot.ai",r["polling_url"])\np=urlsplit(u)\nif p.scheme!="https" or p.netloc!="api.ailoot.ai" or p.username or p.password:\n raise SystemExit("Unexpected returned polling URL; preserve the response")\nsubprocess.run(["curl","--fail-with-body","--silent","--show-error",u,"-H","Authorization: Bearer "+os.environ["AILOOT_API_KEY"],"-D","status-headers.txt","-o","status.json"],check=True)\n# Read this same original polling_url again while pending.\n# Preserve unknown/result_pending_check; do not repeat creation.\nPY_STATUS\nset -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\nexport AILOOT_API_KEY\npython3 - <<'PY_ASSETS'\nimport json,os,subprocess\nfrom pathlib import Path\nfrom urllib.parse import urljoin,urlsplit\nr=json.loads(Path("status.json").read_text())\nroles={}\ndef visit(v,path=""):\n if isinstance(v,dict):\n for k,x in v.items(): visit(x,path+"/"+k)\n elif isinstance(v,list):\n for i,x in enumerate(v): visit(x,path+"/"+str(i))\n elif isinstance(v,str):\n u=urljoin("https://api.ailoot.ai",v); p=urlsplit(u)\n if p.scheme=="https" and p.netloc=="api.ailoot.ai" and not p.username and not p.password and p.path.startswith("/v1/media/assets/") and p.path.endswith("/content"):\n roles.setdefault(u,[]).append(path)\nvisit(r)\nif not roles: raise SystemExit("No completed owned assets; retain the original status")\nmanifest=[]\nfor i,(u,paths) in enumerate(roles.items()):\n target=Path(f"asset-{i}.bin")\n subprocess.run(["curl","--fail-with-body","--silent","--show-error",u,"-H","Authorization: Bearer "+os.environ["AILOOT_API_KEY"],"-o",str(target)],check=True)\n raw=target.read_bytes()\n if not raw: raise SystemExit("Empty asset; retain original status and metadata")\n ext="glb" if raw[:4]==b"glTF" else "png" if raw[:8]==b"\\x89PNG\\r\\n\\x1a\\n" else "jpg" if raw[:3]==b"\\xff\\xd8\\xff" else "webp" if raw[:4]==b"RIFF" and raw[8:12]==b"WEBP" else "mp4" if raw[4:8]==b"ftyp" else "bin"\n name=f"asset-{i}.{ext}"\n if target.name!=name: target.rename(name)\n manifest.append({"file":name,"response_paths":paths,"bytes":len(raw)})\nPath("asset-manifest.json").write_text(json.dumps(manifest,indent=2))\nprint("Saved",len(manifest),"unique owned assets; every response role retained")\nPY_ASSETS\nGET /v1/videos/{request_id}GET /v1/videos/generations/{request_id}GET /v1/videos/{request_id}/contentGET /v1/media/assetsGET /v1/media/assets/{asset_id}Save every completed video or returned file; retrieve every actual returned asset URL.
Retain the complete response and headers, original identifiers, every actual output and all usage/accounting fields. Save each unique owned asset and retain every role pointing to it.
Keep the returned public task or operation id and all headers. Read only the original task; unknown or result_pending_check does not authorize another creation.
| Field | Type |
|---|---|
Fieldid | Typestring |
Fieldpolling_url | Typestring |
Fieldprovider_task_id | Typestring |
Fieldtask_id | Typestring |
Fieldstatus | Typestring |
Fieldvideo_url | Typestring |
Ailoot Ultra pixverse-v5
/v1/videos/generations