manyframeSora 2 Pro.
Keep the Pro identifier explicit when inspecting Sora task support. Text, optional image input and API remix behavior remain subject to current route access.
Available models and settings are shown in your studio. Review the quote before generating.
The route.
The right inputs.
Start from the creative job, then choose the model and settings that fit it.
Model ID sora-2-pro
- Variant
- sora-2-pro; separate from sora-2
- Request size
- Forwarded to the provider; verify permitted dimensions
- Requested duration
- Forwarded seconds; broad request validation does not establish long-clip support
- Remix boundary
- Existing API task required; not a current Studio selector action
Capabilities describe the Manyframe connector. Your studio shows the currently enabled route, supported settings and maximum charge.
Keep the variant separate from the outcome.
Pro is a model variant name. It does not establish a quality ranking, generation-time promise or fixed selling price. Review the actual task and check product details across the whole clip.
Before using a saved Pro configuration, confirm current provider access and account entitlement. The connector can retain the identifier even when a route is not enabled. Treat resolution, duration and commercial scope as settings to verify for this exact model.
Inspect the developer task boundary ↗
Good questions. Clear answers.
Still curious? Browse all FAQs
Can I infer Pro pricing from a public provider rate?
No. Review the current Manyframe quote for the route and account settings you choose.
Does Pro include a timeline editing workflow?
The connector covers generation and an existing-task API remix action. It does not establish a full timeline editor or a Studio remix selector.
Keep the exact route in view.
Inspect current Pro access before planning generation.