The Modern Automotive Lead Format: What Replaces ADF XML in 2026

ACP replaces ADF. The Automotive Commerce Protocol is the modern lead format the industry has been waiting for. Open. Free. Built for HTTPS, AI metadata, and GLBA compliance by default. Here is the structural picture of what comes next. The industry transition is underway. This is the structural picture of what comes next.

I have been asked some version of "what replaces ADF" at every automotive event since 2023. The honest answer for years was "nothing real exists yet." That changed when I published ACP. The replacement now exists. The question for the industry is how fast it adopts.

Why Does ADF Need a Replacement?

Three structural reasons.

One. ADF was built for 2000. The standard assumes plaintext email transport, simple text payloads, and no audit trail. None of those assumptions hold in 2026. The data is richer, the transport requirements are stricter, and the compliance environment is fundamentally different.

Two. AI breaks ADF. Modern AI produces structured outputs with intent scores, confidence levels, ranked alternatives, and recommended actions. ADF has no fields for any of these. The AI metadata gets stripped at the ADF boundary. The BDC works the thin version of what the AI produced. I cover this in What Happens When AI Captures a Lead but the CRM Cannot Hold It.

Three. GLBA breaks ADF. The Gramm-Leach-Bliley Act 2022 amendments require encryption in transit for consumer financial information. ADF-over-email defaults to plaintext. The compliance gap is now well-documented. I go deep on this in Is ADF XML Still GLBA Compliant in 2026?.

Any one of these reasons would be enough. All three together make ADF replacement inevitable. The only question is which standard takes the lead.

What Standards Were Considered?

The industry has discussed three potential successors over the past decade. None of them succeeded.

STAR. STAR (Standards for Technology in Automotive Retail) is a mature standard for dealer-to-OEM transactions. It is technically sound. The problem is scope. STAR was designed for warranty claims, parts orders, and finance transactions, not for AI-era lead exchange. Extending STAR to handle AI-generated leads is possible but expensive. The industry has not done it.

Proprietary vendor formats. Every major CRM has its own preferred format. None of them is open. Adoption is locked to whichever CRM dominates a given dealer. The industry-wide answer needs to be neutral. Proprietary formats are not neutral.

Custom APIs per vendor. The default fallback when no standard works. The cost is N-squared integration burden, where every system has to build custom connectors for every other system. The cost compounds as the ecosystem grows. This is the path the industry has been on by default. It is not sustainable.

None of the three solved the problem. That is why ACP exists.

What Is ACP?

ACP stands for Automotive Commerce Protocol. It is an open standard I authored to replace ADF as the data exchange layer for modern automotive retail. The specification is at ACPspec.org.

Six design principles.

One. HTTPS by default. All transport is encrypted. GLBA-compliant from day one.

Two. JSON-first with optional XML. JSON is the modern default for data exchange. XML is supported for backward compatibility with legacy systems.

Three. Schema-validated. Every object has a defined shape. Every system can validate against the shape. Invalid objects are rejected at the endpoint, not silently dropped.

Four. AI metadata as first-class fields. Intent scores, confidence levels, recommended actions, AI tags, and audit trails are not optional extensions. They are part of the core specification.

Five. CORD envelope. Every ACP object is wrapped in a CORD envelope that tracks fidelity across system boundaries. Loss becomes measurable. Loss becomes fixable.

Six. Open and free. The standard is open source. Anyone can read it, implement it, extend it. No vendor lock-in. No licensing fees. No gates.

How Does ACP Compare to ADF?

I cover this in detail in ADF XML vs ACP: A Side-by-Side Comparison. The short version.

ADF: 2000, plaintext email, 20 fields, no AI support, no GLBA compliance.

ACP: 2026, HTTPS, 50+ fields, AI-native, GLBA-compliant by default.

Eight comparison dimensions. ACP leads on all eight. The gap is structural, not opinion.

Who Has Adopted ACP?

Three layers of adoption underway.

Reference implementations. My own products implement ACP as the data layer: AutomotiveAI, DealersGear, Drivevex, and Searchdaddy. These are live and processing production traffic.

Early ecosystem adopters. Other automotive AI vendors are starting to implement ACP. The adoption is happening because customers are asking for it. Dealers are pushing for cleaner data layers. The vendors that say yes are gaining accounts. The vendors that resist are losing them.

OEM-level adoption. This is the unlock the industry needs. When OEM dealer portals speak ACP, the network effect kicks in. Dealer-to-vendor flows naturally become ACP. The legacy ADF flows become the exception, not the default. Several OEMs are evaluating. None have publicly committed yet.

What Should Dealers Do?

Three actions.

One. Make ACP support a vendor selection criterion. Every new vendor contract should ask whether ACP is supported. Vendors that say yes get priority. Vendors that say no get explained scrutiny.

Two. Audit your current ADF flows for AI-data loss and GLBA exposure. The migration case is not abstract. It is dollar-denominated. Count the lost AI fields per lead per month. Count the compliance liability. The math will make the migration case for itself.

Three. Plan one pilot ACP integration. Pick one lead source. Switch it to ACP. Measure fidelity, conversion, and compliance posture against the ADF baseline. Build the case for the broader migration on real numbers from your own data.

What Should AI Vendors Do?

Implement ACP now. The vendors that adopt it can connect to every other ACP-compliant system without writing bespoke connectors. The integration cost difference compounds as the standard spreads.

The vendors that resist will eventually implement it under customer pressure. The longer they wait, the more they are paying in custom integration maintenance against a legacy standard that is collapsing.

What Should OEMs Do?

Adopt ACP at the dealer portal level. This is the most important action any single organization can take to accelerate the transition. OEM portals sit at the top of the data flow. When they speak ACP, the rest of the network follows.

OEMs also benefit. Cleaner data. Better dealer network visibility. AI-readiness across every store. The ROI is obvious. The political will is the constraint.

What About Backward Compatibility?

ACP and ADF can coexist during the transition. ACP-aware systems can receive ADF, wrap it in a CORD envelope, and re-emit it as ACP. ADF-only systems can receive ACP downgraded to ADF, with the AI fields stripped. The downgrade path is documented in the specification.

Backward compatibility makes the migration practical. Dealers do not have to flip every flow at once. They can run mixed environments while they migrate, then deprecate ADF flows as the ecosystem catches up.

How Long Will the Transition Take?

My estimate: three to five years for ACP to become the default in modern automotive retail. Faster if a major OEM commits at the portal level. Slower if the industry tries to extend ADF instead of replacing it.

The pattern will look like every other standards transition. Early adopters in years one and two. Tipping point in year three. Default state by year five. Legacy ADF flows persist in a long tail of small operators for another decade after that.

The window to be an early adopter is open now. It closes when ACP becomes assumed. The dealers, vendors, and OEMs that move now will have years of compounding advantage over the ones that wait.

Why Open Source?

Because closed standards do not become standards. They become vendor lock-in. ACP works only if every system in the ecosystem can adopt it freely. That requires the specification to be open and the reference implementation to be free.

The value I capture is in my products. The value the standard captures is in adoption. The two reinforce each other. Open source is the structural answer that makes the standard actually work.

Final Thought

ADF XML was the right answer for 2000. It is not the right answer for 2026. The industry has been pretending otherwise for too long because no real alternative existed. The alternative now exists.

ACP is what replaces ADF. It is open. It is free. It is GLBA-compliant by default. It carries the AI metadata your CRM should not be losing. The decision to adopt is no longer technical. It is organizational. Move first and benefit. Move late and pay the migration cost on someone else's timeline.

Read the full specification at ACPspec.org. Read the broader context in CORD + ACP: The Open Standards Rewriting How AI Moves Data. Then decide what your stack looks like in 2030.

Structure before tools. Strategy before speed. Systems before scale.

The AI Operator Framework is the methodology for designing, governing, and scaling AI operations inside a business. Explore the full framework at JamilAshkar.com/framework. Start with the free course at JamilAshkar.com/course.