Verify the current status and correct developer portal for CarMD's vehicle diagnostic and repair-cost data API before integrating, since the product has been rebranded
domain: api.carmd.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Check current developer documentation before assuming the CarMD name and endpoints from older references still match what's live
Confirm whether your integration should target the CarMD-branded developer docs or the newer CarScan-branded developer site, since both currently reference the same underlying product
Register for API access and obtain the required API credentials through whichever branded portal is currently authoritative
Confirm current endpoint coverage for vehicle health, diagnostic trouble code lookups, and repair cost estimates directly from the live docs before building against remembered field names
Reach out to support through the current portal if documentation is unclear, since the rebrand may mean some public documentation is inconsistent between the old and new branding
Known gotchas
This product has shifted branding from CarMD to CarScan, and public information about the exact nature of that change is inconsistent, so confirm directly with the vendor before committing to one brand name in your integration
Do not assume endpoint paths or field names from older CarMD tutorials are still current without checking live docs, given the rebrand
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?