Chinese model APIs on one OpenAI-compatible key. Browse models
AI video generation API topic mark covering Wan, MiniMax and HappyHorse
Wan · MiniMax · HappyHorse

Integrating catalog · not Live media

AI video generation API: track Wan / MiniMax / HappyHorse without lying about Live

Overseas “text to video API” traffic often wants Chinese families first. This page exists so you can plan product, SEO and engineering against Integrating rows — and keep Live DeepSeek text for everything that must work this week.

Why this topic is a status page, not a media SDK

Publishing fake Live video endpoints burns trust faster than ranking. The useful artifact is a shared catalog of Integrating IDs, family hubs, and engineering rules that refuse Chat Completions for frames.

When status flips to Live, this page should grow media docs and billing units — not pretend the chat route suddenly returns MP4s.

Catalog status

Catalog modelAPI IDVendorStatusDetail
Wan Text-to-Videowan-t2vAlibaba CloudIntegratingOpen
MiniMax Video-01minimax-video-01MiniMaxIntegratingOpen
HappyHorse Text-to-Videohappyhorse-t2vAlibaba CloudIntegratingOpen

All video rows above are Integrating. Do not send production render jobs.

Family comparison

DimensionWanMiniMax Video-01HappyHorse
Primary jobText-to-video demand around QwenVideo-01 media + separate text agentsNamed Integrating media row
Hub home/models/qwen/models/minimax/models/qwen
Status todayIntegratingIntegratingIntegrating
Do notCall via Chat Completions for framesMix with M2/M3 agent budgetsQueue customer renders
Ship insteadLive DeepSeek text + feature flagLive text + media flagDemand tracking only

Wan (Qwen hub)

Wan text-to-video demand is why many “Qwen API” searches are really video searches. On the Qwen hub, treat Wan as Integrating media inventory — separate from qwen-plus text evals.

Open hub

MiniMax Video-01

MiniMax also sells an agent-coding story (M2/M3). Do not put Video-01 into the same retry and cost alerts as text agents. The MiniMax hub splits those intents on purpose.

Open hub

HappyHorse

HappyHorse is catalogued beside the Qwen vendor filter as Integrating. Use it for demand tracking and naming consistency, not for a production render queue.

Open hub

Engineering rules until Live

  1. 01

    Do not point Chat Completions at video IDs

    Expecting frames from a chat model string is how prototypes lie in demos. Wait for a documented media endpoint.

  2. 02

    Keep the critical path on Live text

    Product logic, agents and support copy stay on DeepSeek Live routes. Video is a feature flag behind status checks.

  3. 03

    Budget media separately

    When Live ships, token-style text budgets will not map cleanly to seconds or frames. Plan a separate wallet line item.

What to ship now

  • Live DeepSeek text for agents, copy and control planes.
  • UI copy that says video is coming / Integrating — never “available now.”
  • Feature flags keyed off GET /v1/models + this page’s status table.
  • Watchlists for Wan / MiniMax / HappyHorse demand without queueing jobs.

FAQ

Can I render Wan or MiniMax video through SmarToken today?
No as Live production media. The catalog lists Integrating rows so product and SEO teams share one status source. Wait for Live + media docs before customer jobs.
Why publish a video page before the endpoint works?
English search demand for AI video generation APIs clusters on Chinese families. A thin “coming soon” spam page fails; a status + decision page that refuses Chat Completions for frames is useful.
Will video share /v1/chat/completions?
Unlikely as the long-term shape. Text chat stays on Chat Completions. Media APIs usually need dedicated endpoints, async jobs and different billing units. Confirm docs when status flips.
What should engineering ship while waiting?
Keep agents, copy and control planes on Live DeepSeek text. Design the product so video is a feature flag, not a hard dependency in the critical path.