Build with Neuro
Four ways to build. One set of primitives.
Call the Agent API over HTTPS, connect an AI application through MCP, deploy the white-label apps, or run your own Neuron.
Identity, contracts, tokens, payments and messaging, behind one API and one audit trail.
Build on the Agent API, with or without an AI agent.
One HTTPS API for identities, contracts, tokens, payments and messaging. Give a coding agent current docs through skill.md or llms.txt, and let AI applications act through the MCP servers. Best for teams shipping a defined workflow.
Three tasks to hand a coding agent
“Add a server-side health check that logs in through the Agent API and reads the account.”
Two calls, Account/Login then Account/Info, with the credentials kept in your backend.
“Create a contract from our membership template and request signatures from both parties.”
CreateContract, then SignContract per party. Tokens and payments later point to the signed contract.
“Issue each buyer a ticket token and refuse any transfer above face value.”
A token with a state machine. The resale rule is checked at write time, not after.
Three other ways in.
Deploy the white-label apps
The identity app, the Neuro-Exchange trading front end and the Neuro-Admin operator console, under your brand.
Connect an AI application over MCP
Neuron MCP servers expose identity, contracts, payments, messaging and files as tools, under OAuth scopes you grant.
Run your own Neuron
Host accounts and the Agent API yourself, and federate with other Neurons. Neuro-Ledger® included.
Scopes and limits are enforced by the Neuron.
A model-generated request is not proof that a user authorised it. The Neuron checks scopes, roles and spending limits on every call, and records the refusals too.
The rules are not code your agent wrote.
Identity, authority and limits are platform properties. No agent generates its way around them, and neither does a developer in a hurry.
So what you build quickly is still something you can keep.
Paid
Illustrative limit
The limit holds when the AI asks for more.
Try it: ask for more than the limit. Nothing moves, because a person set the limit and the AI never had permission to go past it.
The refusal is recorded too, which is exactly what an auditor wants to see.
What runs underneath.
We wrote the core ourselves, so we can tell you exactly how it behaves.
Neuro-Ledger®
Our distributed ledger. Not a blockchain: no mining, records readable only by those entitled to them, and correctable when the law requires it.
Neuron™
The server that hosts accounts, identities and contracts. Neurons federate, so your installation deals with another while each keeps its own data.
Smart contracts
Human-readable terms, roles and parameters, signed by verified parties. Tokens and their state machines are created by contracts.
e-Daler®
Neuro’s patented electronic money. It moves between two devices with no network and settles when one returns.
Open protocols
Messaging and presence run on XMPP. Our founder contributes to IEEE P1451.99 on IoT harmonisation.
New to Neuro. Working examples two days later.
At FIRSTBLOCK-ATHON 2026 in Stockholm, six organisations brought real problems to teams who had never used Neuro.
-
Before
Nobody in the room had used it.
None of the teams had seen Neuro before the event.
-
The brief
A real problem, not an exercise.
Problems brought by UNICEF, the Swedish Red Cross, the World Food Programme, AI Institutet, Hundstallet and AIMS Management.
-
Two days later
Working examples, running.
The checks, contracts, records and payments were already there, so each team spent its two days on its own idea.
Each real service still needs its own rules, testing and approval.
And these are already carrying real money.
Four services in production, each doing a different job.