Agreements

An agreement combines an approved template, parameters, identified parties, roles, human-readable text, and signatures. It builds on the account, key, and Legal Identity stages.

Before you start

The two-party Agent API flow requires all of the following:

Requirement	Why it is needed	Get it from
Neuron host and authenticated accounts	Each participating user acts through the target Neuron.	Neuron operator and Agent API quickstart
Current Legal Identity for each party	The contract binds identified parties to roles.	Verified identity
Signing key for each party	Each party signs under its assigned role.	Create a cryptographic key
Approved contract template	The instance receives its allowed parameters, roles, and terms from the template.	Sandbox automatic review or operator approval

Use a template ID from the Neuron your application connects to.

Contract approval

In the Neuro sandbox, newly proposed contracts, including templates, enter an automatic review and approval process. Submit your template through the Agent API as usual; you do not need to request manual approval first. The review can approve or reject the proposal. Outside the sandbox, the Neuron operator is responsible for contract approval. Contact the operator to arrange review of a new template or obtain an existing approved template. Approval is asynchronous. Retrieve the proposal with Get Contract and wait for Approved before using it as a template. If it remains Proposed or is Rejected, contact the operator with its identifier. Automatic approval does not sign the contract for its parties; their review and signatures are still required.

Start from where you are

What you have now	What to do next
No account or Legal Identity	Start with the identity foundation.
Accounts but no signing keys	Create a key for each signing party.
Current identities but no approved template	Author and submit a template, then follow the approval process for your environment. You can also ask the operator for an existing approved template.
All prerequisites	Follow the contract API lifecycle.
A contract ID from an existing workflow	Use the contract operations to retrieve its current state.

Follow the agreement lifecycle

Accounts, keys, and current Legal Identities
        ↓
Select or propose a contract template
        ↓
Wait for template approval
        ↓
Create the instance with parameters, parties, and roles
        ↓
Sign and send the proposal
        ↓
Collect the remaining signatures
        ↓
Retrieve and verify the final Signed state

Use the contract API lifecycle for the ordered create, review, propose, sign, and retrieve steps. Use Create a contract with the Agent API for template submission and instance creation. Use LegalLab to inspect and edit templates. Read Templates and instances when designing the contract model.

Confirm success

The agreement is complete only when every party can retrieve the same contract, its status is Signed, and its signatures contain every required role. Persist the template ID, contract ID, party Legal Identities, roles, parameters, signatures, and latest status. Proposal delivery and signatures can be asynchronous, so do not treat the create response as completion.

Continue to a contract-created asset

To create a Neuro-Feature through a contract, follow Author a token with a state machine and Script.

Build an application

Verified identity

Sign-in and signatures

Contracts and agreements

Tokens and digital assets

Wallets and payments

Other application tasks

Reports

Before you start

Contract approval

Start from where you are

Follow the agreement lifecycle

Confirm success

Continue to a contract-created asset

​Before you start

​Contract approval

​Start from where you are

​Follow the agreement lifecycle

​Confirm success

​Continue to a contract-created asset

Before you start

Contract approval

Start from where you are

Follow the agreement lifecycle

Confirm success

Continue to a contract-created asset