AEA/P · Autonomous Economic Agent Protocol

An open governance protocol for autonomous economic agents

AEA/P defines how AI agents are held accountable when they transact: verifiable identity, proof of performance (PoP), liability escrow, dispute resolution, and entity governance — one open specification, implemented by independent Operators and Platforms.

Read the docs Full specification

First Operator implementation is live — Nustro · nustro.com

One agent wants to do business with another it has never met. AEA/P is the trust layer that makes that economic transaction accountable.

Autonomous economic agent
An agent
needs something done
an economic transaction
$pays
delivers a service
Autonomous economic agent
Another agent
offers it for a price
but how do they trust each other?
AEA/P Holds agents accountable for what they do Five governance pillars
P1
Identity
Proves who each agent is
P2
Performance
Tracks their track record
P3
Escrow
Liability escrow protects buyers
P4
Disputes
Recourse if it fails
P5
Governance
Rules it must follow

Agents can do business with agents they don't know — because AEA/P proves who they are, tracks how they perform, holds liability in escrow, and provides recourse when something goes wrong.

Definition

What is an autonomous economic agent?

An autonomous economic agent (AEA) is an AI agent that acts on its own, and whose actions have economic consequences. It spends money, earns money, commits resources, or enters agreements — without a person approving each step.

This is what separates an AEA from ordinary software. An API waits to be called. A smart contract runs when its conditions are met. An AEA takes the initiative: it finds counterparties, negotiates, and transacts — at machine speed.

Communication protocols like MCP and A2A standardize how agents connect. Payment protocols like x402, MPP, and AP2 enable agents to transact. Commerce protocols like UCP and ACP orchestrate the buying experience. Identity standards like ERC-8004 provide on-chain discovery and reputation.

The Gap

None of these protocols answer the harder questions: what happens when an agent causes financial harm? How are disputes resolved without courts? What liability escrow exists before a transaction begins? How does an autonomous entity govern itself?

What AEA/P Defines

AEA/P specifies that missing accountability layer. It doesn’t replace these protocols or sit on top of them—it spans across communication, commerce, payments, and identity, binding them into one governed, end-to-end flow.

Architecture

Where AEA/P sits

AEA/P assumes the existing agent stack rather than replacing it. Each layer below already has maturing protocols; AEA/P runs across them as the governance fabric.

AEA/P
Governance that spans every layer
Identity · PoP · Escrow · Disputes · Governance
Commerce
UCP / ACP — Universal Commerce Protocols
Product discovery, checkout, agentic commerce across AI surfaces
Payments
x402 / MPP / AP2 or native implementation
HTTP-native settlement, machine-to-machine payments, payment authorization, or direct atomic settlement via a native AEA/P-compliant mechanism
Identity
ERC-8004 / OAuth 2.1 / SPIFFE / OpenID Connect
Agent discovery, on-chain reputation, authentication, credential management
Communication
A2A — Agent-to-Agent Protocol
Agent messaging, task delegation, multi-agent collaboration
Connectivity
MCP — Model Context Protocol
Agent-to-tool connections, data access, system integration
One governance fabric running across the entire agent stack — not a layer perched on top of it.

MCP connects agents to tools. A2A enables agent-to-agent coordination. x402, MPP, and AP2 handle payment settlement across stablecoins, cards, and bank transfers. UCP and ACP orchestrate the commerce flow—product discovery, checkout, fulfillment. ERC-8004 provides on-chain identity and reputation signals. AEA/P spans across all of them—tying identity, payments, commerce, and communication into a single accountable flow, so the same governance, liability, and dispute resolution apply end to end across everything an agent does.

Ecosystem

Protocol Landscape

The agent infrastructure stack is maturing rapidly. Existing protocols solve connectivity, communication, identity, payments, and commerce. AEA/P covers what happens when things go wrong—and how trust is established before things go right.

Capability AEA/P ERC-8004 x402 / MPP / AP2 UCP / ACP
Identity✓✓——
Agent authentication✓———
Agent discovery✓✓——
Payment intent✓—✓✓
Payment orchestration✓—✓✓
Human in loop✓—✓✓
Reputation✓✓——
Liability / escrow✓———
Disputes✓———
Governance✓———
Compliance✓———

AEA/P doesn’t compete with these protocols or stack on top of them. It spans across them—tying identity, payments, commerce, and communication into one cohesive, end-to-end flow with the economic accountability that regulated industries require.

The protocol

Five Protocol Pillars

AEA/P defines five interconnected governance capabilities that activate as an agent’s economic participation deepens. Together they form one connected governance lifecycle — select a stage to see what it does.

→ → → →
Scope

What AEA/P is not

A protocol is defined as much by what it leaves out. AEA/P deliberately does not try to be:

A payments protocol

AEA/P moves no money. Settlement runs over x402, MPP, AP2, or a native mechanism — AEA/P governs the identity, escrow, and recourse around the payment.

A communication layer

It does not replace MCP or A2A. Agents keep connecting and coordinating the way they already do; AEA/P makes the resulting transactions accountable.

An agent framework

AEA/P doesn't prescribe how agents are built or which models they run. It defines how they are identified, rated, escrowed, and held to account.

A hosted service

AEA/P is an open specification. Operators and Platforms implement it independently — implementations are built on the protocol, they are not the protocol itself.

Roles

Who AEA/P is for

AEA/P separates roles at two levels: the participants who run the governance fabric, and the agents that transact on it. The roles nest: one protocol spans many Operators, each Operator serves many Platforms, each Platform hosts many agents, and every agent traces to a principal — select a role to see what it does.

Participants and agents — how the roles stack
Principal
AgentconsumerC
Principal
AgentproviderP
Platform
Principal
AgentproviderP
Principal
AgentconsumerC
Platform
Operator
Principal
AgentconsumerC
Principal
AgentproviderP
Platform
Principal
AgentproviderP
Principal
AgentconsumerC
Platform
Operator
Verifier
AEA/P One open specification under every Operator

A third economic role — the Enterprise agent, transacting on both sides as an autonomous business — carries the full governance stack, including entity governance.

See how the roles interlock — end-to-end sequence diagram →
Adoption

Implementations

AEA/P is running in production. Implementations listed here operate the protocol’s Operator or Platform surface against the published specification.

Live
Nustro
Operator — first live implementation

Commercial Operator built on AEA/P, running the protocol’s Operator surface: agent identity issuance (did:aeap:), proof of performance, liability escrow, atomic on-chain settlement, and dispute resolution — with sandbox and production environments.

nustro.com Docs API reference
Your implementation
Building an Operator or Platform?

The specification and the Operator and Platform reference documents are open. If you’re implementing the protocol, get in touch to be listed here.

Read the references Get listed →
Certification

AEA/P Certified

A system claiming AEA/P conformance declares its conformance level and economic role; AEA/P Certified indicates that an independent assessment has verified conformance at the claimed level for the declared role. Certification criteria and processes are being defined with input from early implementers and standards bodies.

✓ AEA/P Certified
On a light host surface
✓ AEA/P Certified
On a dark host surface
Certified implementations display this mark on their own surfaces.
Track record

Origin & Prior Art

AEA/P is not a theoretical proposal. Its core concepts were designed, implemented, and tested in a working platform years before the current AI agent ecosystem emerged.

From xDAC to AEA/P

In 2018, xDAC was published—a platform for Decentralized Autonomous Companies. The xDAC whitepaper defined governance for autonomous entities including Proof of Performance rating, liability escrow, automated dispute resolution, and support for autonomous agents as team members.

The platform shipped with company registration, team management, invoicing, and payment processing. The concepts were ahead of their time—LLM-based agents didn't exist yet. In 2026, those governance concepts are being refined as AEA/P for the current AI agent ecosystem.

Timeline

2018
xDAC whitepaper published. Proof of Performance, liability fund, dispute resolution, autonomous agents as team members.
2019
xDAC platform ships with company registration, team management, wallets, invoicing.
2025
LLM agents go mainstream. MCP and A2A standardize. ERC-8004 launches on-chain. x402, MPP, UCP, and ACP emerge. Economic governance gap becomes critical.
2026
AEA/P protocol initiated. Protocol Framework and Specification published. First Operator implementation (Nustro) goes live. NIST, CSA, and OWASP engagement.
Standards engagement

AEA/P is developed in the open, in dialogue with the bodies standardizing agent identity and governance.

NIST CAISI RFI — Submitted March 2026
NIST NCCoE — Agent Identity & Authorization
Get involved

Contribute to the protocol

AEA/P is an open protocol specification, developed in public. Contributions, feedback, and implementation reports are welcome — if you’re implementing the protocol, integrating a platform, or building agents, reach out at support@aeap.ai.

Read the docs Full specification support@aeap.ai