Filter
Remove routes that miss an input, output, audio, duration, or model rule.
One request → five approved routes
Filter by required features and cost. Choose by price, speed, quality, or an exact model. Return the route and charge instead of hiding the decision.
{
"mode": "image_to_video",
"prompt": "Slow product orbit...",
"required": ["first_frame", "audio"],
"route_policy": "lowest_cost",
"allowed_models": ["wan-3", "kling-3", "veo-3.1-fast"],
"fallback_models": ["veo-3.1-fast"],
"max_cost_usd": 0.50
}Saved route policies
A route must satisfy every required feature and the cost cap. Only then can price, speed, or quality decide which eligible model runs.
| Policy | Required fit | Cost cap | Example route |
|---|---|---|---|
| Lowest cost | All required inputs | $0.25 max | Wan 3 |
| Reference-led | Image or media reference | $0.30 max | MiniMax H3 |
| Controlled motion | Image animation | $0.40 max | Kling 3 |
| Native audio | Dialogue and effects | $0.50 max | Veo 3.1 Fast |
| Premium review | Approved high-cost route | $0.70 max | Seedance 2.5 |

Visible routing
The result names the selected model, price, policy, normalized settings, and fallback attempts.
Remove routes that miss an input, output, audio, duration, or model rule.
Price every eligible route before one paid task enters a queue.
Choose by the saved cost, speed, quality, or exact-model policy.
Create one idempotent job and map upstream states into one lifecycle.
Return the model, decision, output, final charge, and attempt trail.
Multi-model API questions
A multi-model video API gives one application access to several video models through one request, job, webhook, and result shape. The caller can name a model or let routing rules choose an eligible one.
Read the full answer →The router first removes models that cannot satisfy the request or cost cap. It then ranks the eligible routes by the chosen policy, such as lowest cost, shortest queue, or preferred quality.
Read the full answer →Yes. Use an allow list for approved models, a deny list for blocked models, or pin one model for a job that must not route elsewhere.
Read the full answer →Fallbacks should run only for approved retryable failures, keep the same idempotent job, respect the cost ceiling, and record every attempted route. Invalid input and policy blocks should not retry another model.
Read the full answer →A useful normalized response includes one job ID, status, selected model, policy, normalized settings, estimate, final cost, output files, error details, timestamps, and webhook version.
Read the full answer →One stable video contract
Primary sources