How many of this exact car are for sale right now?

Filter the live corpus to your exact year, make, model, and trim — or to a single VIN — and Listings shows every matching car currently for sale across every venue: dealer, auction, and private seller. Each match carries its price, its location, and a timestamp on the pull, so what you get is a live count of real cars described as they stand at that moment, not a market estimate. The number of available cars is a result of the search, read fresh at the address; it isn't a figure quoted at you.

This is the availability question, and it's different from finding one specific car. Here you already know the configuration you want — a 2023 model in a particular trim and drivetrain — and what you need to know is how thin or deep the market is right now: is there one of these for sale, or forty, and where are they? Depth changes how you shop. One available example means you move fast and accept a longer drive; forty means you can hold out for the right color, the right mileage, the right price, and let the far-away ones go.

How the narrowing works

The facets are the instrument. You start broad — a make and model — and each facet you add tightens the set until it matches the exact car you'd buy:

• year — the model year, not a range you have to eyeball
• make and model — the nameplate
• trim — the specific grade, resolved to what the car actually is rather than what an ad labels it
• drivetrain, body, and the rest — the attributes that separate two cars that share a name

Add enough facets and the set collapses toward a single configuration; add a VIN instead and it collapses to one car. Either way, the count you're left with is the live availability of exactly that spec, not a fuzzy "similar vehicles" bucket that quietly mixes trims and years to look larger. The corpus keeps one spine and one grammar across all three venue types — an auction lot is treated as a listing in an auction venue — so a single filtered view spans dealers, auctions, and private sellers without you querying each separately.

Why it's a live count, not a market statistic

There is a deliberate discipline here, and it's worth being plain about: Listings will not hand you an invented market-size number. It won't tell you "there are typically 500 of these on the market" because that would be a manufactured statistic, and the whole point of the door is that every fact is traceable. What it does instead is show you the actual matching listings it holds right now, each one a real car with a real source and a timestamp, and let the count fall out of that set.

That means the number is honest about two things. First, it's current — the timestamp on each pull tells you how fresh the view is, and a car that sold an hour ago stops being a match rather than lingering as a ghost. Second, it's bounded by coverage, and coverage is stated on the page as a fact with its own source and timestamp. Gaps are named, not hidden. If a venue isn't fully represented, that's disclosed rather than papered over with a rounded-up total. A count you can trace beats a bigger count you can't.

Each matching car also carries the same facts a single listing does: price beside its source, the venue, the verification state, and — where the record supports it — a signed delta against that car's market value rather than an adjective. So the availability view isn't just a tally; it's a shelf you can read across, comparing real asking prices at a glance instead of a headline figure.

Depth against value, and across distance

A raw count is more useful when you read it against two other things: what these cars are worth, and how far away they are.

For worth, each configuration's market value grounds the whole set. values.vin posts five value bands for a VIN — retail, private-party, trade-in, wholesale, and auction — each with its source and the comps behind it. With that spread in hand, a filtered availability view stops being a list of prices and becomes a distribution: you can see which of the available cars sit below retail, which are priced at private-party, and which are outliers, because you have the market bands to measure them against. Depth plus value is what tells you whether to buy now or wait.

For distance, availability is only real if the car can reach you. Each match carries its location, so a count of twenty splits into the few nearby and the many that would need to travel. transport.vin posts a delivery quote from a VIN and two zip codes, which turns a far-away match into a landed cost you can compare directly against a closer, pricier one. A cheaper car three states away isn't cheaper if the freight erases the gap — and the quote tells you before you commit.

What it costs, and where the metering starts

Filtering the corpus and reading the live count is free, with no account, on every visit. The availability view is VIN's own data served at zero marginal cost — that's why the base search leads and stays open. The cost-bearing steps sit downstream and at the machine boundary: deepening any single car into licensed data (a full history, licensed book-value overlays) carries its stated price, and consuming the corpus programmatically by API or MCP is metered per call through apis.vin with the rate card published there. For a dealer taking a resulting lead, the ADF export fee is shown on the export sheet before anything sends. Looking at what's available costs nothing; the meter starts only when you cross into licensed or machine access.

When a match is the one, the deal leaves on rails the same way any single listing does — the listing identifier rides into the close so it starts from the record you were reading, or exports as an ADF lead into a dealer's own CRM.

---

Read the live count against value and distance, then start the deal from the record.

• Value: values.vin — five market bands for the exact VIN, with source and comps
• Ship: transport.vin — a delivery quote from a VIN and two zips
• This door: listings.vin — every car for sale, addressable by VIN