# Auto Agent Protocol > Auto Agent Protocol (AAP) is an open automotive contract for dealership discovery, inventory, pricing and consented inquiries. Current release 3.0.0 (contract v3.0). Interfaces: native MCP Streamable HTTP tools; A2A 1.0 SendMessage; Poppy draft 0.3 guest OpenAPI with DPoP. This website publishes the specification and examples. It is not a dealer inventory service or a live MCP endpoint. Find working services through a dealership's own discovery documents and use the exact advertised URLs, capabilities and contract version. The links below prefer readable Markdown. Every documentation page also advertises its corresponding Markdown representation with an HTML alternate link. Schemas define payload validation; normative prose defines behavior and security obligations. ## Start here - [AAP FAQ](https://autoagentprotocol.org/faq): purpose, native interfaces, discovery and adoption - [Introduction](https://autoagentprotocol.org/docs/v3.0/intro.md): The automotive contract for AI agents, with native MCP tools, A2A messages and PAP guest APIs. - [Why automotive needs AAP](https://autoagentprotocol.org/docs/v3.0/why.md): General agent protocols connect systems. AAP gives them a consistent automotive vocabulary and behavior. - [Dealer-domain discovery](https://autoagentprotocol.org/docs/v3.0/discovery.md): One dealership identity, three working interfaces, and a readable llms.txt entry point. - [Versions and migration](https://autoagentprotocol.org/docs/v3.0/versioning.md): AAP 3.0 migration, independent upstream versions, and immutable release artifacts. - [Contributing](https://autoagentprotocol.org/docs/v3.0/contributing.md): How to propose and validate changes to the editable AAP specification. ## Bindings - [MCP binding](https://autoagentprotocol.org/docs/v3.0/bindings/mcp.md): Native automotive tools over MCP Streamable HTTP, with complete schemas, structured results and current and legacy client support. - [A2A profile](https://autoagentprotocol.org/docs/v3.0/a2a-profile.md): Typed automotive DataParts in A2A 1.0 SendMessage, with optional redundant headers on contract-pinned AAP endpoints. - [A2A JSON-RPC binding](https://autoagentprotocol.org/docs/v3.0/bindings/json-rpc.md): Complete A2A 1.0 headers, messages and errors for the shared automotive contract. - [Personal Agent Protocol](https://autoagentprotocol.org/docs/v3.0/personal-agent-protocol.md): Normative AAP 3.0 profile of Poppy draft 0.3, with paired discovery, guest sessions, DPoP, automotive APIs and migration. - [PAP client walkthrough](https://autoagentprotocol.org/docs/v3.0/pap-client-guide.md): Discover a PAP 0.3 dealer, authenticate a guest session and search inventory with verifiable protocol evidence. ## Skills - [dealer.information](https://autoagentprotocol.org/docs/v3.0/skills/dealer-information.md): Dealership identity, physical locations, hours and contact details through the same read skill on all three bindings. - [inventory.facets](https://autoagentprotocol.org/docs/v3.0/skills/inventory-facets.md): Discover actual inventory values, ranges and feature vocabulary before constructing a search. - [inventory.search](https://autoagentprotocol.org/docs/v3.0/skills/inventory-search.md): Find matching vehicles with verified equipment, geographic distance, explicit filters and cursor pagination. - [inventory.vehicle](https://autoagentprotocol.org/docs/v3.0/skills/inventory-vehicle.md): Verify one listing's identity, availability, evidence and authoritative price. - [lead.submit](https://autoagentprotocol.org/docs/v3.0/skills/lead-submit.md): One consented inquiry, an explicit appointment outcome, and safe retries across all three bindings. ## Implementation - [Behavior rules](https://autoagentprotocol.org/docs/v3.0/behavior-rules.md): Shared rules for truthful inventory, evidence, pricing, consent, retries and observability across MCP, A2A and PAP. - [Pricing and fee disclosure](https://autoagentprotocol.org/docs/v3.0/pricing-and-ftc.md): One authoritative advertised price, optional included-fee detail, and precise treatment of unknown prices. - [Errors and retries](https://autoagentprotocol.org/docs/v3.0/errors.md): One typed automotive error, three protocol envelopes, and explicit recovery rules. - [Conformance and verification](https://autoagentprotocol.org/docs/v3.0/conformance.md): What full AAP 3.0 support requires, what this repository verifies, and what each deployment must prove. ## Compatibility - [ADF/XML mapping](https://autoagentprotocol.org/docs/v3.0/compatibility/adf-mapping.md): Map a consented AAP lead into an existing CRM workflow while retaining the complete AAP record and consent audit. - [Migrating MCP integrations](https://autoagentprotocol.org/docs/v3.0/compatibility/mcp.md): Move from the optional AAP wrapper catalog to the first-class AAP 3.0 MCP binding. - [Legacy REST binding](https://autoagentprotocol.org/docs/v3.0/bindings/rest.md): The historical A2A HTTP+JSON option was removed in AAP 1.1. Use the current MCP, A2A JSON-RPC or PAP binding. ## Machine-readable artifacts - [MCP reference tool catalog](https://autoagentprotocol.org/v3.0/mcp.json): tool definitions, not a running MCP endpoint - [A2A JSON-RPC OpenAPI](https://autoagentprotocol.org/v3.0/openapi-jsonrpc.yaml): the automotive SendMessage binding - [PAP OpenAPI](https://autoagentprotocol.org/v3.0/openapi-poppy.yaml): native automotive operations with guest Sessions - [Agent Card example](https://autoagentprotocol.org/v3.0/examples/agent-card.example.json): replace fictional identity and deployment URLs - [Poppy discovery example](https://autoagentprotocol.org/v3.0/examples/poppy.example.json): PAP identity, issuer and API discovery - [Dealer llms.txt example](https://autoagentprotocol.org/v3.0/examples/llms.txt.example.md): exact MCP URL, discovery links and access requirements - [Agent Card schema](https://autoagentprotocol.org/v3.0/schemas/agent-card.schema.json): JSON Schema 2020-12; other payload schemas share this versioned directory - [Full specification](https://autoagentprotocol.org/llms-full.txt): the complete stable documentation in one Markdown file - [Source repository](https://github.com/auto-agent-protocol/auto-agent-protocol): schemas, tools, examples and release history ## Ecosystem - [Public ecosystem register](https://autoagentprotocol.org/partners): implementations and upstream organizations; a listing is not certification of AAP 3.0.0 - [A2A Protocol](https://a2a-protocol.org): Upstream standard. The Agent2Agent open standard that AAP profiles. A2A defines how independently built AI agents discover one another and exchange typed messages; AAP adds the automotive vocabulary on top of A2A v1.0 without changing the wire. Accepted in August 2026 as a Growth Stage project at the Agentic AI Foundation, which A2A describes as Linux Foundation-directed. - [Dealer Handshake](https://dealerhandshake.com): AAP implementation. Connects dealership inventory to compatible AI assistants and routes consented leads to dealer CRMs as ADF. Its Car Handshake marketplace publishes a versioned AAP Agent Card exposing dealer information, inventory facets, search, vehicle detail and consented inquiries over A2A JSON-RPC. Check that live card for the deployed contract version. - [Space Auto](https://space.auto): Dealership platform. Unified dealership platform covering websites, digital retailing, AI-powered CRM, automation, and analytics for franchise and independent retailers, with DAISI as its AI assistant layer. Space Auto, Inc. is based in Dallas, Texas, and joined the A2A Protocol partner ecosystem in July 2026.