Docs

Cardog API

VIN identity, specs, listings, market data and recalls for Canadian vehicles, behind one key.

Last updated:

Reading as an agent? The whole platform is one file: docs.md.

Line drawing of a generic compact crossover in three-quarter view, charging-port door open.
  1. 1The VINSeventeen characters on the dash, read through the glass.
  2. 2The buildMake, model, trim, engine and body, decoded from the VIN.
  3. 3ChargingStations near a point, filtered by connector and power.
  4. 4RecallsCampaigns listed for its model year, per authority.
  5. 5Its priceWhat this configuration sells for, from live listings.
  6. 6Its partsManufacturer part numbers on record, linked to the maker's store.

Get started

Make your first callGet a key, save it, decode a VIN. Three steps.Connect an agentGive Claude, Cursor or any MCP client the Cardog tools.

Products

Vehicle identityDecode a VIN to its exact build, spec sheet and window sticker, and keep your own rows current with a feed.Market dataLive listings, instruments, quotes and daily bars by ref.Recalls & safetyTransport Canada and NHTSA recalls for a VIN or a model, and crash ratings matched to the build.LocationsPlaces a driver goes: fuel stations with today's pump prices, chargers and dealers, one ref per place.

Tools

API referenceEvery v2 route, generated from the contract.SDKs & MCPThe TypeScript and Python clients, the MCP server, and the markdown twins of every page.Build guidesSample apps built end to end on the API.

More

ChangelogWhat changed in the API, by date.Legacy v1The v1 API, kept for existing integrations.

Was this helpful?