The runtime and broker that applications connect to when using Neuro services. It enables secure, federated interaction across domains and hosts higher-level capabilities such as identities, contracts, tokens, and ledger-backed services.
The distributed audit and persistence layer used by Neuro services. It is designed to support auditable, distributed systems without depending on a traditional blockchain model.
A trusted actor within a domain that validates identities, approves or governs identities and contracts, and contributes trust to the network through signatures and policy. Often described as a digital equivalent of a notary.
The identity used to participate in the network as a connected actor or account. It identifies the account communicating with a Neuron or another participant.
A stronger, cryptographically protected identity tied to a real legal actor such as a person or organization. Legal identities are used when trust, signatures, ownership, or compliance matter.
A structured digital agreement. In Neuro, smart contracts combine human-readable and machine-readable content, support signatures and lifecycle rules, and are designed to work across domains.
A digital instrument tied to ownership, agreements, and traceable events. In Neuro, tokens can represent NFTs, asset-backed instruments, rights, or other digital and cyber-physical assets.
Neuro’s token model for digital instruments and tokenized assets. Neuro-Features are created using smart contracts and can represent ownership, rights, or asset-backed structures.
A federated digital payment mechanism used in Neuro. It can be linked to contracts, tokens, and programmable payment flows.
A model where multiple domains manage their own infrastructure but still interoperate in a shared framework. Federation is a core part of how Neuro supports cross-domain interaction.
A distinct operating boundary in the federated network. Each domain can manage its own users, services, policies, and trust relationships.
A cryptographic proof attached to an identity, contract, or other signed data to verify integrity and authorship. Signatures are central to how Neuro establishes trust.
The part of a cryptographic key pair used to validate signatures or encrypted interactions.
The secret part of a cryptographic key pair used to create signatures. Agent API key operations use key material stored encrypted by the Neuron and invoked through the Agent interface.
A structured model for representing workflows as states and allowed transitions over time. In Neuro, state machines can be connected to contracts, tokens, and programmable payment logic.
Neuro’s main HTTP API. The caller acts through a Neuron’s Agent endpoint instead of connecting directly over XMPP while holding the corresponding private keys. The name is unrelated to artificial-intelligence agents.
The federated communication protocol underlying the Neuron’s communication model. It provides the base for secure, cross-domain messaging and interaction.
The ability to inspect and verify what happened, who acted, and what was recorded. Auditability is one of the main reasons Neuro uses Neuro-Ledger together with signatures and identities.
Go deeper
What is a Neuron?
See how the main components relate at runtime.
Developer entry points
Start with the Agent API, connect an MCP client, or find an application guide.