AMDP — Agent Mandate Discovery Protocol
EU-sovereign standard for cross-vertical mandate discovery. Co-authoring with IAB Tech Lab + Linux Foundation. Reference implementation Lean-4 verified.
AMDP defines an open, vendor-neutral mandate layer: which agent may do what, for whom, with which constraints, across verticals. Today every vertical answers this individually (advertising, equity research, procurement, public services). AMDP standardizes the answer.
This is not a marketplace, not a brand, not a revenue layer. AMDP is the spec — like ICANN defines DNS standards without being a search engine. Nexbid is authoring co-maintainer with EU authority position.
What AMDP is NOT
- ❌ "Google for agents" — frame invention (ICANN move, not Google move)
- ❌ Universal Agent Index — already exists (IAB Tech Lab Agent Registry, MCP Registry)
- ❌ Nexbid Mandate Marketplace — no marketplace, no hosting, no revenue layer
- ❌ opua Agent Commerce Platform — frame-invention correction per ADR-039
What AMDP IS
- ✅ EU-sovereign standard in development (authoring + seats, no end product)
- ✅ Co-authoring with IAB Tech Lab + Linux Foundation (multi-stakeholder governance)
- ✅ Reference implementation Lean-4 verified (technical differentiation)
- ✅ Layer L4 in four-layer-defense frame (mandate layer, orthogonal to match/transaction/measurement/execution)
Key Facts
- Status
- ADR-040 accepted (2026-05-17)
- Reference Implementation
- nexbid-dev/protocol-commerce
- Lean-4 Theorems
- 62 (0 sorry)
- IAB Submission Window
- CW21 2026 (Curation Protocol Q2)
- LF Submission
- CW23 2026 (Agent Infrastructure WG)
- Roadmap
- 5 phases over 9-12 months
IAB pitch draft + LF pitch draft ready
Public GitHub repo, MIT license, Lean-4 verified
Formally verified Match-Layer security properties
Inclusion deadline 2026-06-30 for AAMP listing
Charter pull request against linuxfoundation/charters
Pre-submission → IAB inclusion → LF submission → v1.0 → platform hero
Position in Four-Layer Defense Frame
AMDP is the mandate layer BENEATH all other layers. It is not a competitor to Nexbid AdCP (L3 Match), but a bridge between L3 applications.
| Layer | Name | Wer / Who | Status |
|---|---|---|---|
| L0 | Transaction Protocol Base | UCP Coalition, ACP (Apache 2.0, governance closed) | Closed-by-coalition |
| L1 | Execution | Walled-Garden MCPs (Google, Meta, etc.) | Commoditized |
| L2 | Measurement | SegmentStream, Triple Whale, DCM/MMM | Mid-term commoditized |
| L3 | Match + Protocol Discovery | Nexbid (AdCP, Multi-Rail) | High defensibility |
| L4 | Mandate (new, via AMDP) | AMDP standard via IAB + LF | OPEN — AMDP occupies |
Spec sections
- §0
Mandate as first-class citizen
Ed25519-signed mandate object. Who may do what, for whom, until when, with which constraints.
- §1
Resolution semantics
Cross-vertical lookup protocol. Mandate discovery before each agent action.
- §2
Revocation + lifecycle
Mandate updates, expiration, revocation. Audit-trail compliant.
- §3
Interop with AdCP / UCP / ACP / x402
AMDP runs ON TOP OF L0 transaction protocols. Bridges to existing standards.
- §4
Conformance tests
Reference implementation in Lean-4 + TypeScript suite.
- §5
Security model
PQC migration path (ADR-035), crypto agility, threat model.
Competitive Differential
Roadmap
- P1May–June 2026 (~3 weeks)AMDP v0.1 spec draft, IAB AAMP pre-submission conversation, Linux Foundation Agent WG pre-conversation
- P2June 2026 (~30.06. window)IAB Curation-Protocol-Q2 listing as co-authoring seat
- P3July–August 2026Linux Foundation Agent Infrastructure WG proposal
- P4September–October 2026v1.0 spec + reference implementation (Lean-4 + TypeScript)
- P5Q4 2026nexbid.dev platform-hero slot "AMDP" as 4th platform theme