AllocateKimi K2.5 vs Vidu 2.0
Vidu 2.0 is not currently in the Allocate serving catalog, so this page lists no prices for it: every price on this site comes from the live catalog.
Kimi K2.5V Vidu 2.0LabTogethercomputerVidu
AccessOpen weightsNot served on Allocate
Context window256K tokensn/a
List price, input$0.5 / M tokensNot served
List price, output$2.8 / M tokensNot served
Cached inputn/an/a
LicenseNot listedProprietary API
Fine-tunableYesNo
Specifications and provider list prices from the Allocate catalog, checked 2026-09-12.
Choose Kimi K2.5 for
- Whole-document reasoning
- Long-context retrieval
- Open-weight fine-tuning
Common questions
Which has the bigger context window?
Kimi K2.5: 262,144 tokens (256K) against an unlisted window for Vidu 2.0.
Can I fine-tune Kimi K2.5 or Vidu 2.0?
Kimi K2.5 publishes open weights (Not listed) and can be fine-tuned on your own data. Vidu 2.0 is a closed model served over API; its weights are not available.
Related comparisons
Kimi K2.5 vs MiniMax M3Vidu 2.0 vs MiniMax M3Kimi K2.5 vs Meta Llama 3.3 70B Instruct TurboVidu 2.0 vs Meta Llama 3.3 70B Instruct TurboKimi K2.5 vs Deepseek V3.1 NVFP4Vidu 2.0 vs Deepseek V3.1 NVFP4
Run the numbers on your workload
Or do not choose. On Allocate a route name is the contract: point yours at one model today, swap to the other tomorrow, and compare them on your live traffic with per-token metering.