Use /my-records to authenticate with an email OTP and see records associated with your verified identity graph. Records can also be retrieved by AGR reference through the participant-facing web, REST, or MCP surfaces.
Pending records
For a pending record, the initiator may be able to:
- Resend an eligible invitation, subject to delivery waits and cooldowns.
- Remove an unsigned participant.
- Waive or complete without a declined or removed participant.
- Replace a declined or removed witness.
- Rescind the pending agreement.
Participants may sign, decline, or submit a counter-proposal. Witnesses can only witness the current version; they do not accept the underlying party obligations through the witness action.
Pending records expire at their configured expiry time. An expired record cannot continue signing; create a new record if the terms still matter.
Resending an invitation
If a participant hasn't received or has lost their invitation email, the initiator can resend it from the record page in the web app, or through the equivalent REST (POST /agreements/{id_or_ref}/participants/{party_id}/resend-invitation) or MCP (resend_participant_invitation) call. A resend reuses the same invitation link rather than issuing a new one, so a participant who already started responding doesn't lose progress. Resends are rate-limited per participant to stop repeated sends from becoming a nuisance or a delivery-abuse vector; if a resend is refused for being too soon, wait for the cooldown shown before trying again.
Rescinding
Rescinding ends a pending agreement, declaration, or co-notarized notarization before it seals. Only the initiator can do it, and only while the record is still pending. It notifies every invited participant that signing has stopped, but it does not create a sealed record or write anything to the blockchain; there is nothing later to verify, because nothing was ever completed. Use it when the terms have changed enough that continuing to collect signatures on the old text no longer makes sense; a fresh record is the right next step if the underlying arrangement still needs to be recorded.
Adding parties
Participants are set when the record is created or, for an ordinary draft, while the initiator is still editing it before submitting for confirmation; see Create and seal a record. Once the initiator has signed and the record moves to pending, no new signing party can be added; the participant list is fixed at that point (a declined or removed witness can still be replaced, per above). If a record needs an additional signer after it's already pending, the initiator's options are to rescind and recreate it with the full participant list, or to seal it as-is and record the addition as a new, related agreement.
Draft records
An initiator can update or cancel an ordinary draft before it is submitted for confirmation. A draft cancellation is not a cancellation of a sealed record. Notarizations follow their content-hash signing flow and cannot be cancelled or rescinded in the same way as ordinary agreement drafts.
Sealed records
A sealed record is fixed. The original is not edited in place.
- An amendment creates a new draft that references and will supersede the original when sealed.
- A cancellation creates a new mutual cancellation draft for the sealed record; it does not unilaterally cancel the original.
- A superseded original remains preserved as historical authority for its own version, while the newer record becomes the current authority.
Witnesses cannot initiate amendments. The amendment and cancellation paths copy or reference the original participants according to the lifecycle rules.
Artifacts
Participants can retrieve the sealed PDF when it has been generated. The PDF is the human-readable signed artifact and includes verification material. A private PNG share card can also be generated for sealed agreements and notarizations. The card is a convenience artifact, not a replacement for the AGR reference, hashes, or verification result.
Blockchain writing and PDF generation are background operations. A sealed record may briefly show a pending blockchain or document state, followed by separate confirmation email(s) when those artifacts are ready.