Decode a VIN and pull a vehicle history report through the CarsXE API for a used-car marketplace listing
domain: carsxe.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate by passing your API key as the 'key' parameter (query/body param, not a bearer header) on each request
Call the /specs endpoint for a standard VIN decode (year/make/model/trim/engine)
Call the separate History endpoint for a vehicle history report — this is a distinct product from /specs, not a field within it
If market pricing is needed, call the separate Market Value (v2) endpoint rather than expecting valuation data from the specs or history responses
Handle each product's response shape independently since CarsXE exposes specs, market value, and history as architecturally separate endpoints
Known gotchas
CarsXE authenticates via a plain 'key' parameter rather than an Authorization header — a client built assuming bearer-token auth will get rejected
Specs, Market Value, and History are billed and structured as separate endpoints/products — budgeting for one call per vehicle will undercount API usage if more than a basic decode is needed
CarsXE is also resold as a licensed third-party plate-decoder inside at least one other aggregator's platform (MarketCheck) — check for indirect access before adding a separate subscription
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?