PixVerse v3.5 is a video model for text-to-video and image-to-video creation. A written prompt can establish a new scene, while a supplied image can provide its visual starting point. Use the model to develop a short event with an identifiable subject, motion and final composition.
Begin a text brief with the action the audience should follow. A toy vehicle moving past a stack of books, a character looking up from a desk or light shifting across a room each gives the shot a specific purpose. Add the setting and visual details needed to recognize the subject throughout the sequence.
For an image-led brief, prepare the reference around the subject’s important features. Keep its outline, pose and material details visible, and leave space for the requested movement. Describe how the scene develops from that frame. Retain the original image so the completed motion can be checked against its actual starting point.
The documented catalogue includes landscape, portrait and square frame shapes, several resolution choices and normal or fast motion modes. Choose the controls exposed for the selected workflow and keep their actual values with the result. Evaluate the requested action at the size and shape in which the clip will be used.
Plan a readable ending. A moving subject should finish in a useful position; a reveal should end with the important detail visible. Write this final state into the brief, then inspect whether the generated sequence reaches it. The ending determines how easily the shot can connect to another clip or graphic.
For a stylized scene, describe the visible treatment through color, lighting and materials. Keep the same subject details in the prompt and reference. Check how those details change when the subject moves across the frame or turns into a different view. Use the whole sequence when judging visual continuity.
Review motion, object interactions and timing in the completed clip. Watch for changes in shape, appearance or spatial relationships that affect the scene’s meaning. Inspect the opening and ending alongside the central action. Compare candidates using the same playback size so the choice reflects the destination format.
Save the finished video, prompt, reference and settings together. When a revision is needed, write down the observed mismatch and alter the relevant instruction. Preserve the parts of the scene that already work so the next candidate provides a focused comparison.
", "aboutText": "PixVerse v3.5 is a video model for text-to-video and image-to-video creation. A written prompt can establish a new scene, while a supplied image can provide its visual starting point. Use the model to develop a short event with an identifiable subject, motion and final composition.\n\nBegin a text brief with the action the audience should follow. A toy vehicle moving past a stack of books, a character looking up from a desk or light shifting across a room each gives the shot a specific purpose. Add the setting and visual details needed to recognize the subject throughout the sequence.\n\nFor an image-led brief, prepare the reference around the subject’s important features. Keep its outline, pose and material details visible, and leave space for the requested movement. Describe how the scene develops from that frame. Retain the original image so the completed motion can be checked against its actual starting point.\n\nThe documented catalogue includes landscape, portrait and square frame shapes, several resolution choices and normal or fast motion modes. Choose the controls exposed for the selected workflow and keep their actual values with the result. Evaluate the requested action at the size and shape in which the clip will be used.\n\nPlan a readable ending. A moving subject should finish in a useful position; a reveal should end with the important detail visible. Write this final state into the brief, then inspect whether the generated sequence reaches it. The ending determines how easily the shot can connect to another clip or graphic.\n\nFor a stylized scene, describe the visible treatment through color, lighting and materials. Keep the same subject details in the prompt and reference. Check how those details change when the subject moves across the frame or turns into a different view. Use the whole sequence when judging visual continuity.\n\nReview motion, object interactions and timing in the completed clip. Watch for changes in shape, appearance or spatial relationships that affect the scene’s meaning. Inspect the opening and ending alongside the central action. Compare candidates using the same playback size so the choice reflects the destination format.\n\nSave the finished video, prompt, reference and settings together. When a revision is needed, write down the observed mismatch and alter the relevant instruction. Preserve the parts of the scene that already work so the next candidate provides a focused comparison.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "57cc2e63ca7f94281ea6d9dca1a4432f1f05883f35c8cdcfbc4e90bdc840794a", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "pixverse-v3.5PixVerse v3.5 generates video from text or images. Its documented controls include several frame shapes, resolution choices and motion modes for developing short visual scenes with a clear action and edit point.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
PixVerse v3.5 is a video model for text-to-video and image-to-video creation. A written prompt can establish a new scene, while a supplied image can provide its visual starting point. Use the model to develop a short event with an identifiable subject, motion and final composition.
Begin a text brief with the action the audience should follow. A toy vehicle moving past a stack of books, a character looking up from a desk or light shifting across a room each gives the shot a specific purpose. Add the setting and visual details needed to recognize the subject throughout the sequence.
For an image-led brief, prepare the reference around the subject’s important features. Keep its outline, pose and material details visible, and leave space for the requested movement. Describe how the scene develops from that frame. Retain the original image so the completed motion can be checked against its actual starting point.
The documented catalogue includes landscape, portrait and square frame shapes, several resolution choices and normal or fast motion modes. Choose the controls exposed for the selected workflow and keep their actual values with the result. Evaluate the requested action at the size and shape in which the clip will be used.
Plan a readable ending. A moving subject should finish in a useful position; a reveal should end with the important detail visible. Write this final state into the brief, then inspect whether the generated sequence reaches it. The ending determines how easily the shot can connect to another clip or graphic.
For a stylized scene, describe the visible treatment through color, lighting and materials. Keep the same subject details in the prompt and reference. Check how those details change when the subject moves across the frame or turns into a different view. Use the whole sequence when judging visual continuity.
Review motion, object interactions and timing in the completed clip. Watch for changes in shape, appearance or spatial relationships that affect the scene’s meaning. Inspect the opening and ending alongside the central action. Compare candidates using the same playback size so the choice reflects the destination format.
Save the finished video, prompt, reference and settings together. When a revision is needed, write down the observed mismatch and alter the relevant instruction. Preserve the parts of the scene that already work so the next candidate provides a focused comparison.
POST /v1/videostext, imagevideo| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits pixverse-v3.5 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-v3.5",\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-v3.5
/v1/videos/generations