Give every AI creation
a proof trail
The faster agents ship, the more proof matters. Lanveris gives every agent output a verifiable source and time.
Four steps, so outputs can prove themselves
Connect once. Every later agent output can be timestamped, archived, and verified.
→ ok
Connect
Give the setup link to your agent. It installs the tool, registers itself, and gets to work.
Register
When a file is produced, the CLI submits its fingerprint and the metadata needed for the record. Lanveris batches records and writes the credential back.
Records
After login, you can see what each agent registered and copy public verification links.
Verify
Drop a file to query records online. After trust roots are cached once, the CLI can verify credentials offline with one command.
Send one instruction to your agent,
and it handles the rest
Your agent installs the CLI, registers itself, starts timestamping, and gives you a Claim your agent link. No manual setup.
The fingerprint is calculated locally. Your file content never leaves the device.
▶ See how an agent uses it (terminal replay, step by step)
Not platform promises, cryptography and standards
The proof anchors to an international standard, not to a single platform's word.
Files never upload
The fingerprint is calculated locally. The platform receives the fingerprint and the metadata needed to register and verify the record, never the file bytes.
Portable credentials
Each .lanveris file carries the fingerprint, Merkle path, and timestamp response. The CLI can verify it offline after public trust roots are cached.
Trusted time anchor
DigiCert and other timestamp authorities issue RFC 3161 timestamps, the same family of trust used by digital certificates.
Questions about proof
Why is the time trustworthy?
The time is not asserted by Lanveris. It is issued by trusted timestamp authorities such as DigiCert under RFC 3161. Lanveris batches fingerprints into a Merkle tree and timestamps the root, so each record can independently trace back to that timestamp.
Does Lanveris upload my file?
No. The fingerprint is calculated locally. Lanveris receives the fingerprint and the metadata needed to register and verify the record. File content never leaves your device by design.
How can someone else verify my output?
They can use the web verifier to calculate the fingerprint locally and query records online, or use the .lanveris credential with the CLI. Complete offline verification works after Mozilla trust roots have been cached once.
What makes the credential independent?
The credential contains the fingerprint, Merkle path, and timestamp evidence. It anchors to RFC 3161 rather than to a single platform account.
Does this prove legal authorship?
It proves existence, time, integrity, and the registering agent label. Legal authorship and ownership still depend on legal context.