How It Works
The Legal Framework,
Explained
Every Ambr contract exists simultaneously as human-readable legal prose and machine-parsable JSON — linked by SHA-256 hash, signed by ECDSA wallets, minted as cNFTs on Base L2.
Code is law. Law is Readable.
Architecture
The Dual-State Contract
// LAYER 01: WHAT YOUR LAWYERS SEE
Human
Readable
Every authorization Ambr issues comes with a plain-language agreement your legal team can actually read — no JSON, no jargon, no surprises.
- FormatMarkdown / PDF Output
- JurisdictionDelaware, US (Default)
- Cryptographic TieSHA-256 Hash Included
// LAYER 02: WHAT YOUR AGENT EXECUTES
Agent
Parsable
The same agreement, served as strict JSON: spending limits, authorized counterparties, expiry. Your agent can't misread it, and it can't pretend it never saw it.
- FormatJSON
- State StorageBase L2 ERC-721
- Agent InterfaceREST + A2A + MCP
Lifecycle
Contract Lifecycle
From creation to activation — every step is cryptographically verifiable. Full contract text is private by default.
Draft
Agent or principal calls the Ambr API. AI generates dual-format output — human-readable legal text and machine-parsable JSON — linked by SHA-256 hash.
Handshake
Counterparties review, negotiate visibility preferences, and signal intent — accept, reject, or request changes. All via wallet or agent delegation.
Activate
Both parties sign with ECDSA wallet signatures. Second signature activates the contract and triggers cNFT minting on Base L2 with the SHA-256 hash stored on-chain.
< 400ms
Average contract generation
SHA-256
Cryptographic binding
Base L2
On-chain verification
Interface
Reader Portal
A private-by-default interface for viewing, verifying, and sharing contracts. Full text requires authorization — metadata and hash verification are always public.
View Contracts
Authorized parties view the full Ricardian Contract in both human-readable and machine-parsable formats. Unauthenticated visitors see metadata only.
Verify Integrity
Match the document SHA-256 hash against the stored contract to confirm it hasn't been tampered with. Hash verification is always public — no account needed.
Amendment Chains
Navigate the full history — original contract, amendments, extensions, and sub-agreements — via parent_contract_hash links.
Secure Sharing
Generate time-limited share links for lawyers, auditors, or counterparties. No account required — the link grants read access.
Wallet Access
Connect your wallet to prove you're a party to the contract. Wallet signatures verify identity without passwords or accounts.
Handshake Actions
Accept, reject, or request changes directly from the Reader Portal. Negotiate terms and visibility preferences before signing.
Evolution
Amendment Chains
Contracts evolve. Amendments reference the original via parent hash, creating an immutable chain with full audit trail.
Composability
Amendment Chains
Contracts evolve over time. Amendments reference the original via parent_contract_hash, creating a linked chain with full audit trail.
a1b2c3...Master SLA
Original compute service agreement between Deployment Agent and Infrastructure Provider.
d4e5f6...Rate Increase
Amendment increasing rate limit from 10K to 20K requests/day. References parent hash.
g7h8i9...Task Sub-Agreement
Per-task sub-agreement spawned from master SLA for a specific GPU compute job.
j0k1l2...6-Month Extension
Contract extension linked to the original via parent_contract_hash.
Ready to Build?
Initialize your first contract or explore the developer documentation and MCP integration guides.