An exhaustive reference and a card, on file contents
Both entries are read from technical documents. One enumerates every request and response field and names no provenance field at all. The other names an invisible watermark and a credential standard. As of 2026-09-22.
| On this question | Wan | Amazon Nova Reel |
|---|---|---|
| Document read | An API reference and a console guide | A service card and a user guide |
| File contents | Nothing listed among the fields | An invisible watermark plus credentials |
| Visible mark | Text and corner both published | Nothing published |
| Control | A boolean in the request, default false | Nothing published |
| Durability caveat | None | A check works unless metadata was removed |
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.
| Generator | Machine-readable marking | Document read |
|---|---|---|
| Amazon Nova Reel | Invisible watermark plus C2PA Content Credentials | AI service card |
| Wan | Not documented | video 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 silence that means more than usual
Nine rows in the file-contents column are empty because a pricing grid had no reason to discuss the inside of a file. One of these two entries is empty for a stronger reason: the document is an interface reference whose purpose is to enumerate what a caller sends and what comes back, and no provenance field appears in it.
The other entry is the counter-example that makes the point. It is also a technical document, and it names an invisible watermark applied to all output and, on the later model version, Content Credentials built on a named standard and carrying the model and platform used. Same genre, opposite cells.
2Each one is unusually precise about the column the other leaves empty
The reference publishes the text of its visible stamp and the corner it occupies, which is the most detailed visible-mark statement in the register, and a boolean field with a published default for switching it. The card publishes nothing about the frame at all and nothing about control.
So between them the two entries fill all four columns and neither fills more than two. A reader who wants a product that documents both the frame and the file is choosing from an empty set across the whole register, which is the more useful finding than either row alone.
3What an integrator can promise on each
On the reference-read entry the entire published answer to whether output can be identified as generated is to set the stamp field to true. Nothing invisible is described, no standard is named, and the console route stamps unconditionally, which the vendor attributes to compliance requirements.
On the card-read entry the answer exists whether or not the caller does anything, and one of the two layers can be checked with publicly available tools. The same vendor also publishes the limit of that mechanism, which no other vendor here does.
4Sources
- Machine-readable markingNot documented on the vendor's public pages (as of 2026-09-22)not listed among the parameters or the response
- Machine-readable markingAmazon Nova Reel 1.1 adds Content Credentials to videos it generates, built on the C2PA specification, carrying the model and the platform used to generate the videostandard named
Both values above are read from the vendor pages linked in the rows: alibabacloud.com and docs.aws.amazon.com, on 2026-09-22. Each entry has its own page, Wan and Amazon Nova Reel, and the rule for the column they diverge on is on the machine-readable marking column page. Other pairs: trial output, two shapes, a reason, or no route.