Status, model and resolution are separate fields
The most important part of a ModelArk verification result is whether an official artifact signal was found. Model name and resolution are additional fields. They may be present when the provider can recover them, but a response does not have to include every detail to report a positive match.
The interface therefore displays “Not returned” rather than inventing a model or inferring resolution from the uploaded file. That distinction preserves what the official service actually said.
Never translate a missing ModelName field into “not Seedance.” Check the official-match and task-status fields first.
Common reasons optional details are absent
Different model versions, generation paths and verification regions may return different levels of detail. A file can also retain enough provenance data for an official match while losing the portion that identifies a model or resolution.
Editing, transcoding, trimming, container conversion and platform compression can change what remains readable. The verification endpoint may also evolve independently of this site, so the UI must tolerate responses that contain fewer fields than earlier examples.
- The provider confirmed the artifact but omitted optional detail fields.
- The video was processed after generation and only part of the signal remains.
- One verification region returned richer information than the other.
- The upstream response uses a new or less common field layout.
File resolution is not the same as verified generation resolution
It is technically easy to read the width and height of the submitted file. But that value may describe a later export, crop or upscale rather than the resolution produced by Seedance. Showing it as an official generation resolution would be misleading.
Seedance Check reports resolution in the official result area only when it is returned as provenance information. If you need the current file dimensions, inspect them separately and label them as properties of the submitted copy.
How to interpret the combinations
A positive official match with no model or resolution is still a provenance signal, but it supports a narrower statement: the file carries official ModelArk-related signals, while the exact model and original output size are unknown.
A completed task with no official match and no detail fields is a non-match, not a universal AI verdict. An incomplete or failed task is inconclusive and should be retried only after fixing the file or URL problem.
Official references
This guide is based on the public ModelArk artifact-verification workflow. The provider documentation remains the source of truth for endpoint behavior.