# Auto.dev blog

> Guides, product updates and answers about vehicle data, VINs and building with Auto.dev.

- [How to Decode a List of VINs in Google Sheets](https://www.auto.dev/blog/decode-vins-in-google-sheets.md) (2026-10-21): Paste a short Apps Script into your sheet, save your Auto.dev API key as a script property, and type =VIN(A2) to get the year, make, model and trim. For long lists, use the Auto.dev menu instead: it paces itself, writes plain values and picks up where it stopped. Each VIN is one API call.
- [NHTSA's VIN Decoder (vPIC): What It Returns and Where It Stops](https://www.auto.dev/blog/nhtsa-vin-decoder-vpic.md) (2026-10-21): vPIC is NHTSA's public VIN decoder. It needs no key, costs nothing, and is built from the VIN filings carmakers submit to NHTSA, so it's good at what a VIN encodes: year, make, model, body, engine and often the trim. It can't tell you a specific car's options, paint or option prices, because a VIN doesn't contain them. Those come from the manufacturer's build data.
- [How to Research a Used Car With Claude](https://www.auto.dev/blog/research-a-used-car-with-claude.md) (2026-10-21): On its own, Claude answers car questions from its training data. It can't see what's listed near you today or read a specific car's factory options. Add the Auto.dev connector in Claude Desktop (Settings, Connectors, Add Custom Connector, https://mcp.auto.dev/mcp) and it can search live dealer listings, decode VINs, check recalls and pull a car's build data, then turn the results into a spreadsheet or a sale listing. No code or API key needed.
- [Automotive Data for AI Agents](https://www.auto.dev/blog/automotive-data-for-ai-agents.md) (2026-04-04): Auto.dev connects to AI agents four ways: a hosted MCP server at mcp.auto.dev with OAuth sign-in and nothing to install, the auto CLI and a local MCP server from @auto.dev/sdk, a JavaScript/TypeScript SDK, and an agent skill for agents without MCP. Agents can then search listings, decode VINs, calculate payments and check recalls from plain-English requests, limited to what your plan includes.
- [Clickable Links: Exploring Auto.dev APIs In The Browser](https://www.auto.dev/blog/clickable-links.md) (2025-09-16): Raw Auto.dev API responses embed clickable, hypermedia-style links, so once you're signed in you can explore the API in your browser without hunting for routes. Start with a VIN Decode call, follow the discover object to related endpoints, use the actions object to learn query parameters, and open the embedded docs links for depth.
- [What is a Squish VIN?](https://www.auto.dev/blog/what-is-a-squish-vin.md) (2025-09-15): A Squish VIN is a 10-character version of the 17-character VIN: positions 1–8 and 10–11, without the check digit and the serial number. It identifies a VIN pattern (the model, body, engine, model year and plant) rather than one vehicle, which makes it a useful key for specs and for finding comparable cars. Auto.dev returns it with every VIN decode, and the Listings API filters by it with vehicle.squishVin.
- [What is a Vehicle Identification Number?](https://www.auto.dev/blog/what-is-a-vin.md) (2025-09-15): A VIN (Vehicle Identification Number) is a unique 17-character code that identifies a specific vehicle and stays constant for its entire life. It encodes the manufacturer, model, engine, model year, and assembly plant, and appears on the dashboard, driver's-side door jamb, and title. Auto.dev's VIN Decode API turns a VIN into its year, make, model, trim, engine and origin, and the Specifications and OEM Build Data APIs add specs, pricing and factory options.
