OEM-level protocols catch the Transmission & Radar codes generic scanners miss.
The CarDr Difference
A generic scanner hands you a list of codes and stops. Mechanical Intelligence is what happens next — CarDr translates every code into what it means and what to do about it.
"Most scanners tell you what code was found. CarDr tells you what that code means to the transaction."
— Greg Lubrani, CEO & President, CarDr138 OEM protocols, 50+ ECUs, a full read in 15 seconds — the deepest data capture in the category, not a partial one.
Every DTC gets a criticality score, a commonality rating, and a plain-English impact statement — not just a five-character code.
Each report ends in a recommended workflow — hold for review, verify root cause, check disclosure — so the read becomes a decision.
P0420. That's it. No sense of urgency, no cost, no next step — just a string of characters and a technician's best guess at what happens next.
P0420 → High criticality, common fault, $850–$2,200 repair range, recommend mechanical review before release. The same code, turned into a call someone can actually make.
Real pilot results, not projections — from an auction partner who scanned every vehicle with CarDr before sale.
"Cutting our arbitration exposure roughly in half while moving vehicles through the lane faster than before — that's the kind of result that changes how we think about pre-sale inspection."
— General Manager, wholesale auto auction pilot partnerA full engine diagnostic scan — active DTCs, repair cost bands, code-reset history, and open NHTSA recalls, all in one report. This is the moment prospects go from "interesting" to "when can we start."
Whoever is on the hook when a vehicle turns out to be worse than it looked, CarDr gives them the read before the decision, not after.
Score every DTC individually instead of flagging on a single repair threshold — a full risk picture in the lane, not a single red flag.
See patterned component failures and code-reset history before you bid, so the vehicle you buy is the vehicle you priced.
OEM-level protocol coverage catches the B, C, and U codes that generic scanners miss — the ones that quietly erode claim margin.
A 15-second scan across the full protocol stack fits inline with intake, inspection, or remarketing workflows without slowing them down.
Pair ULTRA's scan data with your existing inspection checklist and dispatch flow — one more layer of certainty, no new hardware learning curve.
Full SDKs and APIs let you trigger a scan and publish CarDr diagnostic data directly inside your own native app.
Static OBD readers check what they're told to check. ULTRA adapts to the vehicle in front of it, in real time — reading more ECUs, more protocols, and more codes than a generic scanner in a fraction of the time.
See the Full Comparison
CarDr correlates ULTRA's diagnostic read with repair-cost bands, patterned component failure data, vehicle history, and current market values — so the appraisal reflects the vehicle's real condition, not just its odometer.
Full SDKs trigger the ULTRA device directly from your native app. Full APIs publish diagnostic data straight back into it. White-label hardware available.
Explore the SDKWhether you're building a car-diagnostic feature into an existing platform or dispatching inspectors with GPS-tracked assignments, CarDr's hardware and software plug into what you've already built.
Most software vendors ask you to adapt to their platform. CarDr adapts to you — in one month, we delivered 13 customer-requested enhancements. And some were designed, developed, tested, and deployed in under 24 hours.
"One of the core principles of CarDr is that we listen. When our customers tell us something can be improved, we don't wait — we get to work immediately." — Greg Lubrani, CEO