Verifying without us
The point of this page is to make the rest of this portal optional.
The path of verification contains no server of ours
A sealed file carries its own proof: the signature, the certificate chain that attests the key, and whatever timestamp, transparency-log and anchoring evidence was available at capture. Reading all of that is arithmetic over bytes you already hold. If a component of ours were ever necessary to reach a verdict, that would be a design error, not a feature — and it is the one error this product is built to avoid.
Three ways that are not this API
| The page | A static verifier. The file is read in the browser and never leaves it — no upload, no telemetry. Online it reads an anchor from the public chain RPC its trust set lists, and fetches the digest-checked detector when a file needs one; offline it still reaches a verdict, a weaker one. You can host your own copy. |
| The core | The page, this API and the console's own verifier all run one verification core, and it is public and MIT in the verifier repository. Vendor it into your own pipeline and the verdict never depends on our availability. There is a command-line wrapper around it in that repository too, and it is worth saying plainly that it is not published today — no npm package, no release — so it runs from a clone and not from an install. |
| The specification | Public and MIT, with a conformance corpus and a report format for claiming you pass it. Write your own verifier in your own language and check it against the same vectors this sandbox serves. Nothing in that loop is ours except the vectors, and those are public. |
So what is this API for?
One answer a file cannot carry, which can only make a verdict stronger:
- Revocation. Nothing in a proof can demonstrate the absence of a later revocation entry, so an offline verifier correctly stops at revocation not checked. This service runs the transparency log, so it can ask it — and the same file that reads amber offline can read green here. That is the difference, and it is the whole difference.
Convenience is the honest word for the rest: one call instead of a dependency, the chain read for you, a queue for the detector, and usage we account for. None of it is trust you have to extend to us.
If you are building something that must outlive us
Keep the sealed files. They are the evidence — not a verdict we issued, not a report we printed, not a record we kept. A PDF report from this platform is a written account that says so of itself, and a tenant export is an open format with no verdict summarised in it, for the same reason: the thing that proves something is the file, and it verifies without us.