sora-2

Sora 2 creates video with synchronized dialogue, sound effects and background audio from text or an image reference. The standard profile supports visual exploration and concept clips, with separate producer workflows for reusable non-human characters, continuation and focused video edits.

Ailoot Ultra · Chat Completions POST /v1/chat/completions sora-2
Ailoot Ultra · Anthropic Messages POST /v1/messages sora-2

About the model

This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.

Sora 2 is OpenAI’s video-and-audio generation model for dynamic clips created from a written scene description or an image reference. It generates the visual sequence together with synchronized speech, effects and background sound. The standard Sora 2 profile is positioned for visual exploration, concept development, prototypes and rough cuts. Sora 2 Pro is a separate edition aimed at greater visual fidelity and higher-resolution finishing.

Describe a shot that can be seen and heard

The maker’s prompting guide organizes a useful brief around framing, subject, action, setting and light. Give the scene a coherent visual style, then describe the movement in clear beats. An original product concept might show a small mechanical object turning once on a workbench while the camera moves slowly closer, with soft window light and a subtle motor sound. State what the viewer should notice and how the action ends.

Keep each shot’s camera movement and subject action understandable. A complicated sequence can be divided into distinct shot blocks, each with its own framing, action and lighting. Preserve the same subject details and palette when several clips are intended to form one sequence. The guide emphasizes that shorter shots generally follow direction more reliably and that repeated generation of the same prompt produces different takes.

The model’s launch describes improved physical behavior and continuity across shots, including realistic, cinematic and anime styles. These are intended capabilities to direct and inspect. Review motion, contact between objects, proportions and continuity rather than assuming that a plausible first frame guarantees a coherent sequence. If an action is unclear, simplify it and give it a visible beginning and ending.

Direct dialogue and sound separately

Specify spoken lines separately from the visual description and label the speakers consistently. Keep dialogue short enough to fit the action and the intended clip length. For a two-character animation, alternate a brief question and answer rather than asking a short shot to accommodate a long speech. The guide warns that complex, lengthy dialogue can disrupt pacing and synchronization.

Describe the soundscape that belongs to the scene: a small movement’s sound, room ambience or the rhythm of an environmental effect. Explain which sound should coincide with the action. Listen to the resulting speech and effects together with the picture, checking speaker assignment, wording and timing. Synchronized audio is part of the generated clip rather than a separate text answer.

Size, duration and an image-guided opening

The standard model’s documented output sizes are 720×1280 portrait and 1280×720 landscape. Higher-resolution sizes in the Pro profile should not be attached to standard Sora 2. Size and duration are explicit request settings; writing a different size or asking for a longer film in the prompt does not change those settings. The creation reference lists 4-, 8- and 12-second clip settings, so choose a short, defined beat when preparing a shot. The expanded producer workflow also documents 16- and 20-second clip settings.

An image reference anchors the first frame, and the text describes what happens next. The producer supports JPEG, PNG and WebP references and requires the image to match the target video size. Prepare the subject, environment and composition in that opening image, then ask for a specific movement. This is an opening-frame reference rather than a guarantee of matching every detail throughout the clip.

Reusable non-human characters

The expanded producer workflow can create a reusable character asset from a short reference video of an animal, mascot or object. Its preparation guidance calls for an MP4 clip around two to four seconds, 720p to 1080p, in 16:9 or 9:16. Matching the source and output aspect ratio helps avoid a stretched appearance. The generation can reference up to two characters.

Retain the character identifier and mention its name in the prompt; passing the identifier alone is not the guide’s complete preparation. Character assets can accompany an image-guided generation, but video extensions do not accept them. The producer blocks human-likeness character uploads by default and rejects reference images containing human faces in the documented API flow. The Sora app’s personal-character features are a separate product workflow.

Continue or edit a completed clip

An extension takes a completed source video and a continuation prompt, using the full source clip as context for motion, camera direction and scene continuity. The guide describes additions of up to 20 seconds per extension. Its documented extension input is the source video and text; additional character or image references are excluded from that mode. Describe how the existing action continues instead of introducing an unrelated scene without a transition.

Video editing targets a clear change to an existing clip. A focused revision can alter an object’s color or the scene’s palette while retaining the rest of the shot. The producer guide recommends one well-defined change at a time and distinguishes editing a generated video from uploading arbitrary footage, which has a separate eligibility condition. Keep the completed source and identify the exact revision needed before making another edit.

Render jobs and the finished video

The documented producer video flow is asynchronous: a submitted job can be queued or in progress before it completes or fails. A completed job yields an MP4 video; thumbnail and sprite-sheet assets support previews and browsing. Keep the job identity associated with the prompt, references and returned assets. An initial job response is not the final playable video.

The ordinary download workflow describes a one-hour download-URL lifetime. The expanded batch workflow prepares independent JSON render requests with stable item identifiers, uploaded references and a result mapped back to each shot; its completed assets have a separate download period of up to 24 hours. Preserve the finished clip promptly and inspect the actual picture and sound before treating it as a selected take.

The producer’s documented API content restrictions require material suitable for audiences under 18 and reject copyrighted characters or music and generation of real people. Prepare the scene and references accordingly. The direct model result is video with audio, not generated still images, a conversational tool response or an unlimited film. Retain the exact standard-model identity and the accepted source clip when continuing a visual concept.

Ailoot Ultra · Chat Completions POST /v1/chat/completions sora-2

sora-2

Other /sora-2

Overview

Accepted inputs: Text
Results: json · sse

Available in Ailoot · inputs & methods

Ailoot Ultra · Chat Completions POST /v1/chat/completions

Input types: text
Output types: json, sse
Output format: JSON or text/event-stream

Field	Type	Requirement	Values & limits	Default
Field`model`	Type`string`	RequirementRequired	Values & limits sora-2	Default—
Field`messages`	Type`message[]`	RequirementRequired	Values & limits	Default—
Field`messages[].role`	Type`string`	RequirementRequired	Values & limits	Default—
Field`messages[].content`	Type`string`	RequirementRequired	Values & limits	Default—
Field`stream`	Type`boolean`	RequirementOptional	Values & limits	Defaultfalse

Input material combinations

owned_text_messages

Method parameters and lifecycle

Parameter	Contract
Parameter`content_type`	Contractapplication/json
Parameter`required`	Contractmodel, messages
Parameter`material_types`	Contracttext
Parameter`messages`	Contractmessage array with role and literal string content
Parameter`file_material`	ContractActual UTF-8 material may be inserted as literal string content; no file reference is inferred.
Parameter`optional_controls`	Contractstream

Lifecycle: synchronous_json_or_sse

Pricing

Tariff references do not add request options. Supported parameters are listed for the selected method.

Fast mode: Not specified When fast mode is selected
Flex mode: Not specified When flex mode is selected
Maximum reasoning effort: Not specified When maximum reasoning effort uses the default adjustment

Ailoot rates

Prices by configuration

Configuration	Rate schedule	Charge
ConfigurationBase token rates	Rate scheduleBase rate	Charge Input · Input tokens $0 / 1K tokens Output · Output tokens $0.2 / 1K tokens Input · Cache read $0 / 1K tokens Input · Cache write $0 / 1K tokens Input · Cache write, 1 hour — / 1K tokens

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 →

Example requests

Ailoot Ultra · Chat Completions

curl · complete JSON responsePython SDK · complete JSON responsecurl · preserve SSE stream

set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
python3 - <<'PY_REQUEST'
import json,os
from pathlib import Path
p=json.loads('{"model":"sora-2","messages":[{"role":"user","content":"hello"}],"stream":false}')

Path("request.json").write_text(json.dumps(p,ensure_ascii=False))
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/chat/completions \
  -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \
  --data-binary @request.json -D response-headers.txt -o result.json
python3 - <<'PY_RESULT'
from pathlib import Path
print(Path("result.json").read_text(encoding="utf-8"))
PY_RESULT

from openai import OpenAI
import os

if not os.environ.get("AILOOT_API_KEY", "").strip(): raise SystemExit("Set AILOOT_API_KEY before making a request")
client=OpenAI(base_url="https://api.ailoot.ai/v1",api_key=os.environ["AILOOT_API_KEY"],max_retries=0)
result=client.chat.completions.create(model="sora-2", messages=[{"role":"user","content":"hello"}], stream=False)
import json
from pathlib import Path

data = result.to_dict(mode="json")
Path("result.json").write_text(json.dumps(data, ensure_ascii=False, indent=2), encoding="utf-8")
print(json.dumps(data, ensure_ascii=False, indent=2))

set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
python3 - <<'PY_REQUEST'
import json,os
from pathlib import Path
p=json.loads('{"model":"sora-2","messages":[{"role":"user","content":"hello"}],"stream":true}')

Path("request.json").write_text(json.dumps(p,ensure_ascii=False))
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/chat/completions \
  -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \
  --data-binary @request.json -D response-headers.txt -o result.sse

Receive and save results

Ailoot Ultra · Chat Completions

JSON or text/event-stream

Keep all completed results

Keep every complete returned response, file and content part.

Retain the complete JSON or SSE bytes, response headers, returned usage and all supplied result fields. No model-specific output family is asserted.

If the original response needs checking

Preserve the original response and attempt identity; no new job polling or resubmission is inferred.

Response fields

Field	Type	Meaning
Field`complete response JSON`	Typeobject	MeaningPreserve every returned field without assuming a model-specific result family.
Field`SSE data events`	Typestream	MeaningPreserve every returned event and terminal marker without selecting only text fields.

Aliases

Model aliases

Ailoot Ultra sora-2

Method path aliases

Use the method paths shown above.

Related caller IDs

sora-2

Ailoot Ultra · Anthropic Messages POST /v1/messages sora-2

sora-2

Other /sora-2

Overview

Accepted inputs: Text
Results: json · sse

Available in Ailoot · inputs & methods

Ailoot Ultra · Anthropic Messages POST /v1/messages

Input types: text
Output types: json, sse
Output format: JSON or SSE

Field	Type	Requirement	Values & limits	Default
Field`model`	Type`string`	RequirementRequired	Values & limits sora-2	Default—
Field`messages`	Type`message[]`	RequirementRequired	Values & limits	Default—
Field`messages[].role`	Type`string`	RequirementRequired	Values & limits user, assistant	Default—
Field`messages[].content`	Type`string`	RequirementRequired	Values & limits	Default—
Field`max_tokens`	Type`integer`	RequirementRequired	Values & limits	Default—
Field`stream`	Type`boolean`	RequirementOptional	Values & limits	Defaultfalse

Input material combinations

Text · UTF-8 text

messages[].content string

Method parameters and lifecycle

Parameter	Contract
Parameter`content_type`	Contractapplication/json
Parameter`required`	Contractmodel, messages, max_tokens
Parameter`optional_controls`	Contractstream
Parameter`material_types`	Contracttext
Parameter`text_file_material`	ContractRead the actual UTF-8 document and put its text in the indicated input or message content string.

Lifecycle: synchronous_or_streamed

Pricing

Tariff references do not add request options. Supported parameters are listed for the selected method.

Fast mode: Not specified When fast mode is selected
Flex mode: Not specified When flex mode is selected
Maximum reasoning effort: Not specified When maximum reasoning effort uses the default adjustment

Ailoot rates

Prices by configuration

Configuration	Rate schedule	Charge
ConfigurationBase token rates	Rate scheduleBase rate	Charge Input · Input tokens $0 / 1K tokens Output · Output tokens $0.2 / 1K tokens Input · Cache read $0 / 1K tokens Input · Cache write $0 / 1K tokens Input · Cache write, 1 hour — / 1K tokens

Example requests

Ailoot Ultra · Anthropic Messages

Complete minimal JSON bodycurl · use your UTF-8 documentPython · save the complete result

{
  "model": "sora-2",
  "max_tokens": 128,
  "messages": [
    {
      "role": "user",
      "content": "Summarize the incident report."
    }
  ],
  "stream": false
}

set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
: "${AILOOT_TEXT_FILE:?Set your actual UTF-8 document}"
export AILOOT_TEXT_FILE
python3 - <<'PY_REQUEST'
import json, os
from pathlib import Path

source_file = Path(os.environ['AILOOT_TEXT_FILE'])
if not source_file.is_file():
    raise SystemExit('Set AILOOT_TEXT_FILE to your actual UTF-8 document')
text = source_file.read_text(encoding='utf-8')
if not text.strip():
    raise SystemExit('Choose a document containing text')
payload = {'model': 'sora-2', 'max_tokens': 128, 'messages': [{'role': 'user', 'content': 'Summarize the incident report.'}]}
payload['messages'][0]['content'] = 'Summarize this material and quote supporting source passages.\n\n' + text
Path('request.json').write_text(json.dumps(payload, ensure_ascii=False), encoding='utf-8')
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/messages \
  -H "x-api-key: $AILOOT_API_KEY" -H 'anthropic-version: 2023-06-01' -H 'Content-Type: application/json' \
  --data-binary @request.json -D response-headers.txt -o result.json
python3 - <<'PY_RESULT'
import json
from pathlib import Path

result = json.loads(Path('result.json').read_text(encoding='utf-8'))
print(json.dumps(result, ensure_ascii=False, indent=2))
PY_RESULT

import json, os
from pathlib import Path

source_file = Path(os.environ['AILOOT_TEXT_FILE'])
if not source_file.is_file():
    raise SystemExit('Set AILOOT_TEXT_FILE to your actual UTF-8 document')
text = source_file.read_text(encoding='utf-8')
if not text.strip():
    raise SystemExit('Choose a document containing text')
payload = {'model': 'sora-2', 'max_tokens': 128, 'messages': [{'role': 'user', 'content': 'Summarize the incident report.'}]}
payload['messages'][0]['content'] = 'Summarize this material and quote supporting source passages.\n\n' + text
from urllib.request import Request, urlopen
from urllib.error import HTTPError

api_key = os.environ['AILOOT_API_KEY']
if not api_key.strip():
    raise SystemExit('Set AILOOT_API_KEY before making a request')
headers = {'x-api-key': 'PLACEHOLDER_KEY', 'anthropic-version': '2023-06-01', 'Content-Type': 'application/json'}
headers['x-api-key'] = api_key
request = Request('https://api.ailoot.ai/v1/messages', data=json.dumps(payload, ensure_ascii=False).encode('utf-8'), headers=headers, method='POST')
try:
    with urlopen(request, timeout=120) as response:
        raw = response.read()
        Path('response-headers.txt').write_text(str(response.headers), encoding='utf-8')
except HTTPError as error:
    Path('result.json').write_bytes(error.read())
    Path('response-headers.txt').write_text(str(error.headers), encoding='utf-8')
    raise
Path('result.json').write_bytes(raw)
import json
from pathlib import Path

result = json.loads(Path('result.json').read_text(encoding='utf-8'))
print(json.dumps(result, ensure_ascii=False, indent=2))

Receive and save results

Ailoot Ultra · Anthropic Messages

JSON or SSE

Keep all completed results

Keep every complete returned response, file and content part.

Keep all content blocks, thinking signatures and actual tool-use IDs. Assemble all SSE block deltas; a first text block is not the complete output.

If the original response needs checking

Keep request/response IDs and headers. No generic text job retrieval URL is supplied.

Response fields

Field	Type
Field`id`	Typestring
Field`model`	Typestring
Field`content[]`	Typetext\|thinking\|tool_use\|other content block
Field`stop_reason`	Typestring\|null
Field`usage`	Typeobject

Errors and next steps

Response	Condition	Next step
Response400 · `invalid_request_error`	ConditionInvalid required fields, material representation or parameter value	Next stepCorrect the indicated fields before a new creation request.

Aliases

Model aliases

Ailoot Ultra sora-2

Method path aliases

Use the method paths shown above.

Related caller IDs

sora-2

FAQ · sora-2

What inputs and results are available?

POST /v1/chat/completions · sora-2: text → json, sse

POST /v1/messages · sora-2: text → json, sse

Which fields does the request use?

POST /v1/chat/completions · sora-2: model, messages, stream

POST /v1/messages · sora-2: model, messages, max_tokens, stream

sora-2

sora-2

Describe a shot that can be seen and heard

Direct dialogue and sound separately

Size, duration and an image-guided opening

Reusable non-human characters

Continue or edit a completed clip

Render jobs and the finished video

Overview

Available in Ailoot · inputs & methods

Pricing

Ailoot rates

Prices by configuration

Example requests

Ailoot Ultra · Chat Completions

Receive and save results

Ailoot Ultra · Chat Completions

Keep all completed results

If the original response needs checking

Aliases

Model aliases

Method path aliases

Related caller IDs

Overview

Available in Ailoot · inputs & methods

Pricing

Ailoot rates

Prices by configuration

Example requests

Ailoot Ultra · Anthropic Messages

Receive and save results

Ailoot Ultra · Anthropic Messages

Keep all completed results

If the original response needs checking

Aliases

Model aliases

Method path aliases

Related caller IDs

The company and its project portfolio

Buy tokens at a discount.

Connect the API to a product you sell.