Skip to main content
A Neuron contract is a signed, machine-readable agreement with human-readable text. It is not program code deployed to a blockchain. A contract defines:
  • the machine-readable XML payload;
  • the text each signer sees;
  • roles and required signatures;
  • typed parameters and validation;
  • visibility, validity, and lifecycle rules.
Use the contract quickstart to choose LegalLab, the Agent API, or the .NET XMPP client. Return here when you need to understand the format those tools read and write.

​
Templates and instances

A template defines the roles and parameters that can be filled later. It must be proposed and approved before an application can create contract instances from it.
Start with Templates and instances when this distinction is unfamiliar.

​
MCP’s role

The built-in Neuron MCP servers do not currently propose templates, create contracts, or sign contracts. An MCP-capable development client can still help edit XML, inspect files, retrieve reference content, or query events. Use LegalLab or the Agent API for the contract operation itself.

Contract quickstart

Choose a tool and make a controlled change to an example contract.