Agents are already merchandising inventory, quoting deals, and answering leads on dealers' behalf — but every team reverse-engineers the rules by hand. Feed shapes, DMS writebacks, ADF-XML, credit apps, title math, OEM co-op. None of them knows when a spec changes.
DealerSchema is the standard sitting between agents and dealer systems — a versioned specification, a public registry of conforming schemas, and documented methods for verifying each one. Open, versioned, verifiable.
{
"id": "vendor.homenet.feed.v1.4",
"spec": "dealerschema/v1.0",
"version": "v1.4",
"category": "inventory",
"jurisdiction": "vendor: HomeNet iOL",
"status": "verified",
"verifiedAt": "2026-06-14",
"source": "https://iol.homenetauto.com/…",
"consumedBy": ["merchandiser", "pricing"],
"fields": [ /* typed field list */ ],
"rules": [ /* validation bullets */ ]
}v1.0 is the first stable cut of DealerSchema. Every entry in the registry conforms to the same envelope, the same versioning rules, and the same verification fixtures — so an agent written against v1 will still parse when a franchise or state adds a field next quarter.
Every registry entry ships id, spec version, category, jurisdiction, verification date, source, consuming agents, typed fields, and validation rules.
Breaking changes bump the major. Jurisdiction (US-TN, OEM: Ford, vendor: HomeNet) is part of the id so state and franchise deltas never collide.
Every schema ships with sample payloads and rule assertions. CI in the reference repo re-verifies against live sources on a rolling schedule.
Schemas declare which agent roles (merchandiser, pricing, concierge, chief, ads, reputation, trade) are expected to read or write them.
Field additions, deprecations, and jurisdiction expansions land through an open RFC in /spec/rfc — with a 14-day comment window before merge.
Spec, schemas, and fixtures are MIT. Pitlane maintains the reference registry; anyone can fork it, mirror it, or ship a competing implementation.
{
"id": "vendor.homenet.feed.v1.4",
"spec": "dealerschema/v1.0",
"version": "v1.4",
"category": "inventory",
"jurisdiction": "vendor: HomeNet iOL",
"status": "verified",
"verifiedAt": "2026-06-14",
"source": "https://iol.homenetauto.com/...",
"consumedBy": ["merchandiser", "pricing"],
"fields": [ /* typed field list */ ],
"rules": [ /* validation bullets */ ]
}The open, versioned format every schema conforms to. Deterministic dotted paths, semantic versions, jurisdiction scoping.
The public index of published schemas and their versions. 33 reference schemas across inventory, leads, pricing, DMS writeback, compliance, F&I, OEM programs, and titling.
How each schema is checked against its live source — vendor spec, government bulletin, or OEM program guide. Every entry ships with a verification date.
Every entry has a deterministic ID, a version, a jurisdiction, a live source, and a verification date. Click any row to inspect fields, rules, and the Pitlane agents that consume it.
DealerSchema is founded by Pitlane and built to be governed as an open foundation. More dealers, more vendors, and more jurisdictions make the standard better. If you work on dealer agents, or you own a piece of dealer infrastructure, review the registry and propose a schema.