DDealer Agent
ProtocolApply for the pilot →

Gateway ingestion

Feeds first. Scraping only when it earns its place.

Dealer Agent Protocol defines the answer contract. A Dealer Agent Gateway maps dealer-approved sources into that contract—and keeps each field’s source, timestamp, and authority attached.

Use the strongest available source for each fact.

  1. 1Authorized feed or API

    Use a dealer-approved inventory manager, website provider, or licensed data integration where available.

  2. 2Scheduled dealer export

    Accept CSV/SFTP, object storage, or HTTPS exports, including the open Dealer Agent Inventory CSV profile.

  3. 3Structured web publication

    Read documented endpoints, JSON-LD, inventory sitemaps, and stable vehicle-detail fields on a dealer-authorized domain.

  4. 4Consented extraction

    Crawl only as a bootstrap or gap-filler, then reconcile it continuously against the dealer’s approved sources.

The implementation boundary

Many sources enter. One controlled retail contract leaves.

The protocol stays source-neutral. Vendor credentials and raw source data remain behind the gateway. An agent receives only approved retail facts with the evidence needed to interpret them correctly.

New vehicles and incentives are two different data problems.

Base vehicle inventory can come from a dealer-approved vAuto, HomeNet, Dealer.com, or comparable export. Incentives need their own evidence path because a program can depend on model, geography, finance source, ownership, occupation, expiration, and stacking rules.

Never scrape a rebate amount and assume every shopper qualifies. Prefer a licensed incentive feed or dealer-approved merchandising source. When only a public offer is available, return it as conditional evidence with its source URL, observation time, expiration, geography, and unresolved eligibility rules.

A dealer-maintained campaign file can bridge a missing provider feed during a pilot, but the dealer remains the publishing authority and must approve the mapping.

Use vAuto, HomeNet, or the website—without flattening the evidence.

An authorized inventory export is the preferred path for stock identifiers, mileage, stocked dates, price, photos, merchandising details, and removal events. Website extraction can bootstrap the connection or fill public merchandising gaps.

CARFAX, AutoCheck, and equivalent sources connect only under the dealer’s applicable provider rights. The gateway keeps separate report identifiers, timestamps, access methods, and conflicts. “No events reported” never becomes “accident-free.”

See the used-vehicle profile →

A crawl is evidence, not authority.

  • Dealer authorization for the domain and intended use
  • Respect for robots policy, applicable terms, rate limits, caching, and backoff
  • Preference for JSON-LD, sitemaps, and stable structured fields
  • Source URL, retrieval time, content digest, and extraction version on every record
  • Fast removal checks and stale-data cutoffs
  • Quarantine for surprising VIN, mileage, price, or availability changes
  • No bypass of authentication, access controls, or anti-bot measures

Firecrawl can power this consented adapter during a live pilot. It is not required for the protocol, the synthetic reference gateway, or feed-based integrations.

Read the implementation guide →

Founding dealer pilot

Bring one rooftop and the sources you already control.

Apply for the pilot →

Source review · field mapping · seven-day reconciliation