The record for every vehicle on the road.

Decode the VIN, price the vehicle against the live market, and check every recall that applies.

Five fine lines run in from the left, pass under a crossover and split into a VIN plate, a price histogram and a recall sheet.

For developers

From the first call to production

REST, with TypeScript and Python SDKs. Send a VIN and follow the links the response hands back.

shell

curl https://api.cardog.app/v2/vin/1C4RJHDG0P8708786 \  -H "x-api-key: $CARDOG_API_KEY"# then follow links.quote and links.recalls

A real read of a public listing's VIN, trimmed to the vehicle, its market and its first campaign.

200 · 2023 Jeep Grand Cherokee Overland

// GET /v2/vin/1C4RJHDG0P8708786{  "vin": "1C4RJHDG0P8708786",  "valid": true,  "year": 2023,  "make": "Jeep",  "model": "Grand Cherokee",  "trim": "Overland",  "refs": {    "modelYear": "model-year:jeep/grand-cherokee/2023"  },  "links": {    "quote": "/v2/quotes/model-year%3Ajeep%2Fgrand-cherokee%2F2023",    "recalls": "/v2/vin/1C4RJHDG0P8708786/recalls"  }}// GET links.quote{  "priceMedian": 42988,  "priceP25": 35999,  "priceP75": 47995,  "liveCount": 249,  "asOf": "2026-11-19"}// GET links.recalls  (listed for the model year){  "recalls": [    {      "authority": "tc",      "campaignNumber": "2026418",      "component": "Suspension",      "recallDate": "2026-09-01"    },    …  ]}

Ways in

One record, however you work

One VIN reads identically in code, a spreadsheet, an agent or a web page.

One VIN plate in the centre, four lines out to a terminal, a spreadsheet, a chat bubble and a browser window.
  • API and SDKs

    For engineers wiring it into their own systems.

  • Files and feeds

    For desks that run on spreadsheets and batches.

  • MCP for agents

    For assistants that need a source they can cite.

  • Web app and embeds

    For people at a counter, and the sites they run.