discovery.get_manifestKnow the server
Profiles, versions, resources, limits, and access policy.
System explainer
The protocol does not replace dealer systems. It creates a controlled translation layer between those systems and AI shopping experiences.
The dealer or its technology provider chooses authoritative sources and publication policy. The gateway maps those sources into protocol schemas. Agents consume the same tool contract regardless of the systems behind it.
Layer 1 · retail sources
Layer 3 · consumers
Search results are for discovery. Availability verification is a separate authoritative check. Pricing disclosure keeps universal amounts separate from conditional ones.
The agent reads the manifest and dealer identity before assuming what the gateway supports.
The agent searches the published catalog using typed filters and snapshot-aware pagination.
The exact vehicle record supplies facts, media, identifiers, provenance, and freshness.
Before making a strong availability statement, the agent asks the authoritative source.
The response separates advertised price, required dealer charges, conditional adjustments, and unknown government charges.
discovery.get_manifestProfiles, versions, resources, limits, and access policy.
dealer.getDealer organization and rooftop identity.
inventory.searchPublished inventory with stable filtering and cursors.
inventory.get_vehicleVehicle facts, media, identifiers, lineage, and freshness.
inventory.verify_availabilityA current, authoritative read before a strong claim.
pricing.get_disclosurePrice components, required charges, and conditional programs.
Where did this fact originate: dealer, group, OEM, inventory provider, or another named source?
When was it observed, and until when should the agent treat it as valid?
Is this source authoritative for the claim, or only suitable for discovery?
Is the fact confirmed, estimated, conditional, stale, or unknown?