Two documented off-switches, held by different people

Two entries here publish a switch for the visible mark. One is a boolean in the API request, held by whoever writes the call; the other is a toggle beside the model selector that only paid members have. From 2 source pages, read 2026-10-13 to 2026-10-25; no maker pays to be listed.

Fig. 1 Same column, different hands, opposite defaults.

The two entries on one question at a time, in each vendor's own terms. Recorded 2026-10-25.
On this question	Wan	SceneMixer
Where the control lives	In the request body	Beside the model selector
Who exercises it	An integrator writing the call	A paid member producing the work
Documented default	False, so nothing is applied	On, so the badge is applied
Stated reason	None published	Named rules for a two-layer mark
What stays on regardless	Nothing documented	An invisible watermark, per the terms

Inclusion rule. One row per question on which these two entries can be compared from their own published pages. Questions neither vendor addresses are left out rather than filled with a dash. Order. Fixed order: the mechanism first, then who holds it, then what it leaves behind.

Where each value above was read, and what the register records in the user toggle column. Recorded 2026-10-25.
Generator	User toggle	Document read
SceneMixer	Plan benefit, a switch for paid members	terms of service
Wan	A request parameter, not a plan	text-to-video API reference

Inclusion rule. The two entries on this page, with the value each one's own pages support in the column they diverge on. Order. Alphabetical by generator name.

1Who holds the switch

On one entry the switch is a field in a request, so it is held by whoever writes the integration and is set once in code. On the other it is a toggle in the product, held by a paid member and set render by render while the work is being made.

Neither is held by the person who receives the file, which is the part a downstream platform should notice: the decision is taken upstream, by different people on each side.

2Defaults that point opposite ways

The request field defaults to false, so a caller who does nothing gets no mark. The toggle defaults to on, so an operator who does nothing ships a badge, and a free account cannot change it.

A file from the first arrives clean unless someone asked for a mark; a file from the second arrives badged unless a member took it off. Which of those a production is receiving is a question to settle before footage is collected.

3What neither switch touches

The integrator's field governs the only mark that entry documents. The paid member's toggle governs the visible badge only: the terms say an invisible, compression-resistant watermark or content credential stays on every output, which is the layer a platform's software would look for.

4Sources

Paid tier
The 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 offModel Studio, text-to-video API reference / since 2026-09-22 / checked 2026-10-25
User toggle
Paid members can switch the badge off for later renders; the terms make removing the visible label an optional paid feature where the law permitstied to a paid membershipSceneMixer, terms of service / recorded 2026-10-13
Machine-readable marking
An invisible, compression-resistant watermark or content credential is applied to output and never removedstated in the termsSceneMixer, terms of service / recorded 2026-10-13

Both values above are read from the vendor pages linked in the rows: alibabacloud.com and scenemixer.com, on 2026-10-25. Each entry has its own page, Wan and SceneMixer, and the rule for the column they diverge on is on the control column page. Other pairs: buying later, or not, the first payment.