Buying a used car is one of the biggest checks most people write without a second opinion. The seller knows more than you do. The listing is written to sell. And the two databases that would actually tell you the truth about the car sitting in the driveway are public, free, and completely unreadable to a normal human being.
This is a story about closing that gap with one sentence: "Here's the VIN." No mocked screens, no toy data. Every specification and recall campaign below is a real lookup against live U.S. government records, captured from an actual chat.
The problem with buying used
Marcus is a first-time EV buyer. He found a 2018 Tesla Model 3 on a marketplace, priced a little under the others, and he has exactly one advantage the seller doesn't expect him to use: the seller texted him the VIN.
A VIN is the car's fingerprint. Two U.S. government databases can turn those seventeen characters into the truth about the vehicle:
- The NHTSA vPIC database decodes the VIN into the real make, model, year, trim, drivetrain and factory-installed safety equipment. It settles what the car actually is, regardless of what the listing claims.
- The NHTSA recalls database lists every open safety recall for that make, model and year, including the ones that never got fixed.
Both are free. Both are also built for engineers and insurers, not for a nervous buyer standing in someone's driveway on a Saturday. The data exists; the plain-English answer doesn't.
So instead of learning to read government JSON, Marcus did the thing anyone with a Claude account can do in twenty minutes: he wired both databases into Claude as tools using the official Apify MCP server, and then just talked to it like a knowledgeable friend.
The first tool he connected:
- The NHTSA VIN Decoder & Vehicle Specs Scraper turns a VIN into the full factory spec sheet.
- The NHTSA Recalls Scraper returns every recall campaign on record for a given make, model and year, with the safety consequence and the fix.
Two public databases, one chat window. Nothing to install on the car, no subscription, no salesperson. Marcus opens Claude and types the way he'd text a friend who happens to know cars.
"What is it, in plain English?"
He starts with the only fact he has. He pastes the VIN and asks what the car actually is.
The agent doesn't lecture. It runs the decode, then translates seventeen characters into a picture a human can hold: a 2018 Tesla Model 3, a single-motor Standard Range electric sedan, built in Fremont, California, that stickered around $46,000 new. It reads back the safety equipment that came standard on the car (automatic emergency braking, blind-spot monitoring, lane-keep assist, a backup camera, stability control) and notes, plainly, that this is a strong set for the model year.
Then it does the thing a good second opinion does: it flags something small but real. The VIN's built-in check digit doesn't validate cleanly. The agent doesn't dress it up as fraud. It explains that this is common for early-production and sample VINs, and gives Marcus one concrete action: confirm the VIN on the door-jamb sticker and the title exactly matches the one the seller texted. That is the difference between a data dump and advice.
Every field in that answer came from a real Actor run (2AbJcEVY9gWPpHAeD), not from the model's memory of what a Model 3 usually is. If the seller had quietly listed a base car as a Long Range, or fudged the year, the decode would have contradicted the listing on the spot.
Marcus didn't have to know that the vPIC database exists, or what "electrification level" means. He asked a question in English and got an answer in English. But identity is only half of a safe purchase. The agent knows that, and offers the second half itself: want me to check whether this car has any open safety recalls?
"Are there recalls, and what do I say to the seller?"
This is the question that actually protects Marcus's money and, more to the point, his safety. He says yes, and asks the thing every buyer is too polite or too unsure to ask: what does he actually say to the seller?
The agent runs the recalls lookup (7YfhB7mRkYSTgqQ4x) and comes back with a number that would scare anyone off cold: 18 recall campaigns on record. And here is where the agent stops being a search box and starts being a second opinion. It doesn't dump eighteen scary paragraphs. It reasons about the data on Marcus's behalf and sorts it into what matters and what doesn't:
- 14 of the 18 were fixed over the air: software updates the car downloads on its own. If the car has been online, they're already done. Nothing to chase.
- 4 need a physical shop repair. These do not fix themselves, and these are the only ones Marcus has to care about.
Then it names the four in plain terms, leading with the scary one: a front suspension recall (campaign 23V235000) where a lateral link fastener can loosen and let the suspension separate from the frame. It is safety-critical, and specific to 2018-2019 Model 3s. Plus a front seat-belt fastener recall (21V389000), a rear seat-belt anchor recall (22V798000), and a rearview camera cable recall (21V00D000). All four repaired free at any Tesla service center.
And then the payoff, the part no database gives you. The agent writes the exact message to send the seller:
"Hi, before I come see the car, can you send me the service records showing recalls 23V235000 (front suspension) and 21V389000 (front seat belt) were completed? If you're not sure, I can look up the VIN's recall status together, or we can swing by a Tesla service center. Just want to make sure the safety recalls are closed out."
That is the whole product. A used-car buyer with no mechanical knowledge now has a specific, polite, informed ask (with campaign numbers in it) that turns "I guess it's fine" into leverage. As the agent points out: if the seller can't prove those two repairs were done, that's not a dealbreaker, it's a discount. The fixes are free. What Marcus can't afford is to drive off not knowing.
The cheat sheet in his pocket
Before he leaves for the viewing, Marcus asks for one thing he can keep on his phone.
The agent consolidates both lookups into a single dossier: what it checked, what the official record says, and what Marcus should do about each line. Identity confirmed. Safety features solid for the year. Fourteen recalls already handled by software. Four that need proof of repair. One VIN check-digit to verify against the door jamb. Two databases, one glance, every row traceable to a real government record rather than anyone's opinion.
The bottom line the agent gives him is the one a trusted friend would: the car is what the seller says it is, the safety kit is good, and the only real homework is the suspension and seat-belt recalls. Do that, and he's buying with his eyes open.
Why this matters beyond one buyer
Marcus is the obvious audience, but he's not the only one. The interesting reader here is the marketplace or insurer who could embed this exact agent.
- A used-car marketplace could put a "paste the VIN" box on every listing and hand every buyer this second opinion automatically, closing the information gap that makes people distrust private-party sales in the first place.
- An insurer or a warranty provider could screen a VIN for open safety recalls at quote time, in plain language, without building a data pipeline against two government sources.
- A neighborhood mechanic could run it on a customer's behalf and print the dossier.
The point of the experiment isn't that the data was hard to get. It's public. It's that the judgment layer on top of the data used to require a human who knew cars, knew which recalls fix themselves, and knew what to say to a seller. That layer is now a conversation.
Build the same agent
Everything above is reproducible today with a free Apify account and any MCP-capable client (Claude Desktop, Cursor, or your own app):
- Get your Apify API token from the Apify Console under Settings → Integrations.
- Add the official Apify MCP server to your client and list both Actors in the
toolsparameter:
{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=scrapers_lat/nhtsa-vin-decoder-scraper,scrapers_lat/nhtsa-recalls-scraper",
"headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
}
}
}
- Restart the client, paste a VIN, and ask it, in plain English, to decode the car and check for recalls. It will pick the right tool for each step and reason across both.
📌 Note: each tool call is a real Actor run billed to your Apify account (both are pay-per-result, a fraction of a cent per lookup). To offer this at scale on a marketplace, call the Actors through the Apify API behind your own "paste the VIN" box instead of one call per chat.
🏹 Extend it: the same pattern grows into a full pre-purchase agent. Add a used-car listings source to compare the asking price against the market, or a title and odometer source, and the agent goes from "what is this car" to "should you buy this car, at this price", all over live data, by adding one more Actor to the tools list, with no new code.
The Actors used in this story: NHTSA VIN Decoder & Vehicle Specs Scraper and NHTSA Recalls Scraper.
Top comments (0)