# Why automotive needs AAP **A connected tool still needs to explain what its data means.** Does a price include required fees? Does a feature exist on this vehicle? Is a test drive booked, or merely requested? ![Separate custom integrations converge on one automotive contract that works through MCP, A2A and PAP](https://autoagentprotocol.org/docs/v3.0/img/why-before-after.svg) AAP makes those answers consistent across dealerships and protocols. | Automotive question | AAP contract | |---|---| | Is this listing still eligible? | Controlled availability and a source update timestamp | | Does it meet the buyer's constraints? | Declared filters, evidence, radius/distance and complete pagination | | Which price can I compare? | Authoritative advertised price with mandatory dealer charges included | | May I contact this dealer for the buyer? | An explicit consent grant for this payload and these channels | | What happened after submission? | A lead ID, deduplicated retries and an explicit appointment outcome | ## Built on the protocols agents use ![MCP tools, A2A DataParts and PAP OpenAPI reuse the same automotive operations](https://autoagentprotocol.org/docs/v3.0/img/architecture-stack.svg) | Standard | Its role in AAP 3.0 | |---|---| | [MCP](https://modelcontextprotocol.io/) | Native, self-describing tools with complete schemas and structured results | | [A2A](https://a2a-protocol.org/) | Agent Card discovery and typed automotive messages | | [Personal Agent Protocol](https://personalagentprotocol.org/docs/0.3/spec) | Company identity, guest Sessions, DPoP and native APIs | | [ADF/XML](https://autoagentprotocol.org/docs/v3.0/compatibility/adf-mapping.md) | A practical delivery bridge to existing dealer lead systems | AAP supplies automotive semantics and uses each protocol's own transport and authentication rules. An operator can route all three interfaces to the same inventory, pricing and lead services. ## A vertical contract with a clear boundary Cars, electric vehicles, motorcycles, RVs and trailers share the same five skills. Vehicle-specific fields carry range, charging, engine displacement and other known attributes without changing the call flow. ![Cars, electric powertrains and motorcycles share identity, pricing, evidence and availability](https://autoagentprotocol.org/docs/v3.0/img/multi-class-inventory.svg) The release covers research and consented dealer contact. It does not define checkout, payments, credit decisions or binding valuations. An accepted lead is a conversation starter; a confirmed appointment is an explicit, separate outcome. Use [conformance](https://autoagentprotocol.org/docs/v3.0/conformance.md) to distinguish a validated contract from a verified deployment. Publishing discovery alone does not implement the service, prove a client's support, or establish universal agent adoption.