Reference Implementation · Live in Production · Salt Lake City

The First ARM.

The world’s first working Agent Relationship Manager. Created by Chris Hudson and Ben Reuling. Deployed at a real dealership, Mark Miller Subaru, handling real agent traffic across three open protocols. First deployment April 2026. The first agent-to-agent deal in U.S. history closed through it on May 4, 2026.

The rubric was a definition. This is the definition running.

LIVE
System status
3
Protocols active
334ms
P95 latency
6·2·2
Live · Constrained · Building
MCPModel Context Protocol LIVE
A2AAgent to Agent LIVE
UCPUniversal Commerce Protocol LIVE
AP2Authorize Payments PLANNED
AG-UIAgent-User Interaction PLANNED
A2UIDeclarative Generative UI PLANNED
MCP

Model Context Protocol

The primary protocol for agent-to-tool communication. Agents using MCP connect directly to inventory, pricing, and availability data. The dominant traffic source in the current deployment.

A2A

Agent to Agent

An open protocol for agent-to-agent communication, governed by the Linux Foundation. The channel through which the dealer’s agent and the buyer’s agent speak directly at machine speed.

UCP

Universal Commerce Protocol

An open commerce protocol developed by Google with Shopify, Walmart, Target, and over 20 global partners. Every interaction produces a signed, cryptographically provable record.

In production

Five surfaces. Running today.

Audit logReal-time, across MCP, A2A, and UCP
Live inventory636 vehicles at last count, machine-readable
TrendsThe reservation funnel, visualized
Pricing surfaceFees and disclosures, controlled per rooftop
A2A consoleTest the protocol against the live deployment

This site was a manifesto. Now it is documentation. The next dealer to join will not build any of this from scratch. The work has been done.

Scored against its own standard

Ten criteria. Honest marks.

An ARM that grades itself on a curve is not a standard, it is a brochure. Here is exactly where this implementation stands, and where each claim can be checked.

CRITERION 01

DetectLIVE

Agent traffic is classified at entry by protocol. MCP, A2A, and UCP sessions separate from human sessions before routing begins. Every interaction tagged at ingestion. Hound extends detection to the public web surface.

CRITERION 02

DeployCONSTRAINED

The deployment's transacting agent is in production and meets buyer agents autonomously. Today it transacts at asking price: quotes, availability, 30-minute soft holds, deal handoff. The negotiation tools (submit_offer, counter, accept, reject) are defined in dmc-12 v0.2 and not yet enabled at the reference deployment. When they turn on, this line changes. Not before.

CRITERION 03

EnforceCONSTRAINED

Pricing, doc fees, and tax disclosure are encoded in the schema and held on every quote. No parameter in the public surface accepts a proposed price. That is the strictest enforcement posture there is: the machine cannot be moved off the listed number. Parameter-band enforcement ships with negotiation.

CRITERION 04

RouteLIVE

Agent and human leads travel separate paths from the moment they enter. Human leads route to the CRM. Agent leads route to the ARM. Same dealership, same inventory, two systems.

CRITERION 05

ReportLIVE

Agent activity reports as its own line. Requests, error rate, active agents, latency, throughput, tool mix, and the audit log, live in the dashboard.

CRITERION 06

AdaptBUILDING

The audit trail accumulating now is the training ground. The pattern engine that tunes the deployed agent on outcomes comes online next.

CRITERION 07

VerifyLIVE

Agent identity is verified cryptographically before any tool access. Named agents check against trusted registries. Advocates, scrapers, and probes each get a distinct response. No identity, no transaction.

CRITERION 08

OperateLIVE

A dedicated agent lane runs alongside the dealership stack, drawing on its tools when needed. Humans watch from the dashboard. Discovery and delivery stay human.

CRITERION 09

RememberLIVE

Every interaction carries a cryptographic trace. Identity, protocol, tool, status, latency, trace ID. Persistent, non-repudiable, queryable, 90-day audit trail. When an agent returns, the system knows it.

CRITERION 10

ForecastBUILDING

Forward projection of agent volume and margin impact from accumulated interaction data. The foundation is the audit trail being written today.

Don’t take this page’s word for it. Every live claim maps to a public, unauthenticated document: the Agent Card, the MCP server card, the UCP manifest, the JWKS. Check the well-knowns at dmc-12.ai.

The architecture

Five pillars. One system of record.

01

Agent Registry

Every agent that transacts has an identity, authorized capabilities, and a verifiable key. No identity, no transaction.

02

Trust and Reputation

Every interaction produces signal. Success rate, latency, adherence to terms. Reputation gates access the way credit scores gate lending. The dataset is building in real time.

03

Interaction Logging

Every call, every commitment, recorded with a cryptographic trace. This pillar operates in production today.

04

Protocol Management

The rules of engagement are explicit, versioned, machine-readable. Partners read a schema and plug in. No phone calls. No PDFs.

05

Human Escalation

The conditions that route a transaction to a person are written into the protocol itself. The schema is the policy.

The window

Three conditions. All true right now.

Machine-to-machine identity is commodity. The protocol specs are mature enough to publish a manifest and be discovered by any major agent runtime. And the counterparty exists: buyer agents crossed from research to revenue, and one of them closed a deal against this system on May 4, 2026.

Anyone building an ARM can measure their progress against what is already running.


The CRM was the infrastructure of the human lead era. This is the first infrastructure of the agent era.