Step 01
Connect telemetry
POST batch ingest from telematics, MSO exports, or simulation. SDK handles schema validation and tier histograms in under 5 seconds.
Live product · shadow mode · API-first
Real-time agent SDK & API for sensor correction
NADIR turns fleet telemetry into calibration actions — detect extrinsic drift, score severity, open workflow cases, and export signed evidence. Not a dashboard. Infrastructure your telematics stack embeds.
67 API operations · Python + TypeScript SDK · HORIZON command center · No ECU writes
Shadow advisory only — not in-loop vehicle control. Built for pilots that close in days, not homologation cycles.
FMVSS 127 tailwind
Signed evidence graph
Org-scoped API keys
make demo-complete CI
How it works
Telemetry in. Corrected fleet out. You keep the audit trail.
One workflow from raw frames to defensible calibration proof — the same pipeline powers API Theater, Console dispatch, and HORIZON.
Step 02
Run correction agents
Tri-tier scoring (Pulse → Meridian → Apex), SSE changepoint streams, and fleet-wide knapsack prioritization — pick depth per vehicle.
Step 03
Close the loop
Open workflow cases, verify evidence bundles client-side, and push HMAC-signed webhooks to your ops stack.
Who it's for
Three buyers. One correction layer.
We're piloting with regional fleets, repair networks, and telematics embeds — complementary to physical calibration bays, not a replacement.
Fleet operators
Which vehicles need calibration this week? CRITICAL-first dispatch queue with 14-day forecast.
Console dispatch demo →Repair & glass networks
Audit-grade proof that post-repair calibration was caught and documented — MSO-scale evidence.
Safelite pilot track →Telematics & data platforms
Embed a “sensor reliability” module via API — without 18 months of perception R&D.
SDK + API quickstart →Product
API depth. Operator surfaces when you need them.
Lead with the SDK for embeds. Expand into Console and HORIZON when the buyer wants a command center.
Core wedge
Agent SDK + API
67 operations, OpenAPI 3.1, Python + TypeScript SDK, tiered inference lanes, webhooks.
Developers → OperatorsDispatch Console
Case queue, workflow closeout, readonly demo keys for investor walkthroughs.
Launch console → Strategic accountsHORIZON 3D
Fleet twin, forecast studio, evidence theater — the board-meeting surface.
Open HORIZON →See it live
No slideware. Click the product.
Every link below is a real surface wired to production API contracts (shadow mode).
Why this compounds
The fleet product is the wedge. The evidence graph is the moat.
Every deployment adds proprietary drift intelligence — how sensors fail by route, climate, and repair type. That data does not exist in incumbent tooling.
5.2d
Pulse median lead-time (tier bench)
~193
API tests in CI
3 tiers
Pulse · Meridian · Apex depth
Shadow
Pilot in days, no ECU writes
Pilots
Start small. Expand per vehicle.
Transparent pilot pricing — designed to close LOIs fast, then expand algorithm tier depth.
Shadow kickoff
$750
- 50–200 vehicles
- Read-only shadow monitoring
- 2-week signal report
Paid pilot
$2,800
- 6 weeks · workflow + evidence
- Meridian-class scoring
- LOI-ready metrics pack
Fleet subscription
$4.5k+
- From 500 vehicles
- Per-vehicle tier upsell
- API + Console + HORIZON
From the founders
ADAS calibration guides for fleet & repair operators
Longform articles on drift detection, MSO evidence, and NHTSA readiness — written by Dhruv Hegde and Sri Balaji.
Hire your first sensor correction agents.
30-minute call. We'll run API Theater live, scope a shadow pilot, and share the diligence pack.