Verification platform: a named place to check a file
A verification platform is a named service for checking whether a file carries a scheme's signal. Naming one is what turns a claim about output into something the holder of a file can act on. As of 2026-09-22.
| The term | Verification platform |
|---|---|
| What it names | A named service for checking a file against a scheme |
| What it is not | A general test for whether video was machine-generated |
| Where the register uses it | Two entries' detection facts |
Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.
1Why naming a platform matters as much as naming a scheme
A scheme tells a reader what is supposed to be in a file. A platform tells them how to find out whether it is. Two entries in this register name both, and one names a scheme while describing its detection tooling as internal, which is the same kind of claim with a different value to a recipient.
That is why marking and detection are recorded as separate facts. A filled file-contents cell says something is in the file; only a named route says anybody other than the vendor can find it.
2What a platform answers, and in which direction
Finding a signal establishes what the scheme says it establishes. Not finding one establishes nothing: the file may never have been marked, may have been marked by another vendor's scheme, or may have lost an attached record in ordinary handling.
So a negative result is not evidence a file is genuine. One vendor here publishes that caveat about its own credentials in as many words, and it is the sentence a reader should carry away from this whole subject.
3What none of the named platforms covers
Another vendor's mark. Every detection route in this register checks its own scheme, so there is no published cross-checking of any kind and no single place to take a file of unknown origin.
Which means a publisher handed unattributed footage has to guess which vendor made it before choosing a checker, and a wrong guess produces a negative result that means nothing. The routes are useful when provenance is already suspected and weak when it is unknown.
Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the user toggle column, source documents. Nearby terms: public reader, internal detection, metered access.