GateTrue

What each generator documents about marking its output

Two documented off-switches, held by different people

Two entries here publish a control that is not a plan. One is a boolean in the API request, held by whoever writes the call; the other is a switch in settings, held by whoever runs the account. As of 2026-09-22.

What each product does when nobody makes a decisionOne entry publishes a request field that defaults to false, so output is clean unless a caller asks for a stamp. The other documents a setting that is on, so output is marked unless an operator turns it off. The default decides the ordinary case.A field in the requestA switch in settingsDefaultFalse: nothing appliedOn: the mark is appliedHeld byWhoever writes the callWhoever runs the accountReason publishedCompliance, for the other surfaceTwo labels on one frameLeft alone, output isCleanMarkedDefaults decide the cases nobody thinks about
Fig. 1 Two cells that both record a mechanism rather than a price, pointing in opposite directions.
The two entries on one question at a time, in each vendor's own terms. Recorded 2026-09-22.
On this questionWanSceneMixer
Where the control livesIn the request bodyIn the product's settings
Who exercises itAn integrator writing the callAn operator producing the work
Documented defaultFalse, so nothing is appliedOn, so the mark is applied
Stated reasonCompliance, for the console restrictionAvoiding two labels on one frame
Other surfaceThe console always stampsNo second surface documented

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-09-22.
GeneratorUser toggleDocument read
SceneMixerYes, in settingscompliance guide
WanA request parameter, not a planvideo generation guide

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.

1A default of false and a default of on

These two entries answer the control question with a mechanism rather than a price, and then answer it in opposite directions. One publishes a watermark field that defaults to false, so nothing is applied unless somebody asks. The other describes a switch documented as on, so the mark is applied unless somebody intervenes.

Defaults decide what happens when nobody thinks about the question, which is most of the time. A reader comparing these rows on the control column alone would see two similar cells; the useful difference is in which way the product behaves when it is left alone.

2The control belongs to different roles

A request field is edited by whoever maintains the integration, often a developer in a different part of an organisation from the people delivering the work. A settings switch is flipped by whoever is producing. Both are more accessible than a subscription and they are accessible to different people.

That matters when a marking policy has to hold. Enforced through a plan, a policy is enforced by procurement and changes slowly. Enforced through a request field, it is enforced by whoever last edited the call, which is easy to change and easy not to notice.

3Both publish a reason, and the reasons point opposite ways

One vendor attributes an unremovable console stamp to legal compliance requirements, which is an argument for keeping a mark. The other argues for taking it off, because a destination that adds a label of its own would otherwise put two on one frame. Those are the two published rationales in this register.

A stated reason predicts what a change will look like better than a price does. A mark held in place by compliance does not move when a page is redesigned; a mark held in place by packaging does. Neither claim is testable here, and the register notes which vendor said which.

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 / recorded 2026-09-22
  • User toggle
    An AIGC watermark switch in settings turns it offno plan condition statedSceneMixer, compliance guide / recorded 2026-09-12

Both values above are read from the vendor pages linked in the rows: alibabacloud.com and scenemixer.com, on 2026-09-22. 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.