Documents carry a verify: line pointing at the issuer's domain, e.g.
verify:issuer.example.com/claims. Clip mode: select the text. Camera mode: snap and OCR it.
Either way, the text is normalized, hashed with SHA-256, and looked up at the issuer's URL. You decide upfront whether that domain is an authority on the claim.
1
Get text
Select (Clip) or snap & OCR (Camera).
2
Normalize
Apply text normalization rules locally.
3
SHA-256
Hash the normalized text.
4
Verify
GET the issuer URL; 200 = status returned (OK / REVOKED / etc.), 404 = not found.
What problems does this solve?
... use cases
across ... categories
Fraud, safety, security, compliance, authenticity — unverified documents cause harm across every sector. We've mapped the landscape:
Verified means: the domain in the verify: line currently attests to the hash for the extracted text above it.
It is not "ground truth": the issuer can be wrong, malicious, or out-of-date.
The human decides whether that domain is an authority for the claim in question.
Look out for lookalike/typosquatted domains: while much of verification is automated the domain should be shown prominently for humans to judge or not as part of a "trust or don't trust" decision.
Verifications are revocable
Revocation is part of trust. Issuers can update or withdraw claims over time, so the result reflects what they stand behind today.
Some issuers may return an operational instruction, e.g. Stolen ID — please retain/cut in half and contact https://example.com/stolen_and_found quoting reference 283762..
Simulated integration tests
Screenshots captured by Playwright during automated tests against simulated authority chains in Docker. All organisations and people are fictitious. The Chrome extension is being itself or simulating something built-in to Outlook, Adobe or operating systems.
Text normalization + SHA-256 happen on-device (Clip mode never sends your text anywhere; Camera mode runs OCR on-device too). The only network step is a hash lookup. The science of one-way hashes is explained at
one-way-hash.html, and we go into the rest of the guarantees in the
Privacy Declaration.