The morning an AI agent caught a Takata airbag before the car hit the lot

This is a story about a used-car dealership that stopped losing an hour a day to browser tabs, because someone spent twenty minutes wiring two Apify Actors into Claude the week before. No mocked screens, no toy VINs. Every decoded spec and recall campaign below is a real lookup against a live source, captured from an actual chat.

The setup

Rosa runs inventory at a mid-size used-car dealer. Every vehicle that comes in the door (auction buys, trade-ins, wholesale lots) has to clear two checks before it can be photographed, priced, and put on the lot:

1. Is this actually the car the paperwork says it is? A title that reads "2003 Honda Accord" tells you almost nothing. Is it the four-cylinder sedan or the V6 coupe? Was the VIN re-stamped or transposed? The make on the door jamb is not proof of the make, the model, or the year.
2. Does it have an open safety recall? Retailing a used car with an unremedied recall is a liability the moment something goes wrong, and in several states it is a disclosure problem too. The Takata airbag recalls alone still cover millions of older cars sitting on lots and in auction lanes.

For years this meant Rosa kept two browser tabs open. One on a VIN decoder, one on the NHTSA recall lookup. For every car she typed the VIN, read the spec sheet, copied the make and model into the recall page, and read the campaign list. A ten-car auction run was most of a morning. The check was only as reliable as her patience on a busy day, and intake is always a busy day.

So the week before this story, she did something different. She wired both data sources directly into Claude as tools, using the official Apify MCP server, and let the model do the fetching. Setup was one config file and a restart.

The two tools she connected:

• The NHTSA VIN Decoder & Vehicle Specs Scraper turns any VIN into the full spec sheet: make, model, year, trim, body class, engine, cylinders, horsepower, fuel type, and assembly plant, with a check-digit validation on the VIN itself.
• The NHTSA Recalls Scraper returns every safety recall campaign for a make, model, and year: campaign number, affected component, the official summary, the remedy, and the date the recall began.

Both exposed to Claude through one MCP endpoint. Nothing else changed about how Rosa works: she still opens a chat and types in plain English.

The first car

Monday morning, four vehicles came off the weekend auction run. Rosa started with the one whose title told her the least (a plain "2003 Honda Accord") and asked Claude to decode the VIN before she wrote a word of the listing.

One tool call, and the car had an identity. The VIN decoded clean. The check digit in the ninth position was correct, which is the first guard against a re-stamped or transposed number. And it was not a generic Accord. It was a 2003 Honda Accord EX-V6 Coupe: a two-door body, a 3.0-liter V6 (engine model J30A4), 240 horsepower, five-speed automatic, built in Marysville, Ohio. That is a different listing and a different price band than the four-cylinder sedan someone might have assumed from the title.

This is the quiet part that matters. A make on a title is not a car. The decode caught the real trim and drivetrain in two seconds, and it did it the same way for every VIN, whether it was car one or car forty.

The catch

Then the check that actually stops cars from being sold. Rosa asked Claude to pull open safety recalls for that same Accord before it went anywhere near the lot.

The answer put the car on hold.

The 2003 Accord is covered by multiple recall campaigns, and the ones that matter are the Takata airbag inflators. Claude surfaced them with campaign numbers, components, and remedies attached:

• 19V182000: driver frontal airbag inflator. Remedy: a dealer replaces the driver airbag inflator, free of charge. The recall began April 10, 2019, and covers roughly 1.1 million vehicles.
• 19V501000: passenger frontal airbag inflator. Remedy: a dealer replaces the passenger inflator, free of charge. Began August 12, 2019, roughly 1.66 million vehicles.
• 10V364000: ignition switch interlock lever wear. Remedy: a dealer replaces the interlock pin and lever, free of charge.

Takata inflators can rupture and fire metal fragments at the people in the car; they are the defect behind multiple U.S. fatalities. Selling a used vehicle with that recall still open is exactly the exposure Rosa's manager wants avoided. Claude's recommendation was the right one: route the Accord to a Honda dealer for the free inflator replacement, get the campaigns closed, and only then list it. Nobody had to remember to run this as a separate ritual. It was one sentence in the same conversation, backed by the live recall list rather than anyone's memory of which years Takata covered.

The batch

The last step is the one that used to eat the most time: doing the same thing for the rest of the run and writing it up. Rosa asked Claude to consolidate all four inbound vehicles into a single lot / hold table she could paste straight into the intake sheet.

Four cars, four decisions, each traceable to a campaign number or a run ID:

• 2003 Honda Accord EX-V6: Takata airbag (19V182000, 19V501000) and ignition switch (10V364000). No, hold off lot until the airbag remedy is confirmed.
• 2013 Ford F-150: brake master cylinder (16V345000) and transmission control module (19V075000). Hold and book the service; the brake recall is a physical repair.
• 2018 Tesla Model 3: seat-belt fastener (21V389000) and front suspension link (23V235000), plus software recalls that apply over the air. Hold and verify the two physical items at a service center.
• 2003 Toyota Sienna: a structure recall (10V160000). Hold and verify the remedy.

The headline was uncomfortable and completely real: not one of the four inbound cars was clean. Every vehicle carried at least one open safety recall. On a busy morning, with the old two-tab process, at least one of those (probably the Accord's airbag) had a real chance of being missed.

What actually changed

Nothing about Rosa's judgment moved to the machine. She still decides what to list, what to send for service, and what to send back. What moved was the mechanical part: the tab-switching, the copy-paste between a VIN decoder and a recall page, the risk of skipping a check when the lane is full. That is the right division of labor:

• The fetch is automated. Claude decodes the VIN and pulls the recall campaigns on its own, the moment the conversation needs them.
• The evidence is preserved. Every line cites a campaign number or a run ID, so the intake sheet is audit-ready by default, useful the day a buyer, an insurer, or a regulator asks how the car was cleared.
• The check is consistent. The agent runs the same decode-and-recall screen on every car, at 9am or 6pm, whether it is the first of the day or the fortieth.

The dissolved-shell equivalent here (a life-threatening airbag on a twenty-year-old coupe) was caught before the car ever reached a customer.

Build the same agent

Everything in this story is reproducible today with a free Apify account and any MCP-capable client (Claude Desktop, Cursor, or your own agent):

1. Get your Apify API token from the Apify Console under Settings → Integrations.
2. Add the official Apify MCP server to your client and list the two Actors in the tools parameter:

{
  "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" }
    }
  }
}

1. Restart the client and ask it, in plain English, to decode a VIN and check the car for open recalls. It will pick the right tool for each step.

📌 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). For continuous screening of a full lot or a fleet, run the Actors on a schedule through the Apify API and feed a whole VIN list at once instead of one call per chat.

🏹 Extend it: the same pattern scales past intake. A marketplace can screen every new listing at upload; a fleet operator can re-run the recall check monthly against its VIN list; an insurer can flag open safety recalls at quote or renewal. Point the agent at a VIN list and it decodes and screens the whole book without a line of new code.

The Actors used in this story: NHTSA VIN Decoder & Vehicle Specs Scraper and NHTSA Recalls Scraper.