Question 1

What is on this dealer's lot?

Accepted Answer

the whole market for a cent, before any per-unit call pull the inventory for <dealer id> from cars.com on monid. the id is a uuid you only get from a $0.03 search first, the response carries no total and no page count so paging runs until a page comes back empty and each empty page still bills, and new and used stock are mixed with no filter, so split them yourself before saying what the lot leans toward the lot: 29 vehicles in one call, from $20,914 to $57,968 the mix: five brands, new and used stock side by side on the same lot there is no end signal: the response has no total and no page count, so paging is blind: on a second dealer pages twenty and fifty each came back empty and each billed a cent new and used are mixed: that dealer's 144 rows were 62 new against 82 used with no stock-type filter available, so the weighting question is answered wrong unless you separate them first the gap: the response carries a dealer id but no dealer name, so you know the lot, not the sign why first: a cent buys a rival's whole stock list, which is the cheapest competitive read in the aisle

Question 2

Is this used car priced fairly?

Accepted Answer

comps by hand, and what one word on the report is worth search carfax on monid for a within 50 miles of and give me price, mileage, trim, dealer and the accident summary for each. check the year on every row yourself: this provider's year filter leaks badly, about a third of the rows survived it on both markets we tried. take the service-record count from the number inside the service-history object, not from the similarly named field next to it, which is a boolean what one row holds: price, mileage, trim, dealer, distance, owner count, accident summary, service-record count and the fees, so 25 cars cost $0.0004 each to shortlist the filter leaks: a search pinned to one model year reported 115 results of which 42 were that year, and pages three and four held none of it; on a second market 12 of 38 rows were the year asked for and the last page held none either but it is this provider, not the aisle: the second source's year filter was clean on a second market, 17 rows of 17 on-year, so do not tell a reader every retail search leaks and the dishonest count is the other one: this provider's total was accurate on the second market, 38 reported and 38 reachable, while the second source returned 17 rows while reporting a total of 8 one field name is a trap: the service-record COUNT lives inside the service-history object; the field named for service records next to it is a boolean, so a reader who reaches for the obvious name gets true rather than a number the ZIP that was ignored: another provider accepted the ZIP, returned 21 cars from seven other states, computed the distances from somewhere else, and billed a 200 for it coverage is the real difference: 115 rows against 30 against 21 for the same search, and the subject car existed in only one of the three

Cars.com

Try it with your agents

How-to guides

Cars.com

Try it with your agents

How-to guides

Related categories