AI Storefront
Browse the documentation

Group vs Market Model Mix

Whether a dealership group's model mix matches the market it sells in, and where the conquest gaps and overweights are.

This is the technical reference. For the price, a rendered sample and answers to common questions, see the Group vs Market Model Mix product page.

At a glance

Price $9.99 per run.
Tool name generate_group_model_mix
Scope reports:group-vs-market-model-mix
Built for Dealer Group

What it does

The model-mix comparison for one dealership group in one US state or nationally, used vehicles by default, from Sold Summary API v2 over a window of whole months (3 by default, up to 12): the group's top 25 models by units, each with its share of the group's sales, its share of the market's, the over/under index (group share divided by market share; 1 is the market's weight), and the median days to sell and median asking price at exit on both sides; the conquest gaps (the market's top 25 models the group sells at under half their market weight, largest market first); the overweights (models at 1.5 times their market weight or more, with the turn on both sides); and three reads from the numbers. The market is every sale in the scope, the group's own included. Units and shares add across the window; a median describes one month and is read from the latest month with 5 or more priced sales. From the Sold Summary API: a sale is inferred when a listing leaves a dealer website, and every price is the advertised asking price at exit, never a negotiated transaction price. Use when a dealership group or its inventory director asks whether the group sells the mix its market wants, which volume models it is under-weight in (the conquest gaps), which models it over-indexes on and how they turn, or how to allocate between rooftops. Do NOT use for the trims and price points of one model (use the Trim & Spec Stocking Matrix), for the state-by-state footprint (use the Footprint Strength Map), or for the national rank (use the Group Scorecard). The sold data has state grain, not ZIP or radius. Group names must be ones the sold data knows; an unknown name is refused with the closest spellings and nothing is charged. PRICING: $9.99 per run.

Arguments

Argument What it is Example
group Required The dealership group whose mix to compare, as the sold data names it (e.g. AutoNation). Common short forms resolve to the canonical name; an unknown name is refused with the closest spellings. AutoNation
state Recommended A US state as a 2-letter code (e.g. FL) to compare the group with that state's market. Leave blank for the national market. The sold data has state grain only, no ZIP or radius. FL
inventory_type Recommended Which market to compare: used (the default) or new. used
months Optional Whole months to count units over, ending at the latest complete data month: 3 by default, 1 to 12. The medians always describe one month. 3

What comes back

Asking for it in a chat client

Does AutoNation's used model mix match the Florida market?

Where are Sonic Automotive's conquest gaps nationally?

Running it from a backend

Grant an agent the reports:group-vs-market-model-mix scope, then call the tool over MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "generate_group_model_mix",
    "arguments": {
      "group": "AutoNation Inc.",
      "state": "FL",
      "inventory_type": "used",
      "months": 3
    }
  }
}

See Server-side access for the token exchange and how to read the response.