Agreements - Neuro Developer Documentation

An agreement combines an approved template, parameters, parties, roles, human-readable text, and signatures.

No end-to-end two-party example is currently available. Before integrating, ask the Neuron operator for an approved template and confirm how proposals, signatures, and final status are delivered.

Start here

To edit a contract template, try a contract in LegalLab.
To call contract operations from a backend, review the Contract API workflow.
To learn the contract structure, read Templates and instances, Roles and parts, and Contract parameters.
To check request fields and responses, use the contract API reference.

Agreement lifecycle

Alice and Bob have current Legal Identities
        ↓
Select or propose an agreement template
        ↓
Wait for template approval
        ↓
Create the contract with parameters and parties
        ↓
Send the proposal
        ↓
Collect signatures
        ↓
Verify the final signed state

Store the template ID, contract ID, party identities, roles, parameters, signatures, and returned status throughout this process. The agreement is complete only when every party can retrieve the same contract and verify its final signed status.