Footprint Strength Map
Where a dealership group is strong and thin, state by state, new against used, with each state's price and turn beside its market.
This is the technical reference. For the price, a rendered sample and answers to common questions, see the Footprint Strength Map product page.
At a glance
| Price | $9.99 per run. |
| Tool name | generate_footprint_strength_map |
| Scope | reports:footprint-strength-map |
| Built for | Dealer Group |
What it does
The footprint map for one dealership group from Sold Summary API v2 at state grain over a window of whole months (3 by default, up to 12): every state where the group's rooftops recorded sales, ranked by units, with new and used units summed over the window, the group's share of the state's new, used and total dealer-website sales over the same months, and the used-per-new ratio of the group against the state's market; a second table sets the group's median asking price at exit and median days to sell in each state against the state's whole market, used and new. Four reads are written from the numbers: the strongest states by share, the thinnest and the toeholds under 30 units, where the new-and-used mix differs most from the state's, and the invest-or-divest input (the large markets where the group's share trails its footprint median, and the toeholds to review). 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, the state's from that same month. From the Sold Summary API: a sale is inferred when a listing leaves a dealer website, every price is the advertised asking price at exit (never a negotiated transaction price), and a state share is a share of the state's dealer-website sales, not of registrations. Use when a dealership group asks which states carry its volume, where its share is strong or thin, how its new-and-used mix compares with each state's, or where to put or pull marketing and inventory dollars. Do NOT use for the national rank against named rivals (use the Group Scorecard) or for the model mix inside one state (use Group vs Market Model Mix). 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 to map, as the sold data names it (e.g. Lithia Motors). Common short forms resolve to the canonical name; an unknown name is refused with the closest spellings. | Lithia Motors |
months |
Recommended | Whole months to count units over, ending at the latest complete data month: 3 by default, 1 to 12. Shares are over the same months; medians always describe one month. | 3 |
What comes back
- Footprint by state: every state where the group's rooftops recorded sales, ranked by units, with new and used units and the group's share of the state's new, used and total sales over the same months, and the used-per-new ratio against the state's
- Price and turn by state: the group's median asking price at exit and median days to sell against the state's whole market, used and new
- Strength read: the strongest states by share, the thinnest and the toeholds under 30 units, where the new-and-used mix differs most from the state's, and the invest-or-divest input
- Key metrics: states, units, new and used units, the strongest state by share, the largest by units and the median state share
- A CSV of every state in both tables
- Next steps: Group vs Market Model Mix for one state, the Group Scorecard for the national rank, a monthly monitor
Asking for it in a chat client
Map Lithia's footprint strength by state
Where is Group 1 Automotive strongest and weakest?
Running it from a backend
Grant an agent the reports:footprint-strength-map scope, then call the tool over MCP:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "generate_footprint_strength_map",
"arguments": {
"group": "Lithia Motors Inc.",
"months": 3
}
}
}
See Server-side access for the token exchange and how to read the response.