Notarization records the identity of existing content and, optionally, the people who attest to that same identity. Agreebase does not need to receive the source file.
Choose the content mode
File
Pick a file and Agreebase hashes it with SHA-256 right there in your browser, before anything is sent anywhere. Only the resulting digest, plus a filename or label and optional advisory size and MIME type, is submitted. Agreebase stores that hash and metadata; it never receives the file bytes, its local path, file dates, EXIF data, or the file itself, so there's nothing to notarize a wrong version of by mistake and nothing incidental about your file to leak.
Text
Paste or type the text directly. Agreebase normalizes it; Unicode NFC, line endings converted to LF, outer whitespace trimmed; the same way every time, so the same words always hash to the same digest regardless of which device or editor produced them. See Verification hashes if you want the exact normalization steps for reproducing a hash yourself. Text is limited to 64 KB after normalization.
You can choose whether the normalized text may be published publicly. Public text publication is limited to 300 words and, like any blockchain write, is permanent once it confirms.
Existing hash
If you already have a SHA-256 digest; computed by another system, or one you want to keep entirely outside Agreebase; submit just the digest with a label or filename. Agreebase never sees or asks for the underlying content in this mode.
Add co-notarizers
The creator can invite up to fourteen co-notarizers. Each co-notarizer signs the same content hash. The creator cannot add their own verified contact point as a co-notarizer. Co-notarizers do not receive the source file from Agreebase.
If a co-notarizer declines, the notarization remains pending. The creator can complete without that co-notarizer from the record page. Each decline is resolved separately, and all other active co-notarizers must still sign before sealing. The creator can instead rescind the pending notarization, which ends signing for every co-notarizer and notifies all invited participants without creating a sealed or blockchain record.
Choose signing behavior
pending_signature starts a normal signing workflow. auto_seal can be used with direct API-key authentication when one signature method is required; it can seal immediately when there are no co-notarizers. With co-notarizers, the record remains pending until they complete their signatures.
Notarization signatures use the same proof-of-control methods as other records. See Signing methods.
What is produced
A sealed notarization email contains a notarization payload, content hash, evidence metadata, blockchain commitment, and private share card. It does not generate a signed PDF. Verification accepts the content hash, normalized text where text was retained, and the blockchain transaction hash.
See Verify a record for browser verification. For file notarizations, the browser hashes the selected local file and submits only the digest.