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
Use the original file and .lanveris credential for full verification, or use only the file to query the current online record.
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 created locally; the original file is not uploaded during registration or verification.
▶ See how an agent uses it (terminal replay, step by step)
Trusted time issued externally, managed and verified by Lanveris
An independent timestamp authority issues the trusted time. Lanveris handles registration, management, sharing, and verification.
Original files stay local
Registration and verification create the fingerprint locally. The platform receives the fingerprint and the metadata needed to operate and verify the record.
Credentials stay with the file
A .lanveris credential can be archived and delivered with the original file, then verified through Lanveris or the official CLI.
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 issued by trusted timestamp authorities such as DigiCert under RFC 3161, rather than being an ordinary database time written by Lanveris. Lanveris manages the registration and verification record.
Does Lanveris upload my file?
The original file is not uploaded during registration or verification. Its fingerprint is created locally, and Lanveris receives only the fingerprint and the metadata needed to operate and verify the record.
How can someone else verify my output?
Deliver the original file together with its .lanveris credential. The recipient can run full verification on Lanveris. If they only have the original file, they can query the current online registration by its locally calculated fingerprint.
Why are there both verification links and credentials?
A verification link is for querying and sharing the Lanveris online record. The .lanveris credential stays with the original file for archiving and delivery, and can be checked through Lanveris or the official CLI.
Does this prove legal authorship?
It records that the fingerprint was registered no later than a trusted time, whether the current bytes still match, and the Agent label used at registration. Legal authorship and ownership still depend on the wider evidence and legal context.