# ADF/XML mapping
The Auto-lead Data Format (ADF/XML) has been the de-facto standard for delivering leads to dealer CRMs for over two decades. AAP's [`lead.submit`](https://autoagentprotocol.org/docs/v1.0/skills/lead-submit.md) request is designed to translate losslessly to ADF/XML so a dealer's existing pipeline accepts the lead unchanged.
This page documents the field-by-field translation. The dealer agent (or the dealer's CRM adapter) generates the XML; the buyer agent only sends AAP JSON.
## Mapping table
| AAP field (`lead.submit.request`) | ADF element / attribute | Notes |
|---|---|---|
| `customer.first_name` + `customer.last_name` | `{first} {last}` | ADF expects a full-name node; AAP keeps first/last separate. The mapper concatenates with a single space. |
| `customer.email` | `...` | RFC 5322 email. |
| `customer.phone` | `...` | E.164 phone (e.g. `+14155550123`). ADF allows free-form phones; AAP normalizes to E.164. |
| `customer.address.address_line_1` / `_2` | `......` | Optional. |
| `customer.address.city` | `...` | Optional. |
| `customer.address.state` | `...` | Optional. ADF uses ``; AAP uses `state`. |
| `customer.address.zip` | `...` | Optional. ADF uses ``; AAP uses `zip`. The ADF mapper writes `` from `customer.address.country` when provided, defaulting to `US` otherwise. |
| `vehicle_of_interest.year` / `make` / `model` | `.........` | The required ADF trio. Provided either directly on `vehicle_of_interest` or by VIN-decoding the dealer-side listing. |
| `vehicle_of_interest.trim` | `...` | Optional. |
| `vehicle_of_interest.vin` | `...` | Optional but recommended. |
| `vehicle_of_interest.stock` | `...` | Optional. |
| `vehicle_of_interest.condition` | `` (one of `new`, `used`) | ADF accepts only `new` or `used`. AAP `cpo` MAPS TO `status="used"` AND a free-text `certified pre-owned` on the vehicle. |
| `vehicle_of_interest.body` | `...` | Optional. |
| `vehicle_of_interest.transmission` | `...` | Optional. ADF expects `A` or `M`; the mapper folds `automatic`/`manual` (and variants like `8-speed automatic`) accordingly. |
| `vehicle_of_interest.mileage` | `...` | Optional; typical for used. |
| `vehicle_of_interest.price` | `...` | Mapped from the AAP integer dollar amount (whole US dollars). |
| `appointment.appointment_type` | Implicit on the parent vehicle's `interest`: `test_drive` → ``; `trade_in` → the `` block; `sales` / `service` → the appointment lives in `` of the customer block. | ADF predates structured appointments. |
| `appointment.appointment_at` | `Requested appointment: 2026-05-03 11:00 PT` | Free-text in ``; CRMs route to the appointment desk. |
| `submitted_at` | `...` | ISO 8601 (e.g. `2026-04-30T10:15:10Z`). |
| `message` | `...` | Free-text user message. |
| `source_agent` | `{source_agent}` | Identifies the originating buyer agent (e.g. `chatgpt-shopping`). **Direct integration:** put `source_agent` in ``. **Lead-network delivery:** when an intermediary (e.g. the AAP platform) delivers the ADF, it MAY instead set `` to the network brand, carry `source_agent` in ``, and add `` for the network — `` always stays the selling dealership either way. |
| Dealer name (from the `dealer.information` rooftop `name`) | `...` | Dealer agent fills this from its own profile, not from the buyer agent. |
| `trade_in.year` / `make` / `model` / `trim` | A second `...` block with ``, ``, ``, `` | Trade-in vehicle goes in its own ADF `` block. |
| `trade_in.mileage` | `...` | Strongly recommended; ADF ``. |
| `trade_in.condition` | `...` | `excellent`, `good`, `fair`, `poor` map directly to ADF's `` enum. |
| `trade_in.vin` | `...` | Optional; recommended for accurate appraisal. |
Nothing in `consent` is part of ADF (the format predates structured agent consent). AAP's `ConsentGrant` is preserved alongside the lead in the dealer CRM as an audit record. AAP-specific fields without an ADF equivalent (`customer.preferred_contact`, `vehicle_of_interest.vehicle_id`, `vehicle_of_interest.msrp`/`list_price`/`offered_price`/`zip`) MAY be persisted as CRM extension fields or in ``.
## Concrete worked example
Given a [`lead.submit`](https://autoagentprotocol.org/docs/v1.0/skills/lead-submit.md) request bundling a vehicle of interest, a trade-in, and a test-drive appointment:
```json
{
"type": "lead.submit.request",
"customer": {
"first_name": "Anna",
"last_name": "Lee",
"email": "anna@example.com",
"phone": "+14155550123",
"preferred_contact": "email",
"address": {
"address_line_1": "200 Folsom St",
"city": "San Francisco",
"state": "CA",
"zip": "94105"
}
},
"consent": {
"granted_at": "2026-04-30T10:15:00Z",
"allowed_channels": ["email", "phone"],
"consent_text": "I agree to share my contact info with Demo Toyota about this 2022 Honda Civic, my Sunday test drive, and my Toyota Corolla trade-in.",
"source_agent": "chatgpt-shopping",
"scope": ["lead_submission"]
},
"vehicle_of_interest": {
"vin": "1HGCV1F30KA000001",
"year": 2022, "make": "Honda", "model": "Civic", "trim": "EX",
"condition": "cpo",
"body": "sedan",
"transmission": "automatic"
},
"trade_in": {
"year": 2014, "make": "Toyota", "model": "Corolla",
"condition": "good",
"mileage": 96000
},
"appointment": {
"appointment_type": "test_drive",
"appointment_at": "2026-05-03T18:00:00Z"
},
"message": "Interested in this Civic; can you confirm availability and best price with my trade?",
"source_agent": "chatgpt-shopping",
"submitted_at": "2026-04-30T10:15:10Z"
}
```
The dealer-side ADF/XML payload is:
```xml
2026-04-30T10:15:10Z
2022
Honda
Civic
EX
1HGCV1F30KA000001
sedan
A
certified pre-owned
2014
Toyota
Corolla
good
96000
Anna Lee
anna@example.com
+14155550123
200 Folsom St
San Francisco
CA
94105
US
Interested in this Civic; can you confirm availability and best price with my trade? Requested test-drive: 2026-05-03 11:00 PT.
chatgpt-shopping
Demo Toyota
```
Note:
- `condition: "cpo"` becomes `` PLUS `certified pre-owned`. Plain ADF has no certified value.
- `appointment.appointment_type: "test_drive"` becomes `interest="test-drive"` on the `vehicle_of_interest` block. AAP `trade_in` maps to a second ``.
- `appointment.appointment_at` is folded into the customer `` since ADF has no native appointment element.
- The dealer name `Demo Toyota` is filled from the dealer agent's own profile, not from the buyer agent's request.
- The user `message` and the appointment time land in customer ``.
- This example shows **direct** delivery, so `source_agent` (`chatgpt-shopping`) is the ``. Under **lead-network** delivery the network brand is the `` and `chatgpt-shopping` rides in `` (see the `source_agent` row above); `` is the selling dealership in both cases.
## What does NOT map to ADF
The ADF format predates structured agent consent. AAP's `consent` (`ConsentGrant`) is preserved alongside the lead in the dealer CRM as an audit record but does not have an ADF equivalent. Dealers typically:
- Persist the full `ConsentGrant` JSON in a separate consent table or audit log.
- Surface `consent.allowed_channels` to the dealer's BDC or CRM rules engine to decide which channels to actually use for follow-up (and to refuse unauthorized channels).
`consent` MUST NOT be silently dropped on the dealer side; it is a regulatory requirement that the buyer agent passes through.
## ADF compatibility flag
AAP defines `lead.submit` as ADF-compatible. When the request includes `vehicle_of_interest`, the lead carries enough context to populate ADF's required `` trio cleanly. When the request is customer-only (no `vehicle_of_interest`), it is forwarded into the dealer CRM as an ADF lead with a synthetic placeholder vehicle (e.g. omitted or left as a generic inquiry record), per the dealer's CRM conventions.
For implementation guidance on the receiving side, see your CRM vendor's ADF documentation; AAP does not specify wire-level ADF transport (FTP, SMTP, HTTP POST), only the field-level translation.