Wan hands the decision to whoever sends the request
Wan's API reference documents a boolean watermark field defaulting to false, so a caller decides. The console guide says the same models are always stamped there and cannot be told otherwise. As of 2026-09-22.
| The reading | What it holds |
|---|---|
| The recorded value | A request parameter, not a plan |
| The vendor's own words | A boolean watermark parameter, default false, with the console stamp described as not switchable. |
| How the reading was taken | Read from an API reference for the parameter and a console guide for the restriction. |
Inclusion rule. One row for the value, one for the sentence or absence behind it, one for the method. Nothing here is drawn from output, support replies or coverage by anyone else. Order. Fixed order: the value, then its evidence, then the method.
1Control belongs to a role, not to an account
On the plan-gated rows the person who can change the mark is the person who pays. Here it is the person who writes the request, which in most organisations is not the same person and often not the same department. An integrator can decide what every file carries without touching a subscription.
That is a different kind of exposure. A marking policy enforced through a plan is enforced by procurement; a marking policy enforced through a request field is enforced by whoever last edited the call. Neither is stronger in general, and the second is easier to change and harder to notice.
2Two doors into one product, disagreeing
The console guide says videos generated on its own generation page always carry the stamp and that it cannot be turned off from the console, attributing the restriction to legal compliance requirements. The reference says the field defaults to false. Same models, opposite defaults, and both statements are published.
No other entry in this register documents both sides of such a split. One vendor sells the same models through two routes and does not repeat its marking line on the second; another scopes its mark to downloads from its own surfaces and says nothing about anything else. Here the disagreement is on the record.
3What a default of false implies for anybody downstream
Nothing is applied unless a caller asks for it, which reverses the usual question. Elsewhere this column asks what it takes to remove a mark; here it asks who would add one and why. The answer is the compliance argument the console guide makes, and the API leaves that argument to the caller.
For a receiving party the practical consequence is that a file from this model carries no information about which route produced it. A clean file might have come from a caller who set the field to false or from a caller who never knew the field existed, and those are different situations with the same artefact.
4Sources
- Paid tierThe API request has a boolean watermark parameter that defaults to false; set true it adds a watermark in the lower-right corner with the text AI Generatedthe API surface, default off
- Free tierVideos generated on the Online Experience page of the Model Studio console always carry a watermark: the text AI generated in the lower-right corner of the videothe console surface
The value above is read from alibabacloud.com, the vendor's video generation guide, on 2026-09-22. The whole row for this generator is on its own page, and the rule for what this column may hold is on the control column page. Neighbouring readings: Luma AI, control, Sora, control.