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. As of 2026-09-22.
| Generator | What the reference says the caller controls | Document read |
|---|---|---|
| Veo | Not documented | Veo API documentation |
| Wan | A request parameter, not a plan | video generation guide |
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 same models reached through the Model Studio console are stamped and the page says the stamp cannot be turned off there, attributing that to legal compliance requirements. One vendor, two surfaces, opposite defaults, and only a reference document is granular enough to show it.
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.
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
- ControlThe console watermark cannot be turned off from the console UI, which the page attributes to legal compliance requirementsno switch on the console surface
- Machine-readable markingVideos created by Veo are watermarked using SynthID, described as the vendor's tool for watermarking and identifying AI-generated contentstated under Limitations
- DetectionVideos can be verified using the SynthID verification platforma named platform
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.