Accept-API · Agreement Acceptance Flow

Court-Checkable Agreement Acceptance for Agents

An agent that needs to close a mutual NDA end to end can assemble the agreement, then have both parties bind their acceptance to the exact assembled artifact by hash. The result is a set of hash-chained receipts a third party can check without trusting either side's word for it, plus a clear hand-off point for real, legally binding e-signature.

Assemble → Accept → Accept Hash-Chained Receipts Zero PII Not Legal Advice
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Court-checkable, not legally executed: the assembler stops at the variable map and never asks for real party identity, signatures, or notice addresses. That stays a strict zero-PII boundary. The artifact set is hash-referenced and independently replayable; it is a stated-acceptance record, not an executed contract. Real signatures happen off-platform.
The Flow

Three calls, one hash-chained artifact set

Each step references the one before it by hash, never by re-embedding the agreement text or party identity.

1
Assemble the mutual NDA
Fill in the cover-page variables only: purpose, effective date, term, governing law. The Standard Terms body is the Common Paper Mutual NDA v1.0, vendored verbatim and never touched. The output carries an execution_hash.
assemble_mutual_nda
2
Party A binds acceptance
Party A's acceptance references the exact assembled artifact by its hash. Nothing about the agreement text is re-sent; only the reference.
bind_agreement_acceptance
3
Party B binds acceptance, chained to Party A's
Party B's acceptance references the same artifact hash, plus Party A's acceptance hash as previous_proof_hash, linking both parties' acceptances into one verifiable sequence.
bind_agreement_acceptance
Where Real Signing Happens

The e-sign hand-off

Each of the three artifacts can optionally carry a cryptographic proof binding, turning a stated acceptance into a countersignable receipt. Real party identity and e-signature collection happen off-platform at anchor.ainumbers.co/sign (Anchorproof). This flow never asks for those details itself.

Related

Explore the full technical flow

Agreement Acceptance Receipt Flow (technical)

The full composed how-to with worked-example parameters and hash values.

Open how-to →

mutual-nda-composer chain

The registered 2-node OCG chain: assemble → one acceptance.

Open chain →

Standardized Agreements Guide Hub

The node pages and the wider open-agreement-standards landscape.

Open hub →

Agreement Standards Directory

Curated catalog of open standardized agreement frameworks, including Common Paper.

Open directory →