GateTrue

What each generator documents about marking its output

Products documented on more than one surface, as read in September 2026

In September 2026 three entries could be reached more than one way. One published a marking statement for each route and the two disagreed; one published one for its plans only; one scoped its statement to a route. The first entry's console statement is no longer on the page, so the finding is a dated record. From 2 source pages, read 2026-09-12 to 2026-10-25; no maker pays to be listed.

Two doors into one model, and what is published about eachIn September, where both routes were documented an integrator could plan around a difference in defaults. Where only one was, the second route was an open question that no published page closed. In neither case does the delivered file record which route produced it.Both documented, inSeptemberA console that stamped, a fieldthat defaulted to falseTwo published statementsA split an integrator couldplan aroundOne documentedPlans remove the mark; theinterface pages are silentOne published statementAn open question about theother routeScoped to a routeDownloads from the vendor's ownsurfacesA statement with an edgeOther routes neitherincluded nor excludedThree ways of documenting more than one doorNo file from any of the three records which door it came through
Fig. 1 The first column is the September reading; the entry behind it is now documented on its API route only.
The rows this finding rests on, with the value each one's own pages support. Recorded 2026-10-25.
EntryFree tierDocument read
RunwayNo watermark-free output listedpricing page
SoraVisible moving watermark on downloadsSora 2 system card
WanNot documented now; in September a console that always stamped, and an API field defaulting to falseText-to-video API reference; the earlier video generation guide has been replaced

Inclusion rule. Entries whose pages show that the same models are reachable through more than one surface, whether or not a marking statement is published for each of them. Order. Alphabetical by generator name.

1The route can decide what the file carries

In September one entry stated it outright: its console guide said the console always stamped videos in the lower-right corner and that the stamp could not be switched off there, while its API reference published a watermark field defaulting to false. Same models, opposite defaults, both statements on the vendor's own pages.

The second publishes watermark-free output as a plan feature and does not repeat the line on its interface pricing pages. The third scopes its visible mark to downloads from the vendor's own website and app, which is a route rather than a product, and does not address any other.

2What the October reading changed

The console guide has since been replaced by a general overview of video generation and editing, which carries no statement about a console stamp. The register now records only the API field for that entry, and its console cells as not documented. The other two entries are unchanged.

That removes the one case in which both routes were documented. The finding it supported, that a documented disagreement is worth more than silence, is kept below as it was argued in September, with the evidence it rested on marked as no longer on the page.

3Why a documented disagreement beats silence

An integrator who knows the two routes differ can plan around it: label the pipeline, decide which door production uses, and expect stamped files from the other. An integrator on a product whose second route is undocumented has an open question and no way to close it from published pages.

The register records only what is published, so silence about a second route stays silence. It does not become the same statement as the first route by implication, however reasonable that inference would be, because the September reading showed that the inference can be exactly wrong.

4From the production side

Next to the marking question in “Products with two doors”, SceneMixer's pages describe its output like this:

The product image is always redrawn from your original photo so it stays your product.

SceneMixer, Ad Projects and Remake Projects: What Looks Different in the Wizard and the Editor, and Why — “Can I redraw the product from text?” (read 2026-10-13)

Every new video carries the SceneMixer AIGC badge in its bottom-right corner unless you turn it off.

SceneMixer, The AI Badge Switch (read 2026-10-13)

5Sources

  • 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
  • Machine-readable marking
    Not documented on the vendor's public pages (as of 2026-09-12)not mentioned on the pricing pageRunway, pricing / recorded 2026-09-12

Every row above is read from the vendor page named beside it, on 2026-10-25. The same values in register form are on the support table, the rule for this column is on the free tier column page, and what may fill a cell at all is on the what earns a row page. Other findings: durability caveats, the spread of prices.