Skip to main content
Version: 3.0.0

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 PAPOpen full-size diagram

AAP makes those answers consistent across dealerships and protocols.

Automotive questionAAP 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 operationsOpen full-size diagram

StandardIts role in AAP 3.0
MCPNative, self-describing tools with complete schemas and structured results
A2AAgent Card discovery and typed automotive messages
Personal Agent ProtocolCompany identity, guest Sessions, DPoP and native APIs
ADF/XMLA 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 availabilityOpen full-size diagram

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 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.