For everyone, everywhere.
Call it over HTTPS, or give an AI agent the MCP servers. Every operation is documented, and there is a sandbox to try it in.
Sign-up, document checks, a verification vendor, a payment integration, a double-entry table, an audit log. None of it is the product.
And you maintain all of it for as long as the service runs.
Every transaction needs three answers. Here they are API calls.
Identity
A Legal Identity is a reviewed identity for a person, company or device, signed by whoever approved it. Any service can verify it and ask for one attribute, not the whole record.
Explore Identity Documentation · Legal Identity flow
Assets
A token is an asset record with an owner, the contract that created it and an event log. Its state machine allows some transitions and refuses the rest, at write time.
Explore Assets Documentation · Token state machines
Payments
Wallets hold e-Daler, Neuro’s electronic money, and connect to payment providers. A contract can release a payment on a condition, and the payment records why it moved.
Explore Payments Documentation · PaymentsThe usual stack is three vendors and your glue code. An SDK for the person, a table for the register, a rail for the money, and you own the joins forever.
Neuro is one API, one data model and one audit trail.
So your first sprint goes on the product.
See the architectureEvery interface reaches the same identities, contracts, assets and payments. Pick the one that fits the job.
npx skills add https://docs.neuro-tech.io, or point it at llms.txt or the documentation MCP server.
Your own Neuron
Run the server yourself. A Neuron hosts accounts, identities and the API. Run your own and federate with other Neurons.
The sandbox approves test identities automatically, so you can run the whole flow before any real check happens.
POST /Agent/Account/Create, signed with the API key your Neuron operator gives you.
POST /Agent/Account/Login with an HMAC signature. You get back a JWT for every later call.
POST /Agent/Crypto/CreateKey. The key signs identity applications and contracts on the account’s behalf.
POST /Agent/Legal/ApplyId. A reviewed identity others can verify; the sandbox approves it for you.
POST /Agent/Legal/CreateContract, then SignContract. From here, tokens and payments hang off signed contracts.
Spending limits, signing authority and the audit trail are enforced by the Neuron. An agent, or a developer in a hurry, cannot generate a way past them.
When something does go wrong, the record shows who acted, who allowed it and what moved.
We wrote the core ourselves, so we can tell you exactly how it behaves.
Our distributed ledger. Not a blockchain: no mining, records readable only by those entitled to them, and correctable when the law requires it.
The server that hosts accounts, identities and contracts. Neurons federate, so your installation deals with another while each keeps its own data.
Human-readable terms, roles and parameters, signed by verified parties. Tokens and their state machines are created by contracts.
Neuro’s patented electronic money. It moves between two devices with no network and settles when one returns.
Messaging and presence run on XMPP. Our founder contributes to IEEE P1451.99 on IoT harmonisation.
Same primitives, six different products.
Nobody has built these yet. Open one to see which primitives it uses.
Tell us the workflow. We will point you to the right calls, or the right person.
