Status
What exists, and what does not yet
Enough to invite scrutiny, not enough to claim adoption.
-00
An individual Internet-Draft, draft-rapp-ammp-00, posted on 22 October 2026, with 121 conformance fixtures and a validator that uses only the standard library. Its internal version (v3.1.0, wire contract_version "2") reflects iteration before it reached the IETF, not a settled design.
10
Document types, each with a published JSON Schema and fixtures that must pass and must fail.
0
Third-party dependencies in the Claude Code connector that runs beside the agent: small enough to audit.
10 agents · 1 week
Claude agents working together through AMMP, and finding real defects in the specification.
Open, so it can be checked
All five repositories are public under the Apache License 2.0:
- amap-spec: the specification, JSON Schemas, conformance fixtures, and the Internet-Draft rendering
- amap-router-local: the reference runtime
- amap-connector-claude: the Claude Code connector
- amap-connector-codex: the Codex connector
- amap-deploy-sandy: a working deployment of the two on one host, with a walkthrough that gets two agents talking
Anyone can test any vendor's runtime or connector against the public fixtures, plus the operational checks the specification requires. Passing the fixtures alone isn't conformance (§ Conformance). See For implementers.
Built with itself
- Early AMMP carried the work of building AMMP. Agents developing the specification and the reference implementations coordinated through early versions of the protocol.
- The specification and its implementations matured together. The specification, the reference runtime and the Claude Code connector grew up side by side.
- Fleet week. Once the protocol and implementations could support it, ten sandboxed Claude agents, each owning a repository, worked together through AMMP for one week. They ran a conformance sweep, a security audit and a multi-repository release.
The fleet found defects in the specification itself, not only in code:
- Two clauses of the submit-request section collided: reply binding versus "never transmit to an unnamed address".
- A validator ignored its arguments and reported green for the wrong reason.
- Mutation testing showed that only 44 of 301 schema constraints were pinned by any fixture.
Since then a second connector, for Codex, has run in the same fleet with the reference runtime, delegating to Claude agents and answering them in both directions: several cooperating agents from more than one model vendor, each deployment still under a single operator.
This is evidence of agent-to-agent use under one operator. It is not yet evidence of adoption across organisations.
Next
The IETF
The -00 is posted. Next is the dispatch process and, if there is interest, a BoF; the next meeting is IETF 127, 14–20 November 2026. AMMP is an individual draft, adopted by no working group, and not an IETF standard. See AMMP at the IETF.
Partners
We're looking for development and interop partners, starting with a first deployment across independent organisations. There isn't one yet.
Agent platforms
We're seeking collaboration across agent platforms, as more connectors mean a stronger test of the specification.