Cardog

The record for every vehicle, decoded, priced and recall-checked.

Advanced API
Screenshot of Cardog, The record for every vehicle, decoded, priced and recall-checked

What is Cardog?

Cardog turns a VIN into a sourced vehicle record: decoded build, live market pricing and model year recalls, delivered through a REST API, SDKs, batch files, an MCP server for agents and embeddable widgets. Built for insurers, lenders, fleets, dealers and government desks.

Cardog is a vehicle data platform built around the VIN. Send seventeen characters and it returns the build of a specific car (year, make, model, trim, body, drive, engine and assembly plant), a market quote drawn from live listings, and the recall campaigns listed for that model year. Each field carries its source and the day it was read, and when no source covers a field the record says so rather than filling the gap with a guess. That transparency is the product's central design choice, and it shapes how the output reads in practice. The platform ships as seven products under one API key: identity (VIN decoding), market (median and middle half asking prices from listings seen in the last 30 days), recalls (Transport Canada and NHTSA campaigns joined to model years), files (batch VIN lists returned as filled rows), battery (state of health and cell group voltages read at the diagnostic port), an MCP server for agent tool calls, and embeddable widgets for dealer sites and vehicle pages. The demo scenarios show how the data lands on real screens: an insurance quote form, a registration counter, a loan collateral step, a fleet roster, a dealer trade desk and a manufacturer's trim breakdown. The tool is aimed at organisations that handle cars at scale rather than at individual shoppers. Insurance, government registries and customs, lending, fleet, dealer, and manufacturer desks each get a documented workflow. Developers reach it through REST with TypeScript and Python SDKs, spreadsheets can be uploaded as files and feeds, and agents call it over MCP. Among alternatives it sits closer to a data infrastructure layer than to a consumer car shopping app; the comparison is with building a VIN pipeline in house or stitching together separate decode, pricing and recall vendors.

How do you use Cardog?

  1. 1Create an API account and get a key
    Open the account page to register and retrieve the x-api-key value that authenticates every call to the Cardog API.
    Cardog — Create an API account and get a key
  2. 2Decode a VIN
    Request a single VIN to get the build back, including year, make, model, trim, body, drive, engine and plant, with a source marked on each field.
    Cardog — Decode a VIN
  3. 3Follow the response links for price and recalls
    The decode response hands back quote and recalls links. Call the quote link for median and middle half asking prices, and the recalls link for campaigns listed for the model year.
  4. 4Batch a spreadsheet of VINs
    Upload a CSV or use the feeds route to return filled rows in the same order as sent, with each column completed from its VIN.
    Cardog — Batch a spreadsheet of VINs
  5. 5Connect an agent over MCP
    Point an MCP capable assistant at the Cardog server so it can call identify_vehicle, market_quote and check_recalls and cite the source behind each answer.
    Cardog — Connect an agent over MCP
  6. 6Try a VIN lookup on the public page
    The VIN page offers a quick way to see what a decode returns before wiring anything into your own systems.

Pros and cons

Pros

  • Every field carries its source and read date, and missing data is flagged rather than guessedAI
  • Market quotes show the median plus the middle half and live listing count, so the spread is visibleAI
  • One key covers seven products: identity, market, recalls, files, battery, agents and embedsAI
  • REST API with TypeScript and Python SDKs, plus batch files and an MCP server for agent workflowsAI
  • Recall campaigns are tied to model years, with the maker's VIN lookup left to confirm the specific vehicleAI

Cons

  • Recall output is listed for the model year, not confirmed per VIN, so a second check is still requiredAI
  • Pricing is not published on the homepage; cost has to be established through the demo bookingAI
  • Recall coverage centres on Transport Canada and NHTSA, which limits usefulness outside North AmericaAI
  • No self-serve widget builder or counter app is demonstrated without going through the API accountAI
  • Battery reads depend on access to the diagnostic port, which is not possible for remote or offsite vehiclesAI

How much does Cardog cost?

Support

Documentation and an API reference are published, and a demo booking link is available on the homepage for a direct walkthrough.

Learn more

Integrations

Offers a REST API with TypeScript and Python SDKs, CSV and feed uploads for batch work, an MCP server for agent assistants, and embeds for dealer websites and vehicle pages.

Learn more

Features

Seven products on one key: VIN identity with per field sourcing, market quotes (median, middle half, live count, as of date), Transport Canada and NHTSA recalls joined to model years, batch file fills, battery state of health with cell group voltages, an MCP server for agents, and embeddable listing cards and vehicle pages. Access runs through REST with TypeScript and Python SDKs.

Learn more

Frequently asked questions about Cardog

  • Does Cardog have an API?
    Yes, Cardog offers an API.
  • How do you use Cardog?
    The walkthrough on this page covers 6 steps: 1. Create an API account and get a key 2. Decode a VIN 3. Follow the response links for price and recalls 4. Batch a spreadsheet of VINs 5. Connect an agent over MCP 6. Try a VIN lookup on the public page.
  • What platforms does Cardog support?
    Cardog is available on Web App.
  • What does Cardog integrate with?
    Offers a REST API with TypeScript and Python SDKs, CSV and feed uploads for batch work, an MCP server for agent assistants, and embeds for dealer websites and vehicle pages.
  • What are the limitations of Cardog?
    Recall output is listed for the model year, not confirmed per VIN, so a second check is still required. Pricing is not published on the homepage; cost has to be established through the demo booking. Recall coverage centres on Transport Canada and NHTSA, which limits usefulness outside North America.

Status

StatusActive
Views0
Outbound clicks0
Added10/22/2026

Platforms

Web App

Pricing

Paid