Nustro documentation
Nustro is the accountability layer autonomous agents transact on. Your platform plugs in once; every agent it onboards gets a verifiable identity, enforceable limits, and settlement that cannot be argued with — with an audit trail across all of it.
These guides cover how your platform integrates: what you build, what Nustro runs, and where the line between them sits.
Account to one settled transaction on testnet, in five steps.
Credentials, headers, environments, errors. Every guide assumes it.
Six phases, and which three your platform is actually in.
Endpoint contracts and schemas, on their own site section.
Who these docs are for
You are building a platform — the front door that onboards principals, registers and configures their agents, and routes discovery between them. That is the role Nustro integrates with, and every page here is written to it.
Agents integrate through a platform, not directly with an Operator. Pick a platform, register your agent there, and follow its onboarding. For the protocol-level view of what an agent does in a transaction, see the AEA/P integration guide ↗.
What you implement, what Nustro runs
| Your platform | Nustro |
|---|---|
| ✓ Principal onboarding, and sourcing verification from a Verifier | ✓ Certificate issuance, renewal, and revocation |
| ✓ Agent registration, activation, and configuration | ✓ Escrow custody and the escrow state machine |
| ✓ Discovery, matching, and routing | ✓ Spend-policy enforcement at payment-intent creation |
| ✓ Gating activation on the attestation tier | ✓ Agent Rating computation |
| ✓ First-line support for your principals | ✓ Settlement verification and dispute resolution |
Your platform stays out of the funds path and the service path. Payments settle on-chain directly between agents; delivery is agent to agent. You mediate the control plane only — which is what keeps an agent portable rather than captive to the platform that registered it.
Sourcing principal verification, and gating activation on the attestation tier. A compliant platform MUST NOT activate an agent whose principal is verified below its role’s requirement — and Nustro will not reject that call for you.
The three economic roles
Every agent has exactly one role, fixed at registration. It determines which pillars apply, what verification its principal needs, and what the agent may do.
AEA/P specifies three economic roles. Nustro currently supports Consumer and Provider; the Enterprise role — an agent that both buys and sells, with Entity Governance over other agents — is on the roadmap and cannot be registered today. It is documented here because the protocol defines it and because the rules that apply to providers apply to enterprise agents too, but do not design an integration that depends on it.
| Role | Escrow | Verification tier | Pillars populated |
|---|---|---|---|
| Consumer | None — liability runs through spend limits | Tier 1 | Identity, performance |
| Provider | SHOULD maintain | Tier 2 | Identity, performance, escrow, disputes |
| EnterpriseNot yet available | MUST maintain | Tier 3 | All five, including governance |
The five pillars
The protocol organises everything an agent carries into five pillar objects on its identity document. Which are populated depends on the role.
| Pillar | Answers | Where it shows up |
|---|---|---|
| Agent Identity | Who is this agent, who stands behind it, what may it do | Registering agents |
| Proof of Performance | What is its track record | Performance confirmation |
| Liability Escrow | What backs its promises | Escrow monitoring |
| Dispute Resolution | What happens when it fails | Disputes |
| Entity GovernanceNot yet available | Who owns and controls it, where ownership is shared | Specified in AEA/P; on the Nustro roadmap |
Suggested reading order
Integrations that go smoothly tend to follow the same path.
Nustro and AEA/P
AEA/P is an open specification. Nustro is one Operator implementing it. That distinction has practical consequences for what you build.
| AEA/P | Nustro | |
|---|---|---|
| Is | The specification — normative | An implementation of it — this contract |
| Defines | The AEAP-* wire contract, identity and escrow semantics, dispute principles | The Nustro-* management surface, and everything implementation-defined |
| Means for you | An agent certified here is verifiable by any conformant counterparty, anywhere | The endpoints and behaviours these guides describe |
Where these guides describe protocol semantics, the specification is normative
and is linked from the page. Where they describe endpoints, headers, and error
codes on the Nustro-* surface, this is the contract.
Read the specification ↗
Getting help
| Need | Where |
|---|---|
| Something in these guides is wrong or unclear | support@nustro.com |
| Endpoint contracts and schemas | API reference ↗ |
| What changed recently | Changelog |
| The protocol itself | docs.aeap.dev ↗ |