An A2A Profile
AAP is a strict A2A v1.0 profile: typed automotive messages ride on top of A2A's data layer. The JSON-RPC binding is required everywhere; HTTP+JSON can be added — the payloads are identical.
Five Skills
dealer.information, inventory.facets, inventory.search, inventory.vehicle, lead.submit. Everything a BDC needs in one unified contract.
FTC-Aware Pricing
Four explicit pricing fields (msrp, list_price, offered_price, price). The price field carries the final out-the-door amount a buyer can actually pay — AAP's rule against bait pricing, aligned with FTC guidance.
Anonymous First
Inventory operations are anonymous by default. Personal data only travels with leads, and only with an explicit ConsentGrant attached.
ADF-Mappable Leads
lead.submit is field-by-field convertible to ADF/XML, so any compliant lead drops cleanly into existing dealer CRMs without bespoke integration.
MCP Ready
An official MCP reference manifest maps every AAP skill to an MCP tool, so MCP hosts can adapt the same contract without speaking A2A directly.
Five skills, one contract
AAP standardizes the five skills that cover a dealership BDC's core needs — anonymous inventory queries plus a single unified lead.submit that bundles vehicle interest, trade-in, and appointment scheduling in one consented call. No quotes, no checkout, no payment scope. Just the read-and-lead lifecycle, typed and validated.
FTC-aware pricing, baked in
Vehicles carry four explicit pricing fields. The price field is the final out-the-door amount — what the buyer would actually pay; AAP requires it so agents never quote bait prices. msrp, list_price, and the regional offered_price sit beside it, so AI agents can give honest answers, in line with the FTC's push against hidden fees and bait pricing.
How AAP relates to other protocols
A2A
The base. AAP is a strict A2A v1.0 profile. Every AAP message rides inside an A2A DataPart.
ACP / UCP
Complementary. AAP focuses on automotive leads and appointments, not commerce checkout flows.
MCP
Complementary. AAP publishes an official MCP reference manifest mapping every skill to an MCP tool.
ADF/XML
Legacy bridge. lead.submit maps field-by-field to ADF/XML for existing dealer CRMs.