Dealer Agent
Protocol Free AI Answer Audit

Dealer Agent Protocol · Version 0.1 open for review

Give every shopping agent the same retail truth.

Dealer Agent Protocol gives AI agents one precise way to read dealer-published vehicles, verify availability, and explain prices and offers—without exposing the DMS or CRM.

Get a free AI Answer Audit Why this is different
  • 10defined tools
  • 6profiles
  • 12canonical schemas
  • 49behavior checks

The adoption problem

Dealer facts exist.
Agent-ready meaning does not.

Inventory feeds, website pages, incentive programs, and availability signals describe different parts of the retail offer. An agent that scrapes and guesses can merge them incorrectly.

The protocol defines the answer contract: what a fact means, who published it, how fresh it is, and what remains conditional or unknown.

Protocol ≠ gateway

The protocol is the rulebook. The gateway is software that follows it.

OPEN SPECIFICATION

Dealer Agent Protocol

Defines the shared tool names, schemas, retail meaning, pricing disclosures, trust fields, and conformance rules.

Anyone can implement it.
REFERENCE SOFTWARE

Dealer Agent Gateway

Connects approved dealer sources, applies policy, and serves protocol-compliant MCP tools to agents.

One implementation of the protocol.

MCP is the transport between an agent and a gateway. Dealer Agent Protocol defines what the retail tools and answers mean.

One boundary · many consumers

Keep the integrations behind the gateway. Publish only the retail facts agents need.

Dealer Agent Protocol is the open contract between the gateway and agents. MCP carries the calls. The protocol supplies the retail vocabulary, schemas, disclosure rules, and conformance claims.

Walk through the complete system · See how the gateway gets inventory

From question to grounded answer

Five steps an agent can follow instead of improvising.

  1. 01Discover

    Learn the gateway, supported profiles, dealer, and rooftop.

    get_manifest
  2. 02Search

    Find published vehicles with stable filters and cursors.

    inventory.search
  3. 03Inspect

    Read the exact vehicle facts, media, and source lineage.

    get_vehicle
  4. 04Verify

    Check a fast-changing availability fact against authority.

    verify_availability
  5. 05Explain

    Separate advertised price, required charges, and conditional offers.

    get_disclosure

Why each side adopts

One contract. Three practical wins.

01

For dealers

Control what an agent can claim.

Publish only approved retail facts and policies—including used-vehicle history, inventory age, and condition. Keep internal records outside the boundary.

See used-vehicle truth →
02

For retail technology providers

Build one agent-facing contract.

Map existing feeds and APIs behind a gateway, then expose consistent schemas across rooftops without replacing systems of record.

Provider path →
03

For agent builders

Stop reverse-engineering every dealer.

Use typed, discoverable read tools for inventory and offers, with explicit freshness, authority, and uncertainty in every result.

Builder path →

A deliberate first boundary

Retail facts in.
Dealer-controlled.

Version 0.1 focuses on the facts an agent needs to help someone understand a vehicle and its retail offer.

+ The retail read

  • Dealer and rooftop identity
  • Published vehicle inventory
  • Used mileage, history, condition, and inventory age
  • Authoritative availability
  • Advertised price and dealer charges
  • Discount and incentive conditions
  • Provenance, freshness, uncertainty

Founding dealer pilot

Start with one rooftop. Prove the answers before agents repeat them.

Apply for the pilot Read the human guide

Applications open · Private evaluation · No customer data

Open project

Built in public for shared adoption.

01

Apache-2.0

The specification, schemas, examples, tests, websites, and reference gateway are available under the Apache License 2.0, including its explicit patent grant.

Read the license →
02

Contribute

Propose protocol changes, improve schemas and tests, or strengthen the reference gateway. Normative changes require a concrete interoperability case.

Contribution guide →
03

Creator

Dealer Agent Protocol and Dealer Agent Gateway were created by Ariel Coro, with future improvements welcomed from public contributors.

Ariel Coro on GitHub →