T2V 01 is MiniMax’s text-to-video edition for creating a scene from a written description. The text supplies the visual brief: who or what appears, where the action happens, how the subject moves and how the viewer sees it. Use it when the starting point is an idea or shot description rather than a prepared opening image.
Begin with the action that makes the scene useful. A small boat passing a pier, a hand placing a cup on a table or a traveler stopping beside a sign each gives the model a clear event to depict. State the important subject features and the setting, then describe the movement in the order it should be visible. Keep the shot centered on one readable sequence.
Choose the framing before adding decorative detail. A close view can emphasize a material or gesture, while a wider view can explain the relationship between the subject and its environment. Describe which object or person should remain the visual focus and what the ending should show. This gives the finished clip a purpose within a larger edit.
The maker’s text-to-video prompt supports up to 2,000 characters. Use that space for visible instructions and concrete relationships. For a product-style scene, identify the object’s shape, material, placement and the motion around it. For a character scene, explain the action and expression that carry the moment. Avoid asking one short clip to introduce many unrelated characters, locations and events.
The maker’s legacy text-to-video table lists 720P as the default resolution for T2V 01 and does not list a ten-second option for this edition. The documented duration default is six seconds. Plan the action with a clear beginning and ending inside a short shot, then inspect the actual result to see how much time each part receives.
Automatic prompt optimization is available in the maker’s workflow and is enabled by default. Retain that choice with the text so comparisons use a known brief. If a result misses an important detail, revise the instruction that describes that detail and preserve the parts that already work. A change to the subject action is easier to evaluate when the setting and viewpoint remain consistent.
Use the completed video as a scene element, concept shot or source clip for further editing. Keep exact written titles or captions in an editable layout source if they will accompany the imagery. Watch the full clip for subject continuity, the order of events and the final composition, rather than choosing a result from its first frame alone.
Save the actual video with the prompt and output settings. For a revision, identify the specific visual failure: an action that never completes, an object that changes shape, a gesture hidden by framing or a closing view that does not fit the edit. Change the relevant part of the scene description and compare the next result with the same shot goal. A clear retained brief makes it easier to build a sequence of clips whose subjects, settings and visual intentions are consistent.
", "aboutText": "T2V 01 is MiniMax’s text-to-video edition for creating a scene from a written description. The text supplies the visual brief: who or what appears, where the action happens, how the subject moves and how the viewer sees it. Use it when the starting point is an idea or shot description rather than a prepared opening image.\n\nBegin with the action that makes the scene useful. A small boat passing a pier, a hand placing a cup on a table or a traveler stopping beside a sign each gives the model a clear event to depict. State the important subject features and the setting, then describe the movement in the order it should be visible. Keep the shot centered on one readable sequence.\n\nChoose the framing before adding decorative detail. A close view can emphasize a material or gesture, while a wider view can explain the relationship between the subject and its environment. Describe which object or person should remain the visual focus and what the ending should show. This gives the finished clip a purpose within a larger edit.\n\nThe maker’s text-to-video prompt supports up to 2,000 characters. Use that space for visible instructions and concrete relationships. For a product-style scene, identify the object’s shape, material, placement and the motion around it. For a character scene, explain the action and expression that carry the moment. Avoid asking one short clip to introduce many unrelated characters, locations and events.\n\nThe maker’s legacy text-to-video table lists 720P as the default resolution for T2V 01 and does not list a ten-second option for this edition. The documented duration default is six seconds. Plan the action with a clear beginning and ending inside a short shot, then inspect the actual result to see how much time each part receives.\n\nAutomatic prompt optimization is available in the maker’s workflow and is enabled by default. Retain that choice with the text so comparisons use a known brief. If a result misses an important detail, revise the instruction that describes that detail and preserve the parts that already work. A change to the subject action is easier to evaluate when the setting and viewpoint remain consistent.\n\nUse the completed video as a scene element, concept shot or source clip for further editing. Keep exact written titles or captions in an editable layout source if they will accompany the imagery. Watch the full clip for subject continuity, the order of events and the final composition, rather than choosing a result from its first frame alone.\n\nSave the actual video with the prompt and output settings. For a revision, identify the specific visual failure: an action that never completes, an object that changes shape, a gesture hidden by framing or a closing view that does not fit the edit. Change the relevant part of the scene description and compare the next result with the same shot goal. A clear retained brief makes it easier to build a sequence of clips whose subjects, settings and visual intentions are consistent.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "43fe3c4f737838d68927eba84a2b8c4eea45efc469b65c8354518309aed29bca", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "minimaxi-t2v-01T2V 01 generates a short video from a written scene description. Use the text to establish the subject, setting, visible action and viewpoint, then review the clip’s timing and continuity against the intended shot.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
T2V 01 is MiniMax’s text-to-video edition for creating a scene from a written description. The text supplies the visual brief: who or what appears, where the action happens, how the subject moves and how the viewer sees it. Use it when the starting point is an idea or shot description rather than a prepared opening image.
Begin with the action that makes the scene useful. A small boat passing a pier, a hand placing a cup on a table or a traveler stopping beside a sign each gives the model a clear event to depict. State the important subject features and the setting, then describe the movement in the order it should be visible. Keep the shot centered on one readable sequence.
Choose the framing before adding decorative detail. A close view can emphasize a material or gesture, while a wider view can explain the relationship between the subject and its environment. Describe which object or person should remain the visual focus and what the ending should show. This gives the finished clip a purpose within a larger edit.
The maker’s text-to-video prompt supports up to 2,000 characters. Use that space for visible instructions and concrete relationships. For a product-style scene, identify the object’s shape, material, placement and the motion around it. For a character scene, explain the action and expression that carry the moment. Avoid asking one short clip to introduce many unrelated characters, locations and events.
The maker’s legacy text-to-video table lists 720P as the default resolution for T2V 01 and does not list a ten-second option for this edition. The documented duration default is six seconds. Plan the action with a clear beginning and ending inside a short shot, then inspect the actual result to see how much time each part receives.
Automatic prompt optimization is available in the maker’s workflow and is enabled by default. Retain that choice with the text so comparisons use a known brief. If a result misses an important detail, revise the instruction that describes that detail and preserve the parts that already work. A change to the subject action is easier to evaluate when the setting and viewpoint remain consistent.
Use the completed video as a scene element, concept shot or source clip for further editing. Keep exact written titles or captions in an editable layout source if they will accompany the imagery. Watch the full clip for subject continuity, the order of events and the final composition, rather than choosing a result from its first frame alone.
Save the actual video with the prompt and output settings. For a revision, identify the specific visual failure: an action that never completes, an object that changes shape, a gesture hidden by framing or a closing view that does not fit the edit. Change the relevant part of the scene description and compare the next result with the same shot goal. A clear retained brief makes it easier to build a sequence of clips whose subjects, settings and visual intentions are consistent.
POST /v1/videostextvideo| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits minimaxi-t2v-01 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",\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
/v1/videos/generations