<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wanxiang on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/wanxiang/</link><description>Recent content in Wanxiang on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 28 Feb 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/wanxiang/index.xml" rel="self" type="application/rss+xml"/><item><title>Aliyun Bailian (4): Wanxiang Video Generation End-to-End</title><link>https://www.chenk.top/en/aliyun-bailian/04-wanxiang-video-generation/</link><pubDate>Sat, 28 Feb 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/aliyun-bailian/04-wanxiang-video-generation/</guid><description>&lt;p>Wanxiang is the API that has done the most for our marketing pipeline and caused the most production surprises. The model is genuinely good — &lt;code>wan2.5-t2v-plus&lt;/code> produces 720p clips that pass for an actual video team&amp;rsquo;s output most of the time — but the surface around it is async, native-protocol, has expiring URLs, and rate-limits in non-obvious ways. This article is the version of the docs that has been through six months of &amp;ldquo;why is this happening at 2am&amp;rdquo; tickets.&lt;/p></description></item></channel></rss>