SHA-256 is a fingerprint function. You give it a file. It gives you a 64-character string. Change one character in the file and the string changes. You cannot usefully work backwards from the string to the file.
On AI Verified, that string is the public address of a business identity record. The page is /v/ plus the hash. The machine copy is the same path with .json.
Why a fingerprint instead of a pretty URL
A slug like /roofers/miami/best-company can be edited later. The reader cannot see that the document moved. A hash is ugly on purpose. If the facts in the file change in a way that changes the canonical document, the fingerprint changes. The old address still points at what it pointed at.
That property is why software teams use SHA-256 for packages and why this registry uses it for identity files. It is the same family of tools described on SHA-2 and in Wikidata Q13425597.
What the hash proves
It proves integrity: this text, hashed this way, produces this string. It proves a moment: the file looked like this when the hash was issued.
It does not prove the government typed the numbers. It does not prove the owner is good at the trade. It does not prove ChatGPT will cite the page. A filing number on the file is still a report until you open the issuing register.
How it shows up for an owner
Bronze and Gold records both get a hashed URL. Gold adds the seal, the short link, and a playbook for putting that URL in press, citations, and the site the owner controls. The hash is not the product you sell at dinner. The file is. The hash is how you know the file was not silently rewritten.
If two copies of a JSON file hash to the same string, they are the same document. If they do not, someone changed a field. That is the whole operational use.
Related
Digital business passport · Cryptographic business verification · What AI Verified is · How to use the file