Every used car on CarGurus, with CarGurus's own verdict on its price

They are CarGurus's own analysis of each car. imv_price is CarGurus's instant market value, the price it estimates for that car; deal_rating says how the asking price compares: great, good, fair, high, overpriced, or no_analysis and uncertain when CarGurus does not rate the car. deal_rating_code keeps CarGurus's own code and deal_score its score. Both are on every search row and in listing. All 179 rows of an eight-search sample across the three sites carried an IMV and a deal rating.

CarGurus places every search around a location, and its distances and result counts depend on it: 10001 gives about 81,000 cars within 50 miles, 90210 about 64,000. Without a location the site would choose one for you, so the API asks for zip (a US ZIP, a Canadian postal code such as M5V 3L9, or a UK postcode such as SW1A 1AA). A code CarGurus cannot place is refused instead of returning a search around somewhere else. Use nationwide=true to search the whole country.

Yes. listing returns price_history, every price change with its date, plus days_on_market and days_at_dealer. Every search row also carries the previous price, the original price, the amount and date of the last price drop. 28 of 179 rows in a mixed sample had a recent drop; price_drops_only=true returns only those (about 10,400 of 81,000 around New York).

site=us reads cargurus.com in US dollars and miles, site=ca reads cargurus.ca in Canadian dollars and kilometres, site=uk reads cargurus.co.uk in pounds and miles. Listing ids and make ids belong to one site, so pass the same site to listing that the search row came from (every row carries it). UK rows also carry ulez_compliant.

About 20 to 23 cars a page. total is CarGurus's own count, but CarGurus stops serving pages before that count runs out: around New York it served 417 pages of an 81,000-car search, and 50 pages of a 1,177-car Ford Explorer search. A page past the end returns no rows with beyond_last_page: true, so a loop can stop there. Narrow the search with filters to reach every car.

Yes, CarGurus places priority and featured listings on every page. They are kept, because they are real cars for sale, and marked with placement and is_sponsored; meta.sponsored_rows counts them. They are placed by CarGurus and do not follow the chosen sort order. Promotional tiles without a car are removed and counted in meta.promo_tiles_dropped.

In a sample of 179 rows from eight searches (SUVs, pickups, electric cars, sedans, cheap cars, convertibles, Canada, UK): price, price with fees, IMV, deal rating, VIN, mileage and dealer name were on every row, days on market on 177, the dealer's phone on 176, features on 176, colour on 175, engine on 169, drivetrain on 168 and combined fuel economy on 147. Distance on a listing is returned only when you pass zip.

No. CarGurus itself quietly ignores filter values it does not know and returns the whole market, so every value is checked first and an unknown one is refused with the list of valid ones. Each filter was checked against an unfiltered search in the same run (around New York: electric 1,626, manual 1,387, great deals 8,545, single owner 47,547). The deal-rating filter uses CarGurus's index, and 2 of about 350 filtered rows carried the neighbouring rating at the moment of reading; the row shows CarGurus's current rating.

CarGurus API is a ReefAPI endpoint group for cargurus used-car listings from the us, canada and the uk as json: the asking price, cargurus's own deal rating and instant market value, days on market, price drops, vin and the dealer behind every car. It returns live JSON through POST requests under /cargurus/v1.

Yes. ReefAPI starts with 1,000 free credits, no card required. CarGurus calls use the same shared credit balance as every other ReefAPI engine.

No login to CarGurus is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.

CarGurus actions currently cost 2 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.

Yes. Connect ReefAPI once through MCP and your assistant can call cargurus actions with the same key, credit pool and JSON envelope used by normal REST requests.