For repair, tire and parts teams
Know exactly which vehicle you are working on
Decode the VIN to the exact build, match a trouble code to its diagnosis, and check open recalls, so the right part, calibration or repair is picked the first time.
- Decode a VIN to the exact build
- Match a trouble code to its diagnosis
- Check recalls the maker still pays for
Pay only for successful API calls · Free sandbox
Scale and reliability
Running in production today
A mobile ADAS calibration company uses this on every repair.
- 99.9%
- API uptime
- 275M+
- Vehicle records
- 500M+
- API calls per month
- 50+
- Countries covered
Platform reliability
Coverage depth
Proven at scale
Plate and VIN lookups
Use cases
Diagnosis, fitment and calibration
Shops, tire and parts counters, ADAS calibrators and the software they run need the same certainty.
Diagnostics
Turn a stored code into the described fault, for cars, trucks, motorcycles and RVs.
Parts and fitment
Decode the VIN to trim, drivetrain and seating so the right part is ordered once.
ADAS and calibration
Calibration teams map sensor configuration per VIN from specifications and images.
Capabilities
Diagnosis and fitment data
Four endpoints cover the code, the exact build, the recall list and the photo.
Trouble code lookup
Over 3,000 codes matched to the trouble or diagnosis they describe.
Exact build decode
Trim, body style, drivetrain and seating for the VIN in front of you.
VIN from a photo
Read the VIN from a dashboard, a door plate or a photo of the paperwork.
Maker-paid recall work
Open recalls the manufacturer remedies at its own cost, not on your ticket.
Enterprise
Groups, franchises and mobile teams
One key across every bay, van and counter, with nothing to install on a terminal.
Every location, one key
Any terminal or tablet that reaches the internet calls the same endpoint.
Key benefit
Adding a location does not add an integration.
Works without a VIN
Year, make and model lookups cover vehicles that arrive with no VIN captured.
Key benefit
An unreadable plate does not stop the job.
Try it on real work
Run a sandbox key against real jobs before committing to a plan.
Key benefit
Nothing is charged for a lookup that finds nothing.
Implementation
How it works
Four steps to a working repair-shop integration, with or without engineers.
- 1
Get a sandbox key
Sign up with a work email. 100 calls, no credit card, no sales call.
- 2
Pick how you connect
REST and JSON, official SDKs, MCP, Snowflake, n8n or Zapier. See integrations.
- 3
Call the endpoints you need
For repair shops, that is OBD Codes Decoder, Specifications and Recalls.
- 4
Map the fields once
Field names are stable and documented, so your shop system maps them once.
Products
Lookups these teams run
OBD Codes Decoder and Specifications carry most of this work.
Security and compliance
Enterprise-grade security
Vehicle data is handled to the standards your compliance team expects.
- SOC 2 Type II
- Certified
- GDPR
- Ready
- ISO 27001
- In progress
- 256-bit SSL
- Encryption
FAQ
Frequently asked questions
Not answered here? Contact us and we'll point you at the right endpoint.
More industries
The same platform, nine industries
CarsXE across the automotive ecosystem
Dealership
Build recall, equity and trade-in tools on licensed vehicle data.
Insurance
Quote, underwrite and settle claims on verified vehicle data.
Rental
Identify, ground and resell rental vehicles from one record.
Finance
Check liens, title and collateral value before you fund a loan.
Warranty services
Screen eligibility and settle warranty claims from one record.
Auto tech startup
Ship vehicle features without building a data pipeline first.
Fleet management
Vehicle records for every VIN in a fleet, without telematics.
Parking and valet
Identify vehicles at gates, valet stands, and parking apps.
Get started
Start building today
Test drive the CarsXE platform. Sign up with your work email and start on the free sandbox. No credit card required.
