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 verification — you assert each principal’s tier | ✓ 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 |
| ✓ Choosing each agent’s type and authorized actions | ✓ 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.
Your platform verifies each principal — itself or through a verification
provider — and asserts the tier to Nustro. Nustro checks the asserted tier
against the agent type at registration and activation and rejects a mismatch
(verification_tier_insufficient), but it cannot check the verification behind
it: the assertion is your platform’s, and so is its accuracy.
Agent types
Every agent has an agent type, set at registration, that says whom it acts
for. Its authorized actions — purchase, sell, delegate — say what it
may do. The line between the two types is receiving money: a personal agent only
pays; a business agent may be paid.
| Type | Acts for | Authorized actions | Verification | Escrow |
|---|---|---|---|---|
| Personal | A natural person | MUST include purchase; never sell | Tier 1 | None — liability runs through spend limits |
| Business | A company, or an individual holding a business license | At least one of purchase or sell | Tier 2 | MUST maintain when it carries sell, sized on what it sells |
In a transaction the two agents are named by side — the buyer agent and the seller agent. A business agent that carries both actions is a buyer in one transaction and a seller in the next. “Role” in these guides means only the infrastructure roles: Operator, Platform, Verifier.
Once its principal is verified to Tier 2, a personal agent can be upgraded to a business agent in place — the same agent ID, rating history and dispute record. Business to personal is not supported; register a new personal agent. See Registering agents.
The five pillars
The protocol organises everything an agent carries into five pillar objects on its identity document. Which are populated depends on what the agent does — Liability Escrow, for one, only on a business agent that sells.
| 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 for business agents under a governance document; 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 ↗ |