The Diagnostic Engine
Behind Your Scanner.
Your scanners pull 300+ proprietary PIDs. Our engine knows exactly what they mean. Don't build a diagnostic R&D team from scratch — pipe your telemetry into our platform.
Sandbox access available · No upfront commitment · Volume pricing on request
How It Works
Four steps from hardware scan to structured diagnosis. Your device does the reading. Our engine does the reasoning.
Partner Device Scans Vehicle
Your hardware reads 300+ proprietary OEM PIDs, module versions, freeze frames, and manufacturer-specific DTCs via CAN FD, DoIP, or J2534.
JSON Payload → Lane Pilot REST API
Your device POSTs the full telemetry payload to our diagnostic endpoint via HTTPS. Standard JSON — no proprietary SDK required.
Lane Pilot Diagnostic Engine
Our proprietary engine cross-references every PID against DTC context, NHTSA recall and complaint records, and confirmed repair outcomes — deterministically.
Structured Diagnosis → Partner UI
A JSON envelope carrying a three-section diagnosis, the vehicle it was resolved against, and per-request metering is typically returned in 30-90 seconds. Complex multi-DTC faults take longer due to deeper reasoning.
One request. Four hops.
What your device sends, where it is authenticated, and what comes back.
Authentication and rate limiting resolve before routing, so an unauthenticated request never reaches a query. The response is one complete JSON document — packets show the path, not a timing claim.
One Endpoint. Unlimited PID Depth.
Send every PID your hardware reads. Our engine cross-references the full payload — not just standard OBD-II.
/v1/diagnose{
"session_id": "uuid",
"fault_code": "P0016",
"symptom": "Loss of boost under load, rattle on cold start",
"make": "Ford",
"obd_telemetry": {
"vin": "1FTFW1ET5DFC10312",
"dtcs_stored": ["P0016", "P0299"],
"dtcs_pending": ["P0300"],
"live_pids": {
"engine_rpm": 2450,
"calc_load_pct": 88.4,
"boost_pressure_psi": 4.2,
"fuel_rail_pressure_psi": 2150
},
"protocol": "CAN 11/500",
"deep_scan": {
"freeze_frame": { "rpm_at_fault": 2450, "speed": 62 },
"mode6_tests": { "misfire_cyl_2": { "value": 4 } }
}
},
"oem_telemetry": {
"pcm_calibration_id": "FL3A-14C204-BK",
"cam_intake_b1_pos_deg": 14.2,
"cam_intake_b1_target_deg": 22.0,
"vct_oil_solenoid_duty_pct": 68.4,
"wastegate_actuator_duty_pct": 92.0,
"turbo_boost_deviation_psi": -5.8
}
}The oem_telemetry object accepts any key-value map. Send proprietary PIDs your hardware reads — our engine reasons over the complete payload.
Technical Specifications
Your Hardware + Our Brain
= A Product Neither Can Build Alone.
Intelligence Without the R&D Overhead
Skip the 18-month build cycle. Integrate production-grade diagnostic intelligence into your hardware in weeks, not years.
300+ PID Intelligence
Your scanners already pull manufacturer-specific PIDs that generic tools ignore. Our engine actually understands what those readings mean together.
Tenant-Isolated Security
Each partner gets dedicated API keys with IP allowlisting, per-request audit trails, and independent rate limits.
Volume-Based Pricing
Session-based billing scales with your fleet — the same API and the same structured output at every volume, with per-tier rate limits from 60 to 1,000 requests per minute.
Ship in Days, Not Months
One REST endpoint. Standard JSON payload. Structured response schema. Your firmware team can integrate over a sprint.
Ready to Integrate?
Get sandbox API access, integration support, and volume pricing tailored to your device fleet.