The web app is the simplest way to create an agreement, declaration, or witnessed agreement. The flow helps you define the text, review it, choose participants and publication settings, complete the initiator signature, and invite the remaining people.
1. Choose the record and draft the text
Start by choosing an agreement, declaration, or witnessed agreement document type. Write the substance in plain language. For an agreement, include the parties, obligations, dates, amounts, conditions, delivery details, and consequences the user actually intends to record.
An agreement is a contract; Agreebase brings the power of the contract into simple, everyday agreements between parties, so when writing your agreement it's useful to think of exactly what is being agreed and any important details that need to be captured.
If you are unsure how to write the agreement or declaration, click the "Draft it for me" button to open the smart-template assistant, which asks structured questions and produces a draft for you to check and edit. See Drafting with the smart-template assistant for what it asks and what to check before continuing.
Agreements and declarations are limited to 350 normalized words or approximately 7,000 characters. The limit applies across the browser, REST, and MCP creation paths.
2. Review the text and legally-binding signals
Agreebase can optionally analyze the draft for missing or unclear material elements that might undermine its legal intent; not legal advice, but a strong signal on whether your draft looks complete for the jurisdiction you selected. See Reviewing legal completeness for what it checks, what a recheck does, and how to act on (or skip) what it surfaces.
3. Add participants and witnesses
Add the parties who need to sign and provide their display names and contact details they should see in invitations. Agreements can have at most 15 signing participants in total, including the initiator. Declarations have one declarant. Either type can have up to five active witnesses.
Any witnesses that were added are invited after the main signing participants complete their signatures. See Sign and respond for the recipient experience.
4. Set signature and publication rules
An Agreebase signature can comprise one or more methods, with at least one method (email account confirmation via OTP) required. Users (or agents) complete a signature by proving control of an existing digital identity.
The initiator of an agreement chooses how many methods must be completed at a minimum, and the initiator is also required to complete the same minimum. The more signature methods that go into an agreement signature, the more robust that signature is. The maximum number of signature methods permissible is three.
For publication options, hash-only blockchain publication is the default. This means that the blockchain record does not include the full-text but instead a cryptographically generated, secure hash of that text. To learn more about hashes and why they are both private and reliable as confirmation of the text they represent, see What is a hash?.
Full-text publication and verified party details are separate, explicit choices, and result in irreversible publication on the Base public blockchain. Full text is permanently public once written to Base. Verified party publication can include entered names and verified signing email addresses if that option is selected by the initiator, and affected signers must acknowledge that their details, and the fact they signed/witnessed the agreement or declaration being signed, are going to be on a blockchain record that cannot be deleted, before finalization can occur.
Choose an expiry window from one to thirty days when the record should stop accepting outstanding signatures. Settings are locked before the initiator signs; material changes can reset completed signature work.
5. Authenticate and sign as the initiator
The initiator verifies control of their own digital identity, completes the required signature methods for the current version of the agreement or declaration being signed, reviews the final text, and explicitly finalizes the signature. Authentication proves control of a digital identity via email one-time passcode (OTP); signing proves that the person controlling that digital identity confirmed intent to sign the record being created - these are two separate and explicit steps.
After the initiator finalizes, the record moves to pending confirmation and Agreebase sends invitations to the other participants. A participant can sign, decline, or submit a counter-proposal. A counter-proposal pauses the record until the initiator resolves it.
6. Complete the record
When all required party signatures and required witness signatures (if applicable) are complete, the record seals. If an eligible declined or removed participant is not required to complete, the initiator may explicitly proceed without them.
The sealed version is permanent and unchangeable. If it is an agreement, then modifying its obligations must be done the same way a paper contract would be, which is typically be creating a new agreement, referencing the agreement being modified, and explicitly agreeing with the same parties that you agree to change the terms of the original agreement.
To learn more about the different lifecycle stages of an Agreebase record, see Lifecycle and versions.
7. Retain the resulting artifacts
For agreements and declarations, Agreebase creates a signed PDF, evidence metadata, confirmation emails, and a blockchain commitment. On rare occasions if the blockchain is congested, parties may receive the confirmation email and PDF before the blockchain record completes, in which case they will receive a follow-on email confirming the blockchain record.
It is important that parties and witnesses retain the confirmation emails sent by Agreebase at the time of sealing or completing a notarization process, as these contain the details required to perform future verification against the record if required.
Use Manage a record to retrieve sealed artifacts and Verify a record to check them later.