You are holding a file. Did anyone seal it?
Drop an image, a video, a document, anything. It is fingerprinted in this browser and the fingerprint is checked against every sealed declaration on the record. For a picture or a video APIR also measures a pixel fingerprint, so a re-saved or re-encoded copy of a sealed original still points back to it.
Drop files anywhere on this panel, or choose them. Up to 25 at a time. Nothing is uploaded, nothing is stored about the file itself, and you do not need an account to ask.
An agent calls a service on trust. Enter the service’s domain to see whether someone who could make that domain answer has sealed a declaration about it: what it is, what it may do, how it handles data, over its exact spec file.
APIR confirms the domain answered its challenge and seals the declaration. The answer proves control on the date shown, not today: domains change hands, and nothing re-checks them yet. APIR does not test the service, its security or its behaviour, and does not vouch for any response it returns. By the call: GET /api/seal/api?domain=
These exact bytes sit inside a declaration a named person sealed on a date, on a hash-chained ledger an outside authority timestamps nightly. Open it and recompute every hash yourself. What the declaration claims is the declarant's word, not APIR's finding.
A sealed picture measures within ten bits of sixty-four of this one, and the bytes differ. That is a measurement and nothing more. It is what a re-save, a crop, a compression or an edit of the sealed original looks like, and also what an unrelated picture that happens to measure close looks like.
APIR holds no seal over these bytes. That is a fact about the record, not about the file. Almost nothing in the world has been sealed, so an unsealed file is not a fake and this page will never say it is.
A marketplace, a newsroom or a platform running this check at volume can ask the same question over HTTP. No key, no account, the same three answers.