Version 0.1 · Human guide
Understand the protocol before reading the protocol.
This guide explains the decisions, boundaries, and implementation path in plain language. The versioned specification and schemas remain the normative source.
Choose your path
Core concepts
What the protocol standardizes, what stays behind the gateway, and how trust travels with data.
ImplementQuickstart
Build or evaluate the mandatory core retail read bundle.
Explain offersPricing model
Separate universal amounts, required charges, conditions, and unknowns.
ValidateConformance
Understand profiles, checks, claims, and compatibility expectations.
In one sentence
Dealer Agent Protocol is an open, read-only contract that lets AI agents discover dealer-published vehicles, verify availability, and explain retail pricing with source, freshness, authority, and uncertainty.
Version 0.1 scope
The first release defines one focused retail read: who is selling the vehicle, which vehicles are published, whether a specific vehicle is available, and how its price and offers should be explained.
| Core retail fact | What the agent learns |
|---|---|
| Dealer and rooftop identity | Who is publishing the inventory and retail offer. |
| Published inventory and vehicle facts | Which exact vehicles are being presented for sale. |
| Authoritative availability | Whether a specific vehicle is currently available, according to the designated authority. |
| Pricing and required charges | Which amounts apply to every buyer in the disclosed context. |
| Discount and incentive conditions | Which offers may apply and what must be true for eligibility. |
| Provenance and freshness | Where each fact came from and how recently it was observed. |