AI video answer
Can I choose which video models a router uses?
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.
Build an approved model pool
Define which models each product, customer, region, input mode, or workflow can use. The router should never add a route outside that approved pool.
Keep separate policies when draft jobs and final exports need different models or cost limits.
Pin exact-model work
Use a direct model ID when the customer bought a named model, a test must be repeatable, or the result must match an earlier workflow.
A pinned request should fail clearly when that route is unavailable instead of silently changing the model.
Change policy without rewriting the app
Saved routing rules let the model pool, order, and cost ceiling change while the application continues calling one contract.
Return the policy version with each job so old and new decisions can be audited.
Related guide
Get the full context.
Multi-model video API for routing, fallbacks, and cost control
Use one multi-model video API for capability routing, approved fallbacks, cost caps, normalized jobs, webhooks, and results across five AI video models.
Read the multi model video API guideCurrent prices
Compare each video route.
| Model | Compared rate | Cre8vid price | 5 sec | 10 sec | Savings |
|---|---|---|---|---|---|
| MiniMax H3MiniMax | $0.065 | $0.029 | $0.145 | $0.29 | 55% less |
| Wan 3.0Alibaba | $0.050 | $0.025 | $0.125 | $0.25 | 50% less |
| Kling 3.0Kuaishou | $0.084 | $0.039 | $0.195 | $0.39 | 54% less |
| Seedance 2.5ByteDance | $0.144 | $0.069 | $0.35 | $0.69 | 52% less |
| Veo 3.1 Fast + audioGoogle | $0.100 | $0.049 | $0.24 | $0.49 | 51% less |
Source notes