T2V 01 Director is MiniMax’s text-to-video edition with documented camera-movement commands. A written prompt establishes the scene and action, while bracketed instructions describe how the camera should move. Use this edition when the shot needs a particular reveal, approach, follow or change of viewpoint to make the scene understandable.
Start with the visual event. A person crossing a courtyard, a small object being placed on a workbench or a vehicle arriving at a doorway can each form one coherent shot. Describe the main subject, the setting and the action in a readable sequence. Then choose the camera movement that shows the important detail rather than adding movement only for its own sake.
The maker documents fifteen commands covering truck, pan, push and pull, pedestal, tilt, zoom, shake, tracking and a static shot. Their spelling is explicit, such as [Push in], [Pan left] or [Static shot]. Keep the distinction between the subject’s movement and the camera’s movement clear: the subject can cross the frame while the camera stays still, or the camera can follow while maintaining the subject’s position in view.
Several commands inside one pair of square brackets request simultaneous movement. Commands placed at successive points in the description request a sequence. The maker recommends combining no more than three movements. Place the command where its effect should begin and state the action that happens with it, so the requested camera work is tied to a visible moment in the shot.
The prompt supports up to 2,000 characters. Use the available text for subject appearance, scene relationships, action and framing. A brief can establish an object on a table, request an approach that reveals its surface and finish on a stable view. Keep the ending useful for the intended edit, especially when the next shot needs to continue from a recognizable composition.
The maker’s legacy text-to-video table lists 720P as the default for T2V 01 Director and does not list a ten-second option for this edition. Six seconds is the documented duration default. Choose a shot plan with enough time for the action and requested camera change, then inspect the actual pacing of the completed clip.
Automatic prompt optimization is enabled by default in the maker’s workflow and can be disabled for closer control of the written description. Record the setting with the exact camera commands when comparing versions. Keep a successful scene description stable while refining a camera move, or retain the camera plan while changing the action that needs correction.
Review the completed sequence for camera direction, framing and subject continuity. Check whether a reveal exposes the intended detail and whether the camera stops or continues as the brief requires. Save the actual video with the prompt and settings, then revise the concrete mismatch observed in the result. This keeps the Director edition’s camera controls connected to the shot’s purpose and makes comparisons between candidate clips easier to judge.
", "aboutText": "T2V 01 Director is MiniMax’s text-to-video edition with documented camera-movement commands. A written prompt establishes the scene and action, while bracketed instructions describe how the camera should move. Use this edition when the shot needs a particular reveal, approach, follow or change of viewpoint to make the scene understandable.\n\nStart with the visual event. A person crossing a courtyard, a small object being placed on a workbench or a vehicle arriving at a doorway can each form one coherent shot. Describe the main subject, the setting and the action in a readable sequence. Then choose the camera movement that shows the important detail rather than adding movement only for its own sake.\n\nThe maker documents fifteen commands covering truck, pan, push and pull, pedestal, tilt, zoom, shake, tracking and a static shot. Their spelling is explicit, such as [Push in], [Pan left] or [Static shot]. Keep the distinction between the subject’s movement and the camera’s movement clear: the subject can cross the frame while the camera stays still, or the camera can follow while maintaining the subject’s position in view.\n\nSeveral commands inside one pair of square brackets request simultaneous movement. Commands placed at successive points in the description request a sequence. The maker recommends combining no more than three movements. Place the command where its effect should begin and state the action that happens with it, so the requested camera work is tied to a visible moment in the shot.\n\nThe prompt supports up to 2,000 characters. Use the available text for subject appearance, scene relationships, action and framing. A brief can establish an object on a table, request an approach that reveals its surface and finish on a stable view. Keep the ending useful for the intended edit, especially when the next shot needs to continue from a recognizable composition.\n\nThe maker’s legacy text-to-video table lists 720P as the default for T2V 01 Director and does not list a ten-second option for this edition. Six seconds is the documented duration default. Choose a shot plan with enough time for the action and requested camera change, then inspect the actual pacing of the completed clip.\n\nAutomatic prompt optimization is enabled by default in the maker’s workflow and can be disabled for closer control of the written description. Record the setting with the exact camera commands when comparing versions. Keep a successful scene description stable while refining a camera move, or retain the camera plan while changing the action that needs correction.\n\nReview the completed sequence for camera direction, framing and subject continuity. Check whether a reveal exposes the intended detail and whether the camera stops or continues as the brief requires. Save the actual video with the prompt and settings, then revise the concrete mismatch observed in the result. This keeps the Director edition’s camera controls connected to the shot’s purpose and makes comparisons between candidate clips easier to judge.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "2015aee226f063447df05e09f6447eb9ae03e527a46a6aaf2fcb5cce62881332", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "minimaxi-t2v-01-directorT2V 01 Director creates video from text with explicit camera commands. Plan the subject and action, then use documented truck, pan, push, tilt, zoom, tracking or static-shot instructions to shape the camera’s movement through the scene.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
T2V 01 Director is MiniMax’s text-to-video edition with documented camera-movement commands. A written prompt establishes the scene and action, while bracketed instructions describe how the camera should move. Use this edition when the shot needs a particular reveal, approach, follow or change of viewpoint to make the scene understandable.
Start with the visual event. A person crossing a courtyard, a small object being placed on a workbench or a vehicle arriving at a doorway can each form one coherent shot. Describe the main subject, the setting and the action in a readable sequence. Then choose the camera movement that shows the important detail rather than adding movement only for its own sake.
The maker documents fifteen commands covering truck, pan, push and pull, pedestal, tilt, zoom, shake, tracking and a static shot. Their spelling is explicit, such as [Push in], [Pan left] or [Static shot]. Keep the distinction between the subject’s movement and the camera’s movement clear: the subject can cross the frame while the camera stays still, or the camera can follow while maintaining the subject’s position in view.
Several commands inside one pair of square brackets request simultaneous movement. Commands placed at successive points in the description request a sequence. The maker recommends combining no more than three movements. Place the command where its effect should begin and state the action that happens with it, so the requested camera work is tied to a visible moment in the shot.
The prompt supports up to 2,000 characters. Use the available text for subject appearance, scene relationships, action and framing. A brief can establish an object on a table, request an approach that reveals its surface and finish on a stable view. Keep the ending useful for the intended edit, especially when the next shot needs to continue from a recognizable composition.
The maker’s legacy text-to-video table lists 720P as the default for T2V 01 Director and does not list a ten-second option for this edition. Six seconds is the documented duration default. Choose a shot plan with enough time for the action and requested camera change, then inspect the actual pacing of the completed clip.
Automatic prompt optimization is enabled by default in the maker’s workflow and can be disabled for closer control of the written description. Record the setting with the exact camera commands when comparing versions. Keep a successful scene description stable while refining a camera move, or retain the camera plan while changing the action that needs correction.
Review the completed sequence for camera direction, framing and subject continuity. Check whether a reveal exposes the intended detail and whether the camera stops or continues as the brief requires. Save the actual video with the prompt and settings, then revise the concrete mismatch observed in the result. This keeps the Director edition’s camera controls connected to the shot’s purpose and makes comparisons between candidate clips easier to judge.
POST /v1/videostextvideo| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits minimaxi-t2v-01-director Conditions: Use the exact Ailoot model selector. | Default— |
Fieldprompt | Typestring | RequirementRequired | Values & limits Conditions: Describe the scene and motion. | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, prompt |
Parameteroptional | Contract |
Parametermaterial_types | Contracttext |
Parameterconditions | ContractUse the exact Ailoot model selector., Describe the scene and motion. |
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 | Billing quantity | Charge |
|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Forecast quantity— | Billing 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 |
| ConfigurationPer request | Rate schedule— | Forecast quantity— | Billing quantityone request | Charge Input · Estimate for comparison only $1 per request |
| ConfigurationEstimated generation cost | Rate schedule— | Forecast quantityone generation estimate | Billing quantity— | Charge Output · Estimated generation cost · Estimate for comparison only $1 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": "minimaxi-t2v-01-director",\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 minimaxi-t2v-01-director
/v1/videos/generations