GateTrue

What each generator documents about marking its output

Developer references, where a parameter is the answer

Two generators here are read from developer documentation. In that genre the marking answer stops being a tier and becomes either a request field with a published default or a sentence under a heading called Limitations. From 3 source pages, read 2026-09-22 to 2026-10-25; no maker pays to be listed.

A field with a published default, beside a sentence under LimitationsThe Wan reference documents a boolean watermark field that defaults to false and adds the words AI Generated in the lower-right corner when set to true. The Veo documentation has no field at all and says under Limitations that videos are watermarked using SynthID.What the developer documentation gives the callerWan, text-to-video referenceA request fieldA boolean watermark parameter, publishedas defaulting to false.Veo, model documentationA statement of factWatermarked using SynthID, stated underLimitations, with no parameter thatchanges it.Neither document says anything about files already downloaded
Fig. 1 One reference gives the caller a choice; the other states what the output will carry whatever the caller sends.
Generators read from developer documentation, with the control that documentation describes. Read 2026-09-22.
GeneratorWhat the reference says the caller controlsDocument read
VeoNot documentedVeo API documentation
WanA request parameter, not a plantext-to-video API reference

Inclusion rule. Generators whose recorded control or marking value comes from an interface reference written for a caller rather than for a buyer. Order. Alphabetical by the name in the first column.

1A default is a stronger statement than a benefit

Wan's text-to-video reference lists a boolean field named watermark and says it defaults to false, adding that setting it true puts the words AI Generated in the lower-right corner. That is a more precise claim than any pricing grid on this site makes. It names the mechanism, the default state, the text and the corner, and it does so in a document whose whole purpose is to be exact about inputs.

It is also a claim with a narrower scope than it first appears. The reference describes the API surface and says nothing about the vendor's own generation page, and the guide that once described a stamp there has been replaced by an overview that is silent on it. Only a reference document is granular enough to show where a statement stops.

2Limitations sections are where a mark gets mentioned

Veo's documentation has no parameter for marking at all. The statement appears instead under Limitations: videos created by Veo are watermarked using SynthID, and they can be verified using the SynthID verification platform. Two sentences, no tier, no switch, and no indication that any caller input changes the outcome.

Filing that under Limitations rather than under Features is itself a reading worth recording. The vendor is telling a developer what the output will carry regardless of how it is requested, which is the same grammar a rate limit is written in. On this register that lands as a filled machine-readable cell and an empty control cell, which is a shape no pricing grid produces.

3What a reference still leaves open

Neither document says anything about how the mark behaves after the response is downloaded. Wan names the corner and the words but not the size or the opacity; Veo names the scheme but not the fields it writes. A reference describes the boundary between the caller and the service, and both marks live on the far side of that boundary once the file is in hand.

The practical consequence is that these two rows tell an integrator what to send and tell a publisher almost nothing about what to expect in an editor. That split is why the register keeps the control column apart from the machine-readable one instead of collapsing both into a single question about removability.

4What the delivered file carries

Next to the marking question in “Developer references”, SceneMixer's pages describe its output like this:

It becomes a marked line — inner voice or narration — so it is heard while the picture shows something worth watching, rather than becoming a shot of somebody thinking.

SceneMixer, AI Dialogue Generator — “What happens to inner monologue from a novel?” (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
  • Control
    Not documented on the vendor's public pages (as of 2026-10-25)nothing published about a console switch: the earlier statement is no longer on the pageModel Studio, video generation and editing guide / recorded 2026-10-25
  • Machine-readable marking
    Videos created by Veo are watermarked using SynthID, described as the vendor's tool for watermarking and identifying AI-generated contentstated under LimitationsGemini API, Veo documentation / recorded 2026-09-22
  • Detection
    Videos can be verified using the SynthID verification platforma named platformGemini API, Veo documentation / recorded 2026-09-22

Every line above is read from the document named beside its row, on 2026-09-22. The same values in their register form are on the support table, and the rules for what a cell may hold are on the what earns a row page. Other kinds of source document: model cards, operator guides.