Algorithm tier deliverable
NADIR Pulse is the embeddable sensor-reliability lane for partners who need CAUTION and CRITICAL tier classification at scale — under 200ms per vehicle, without forecast compute or 3D twin overhead.
Live simulation
Interactive comparison lab embedded from /tier-benchmark — same Mahalanobis gates as production Pulse,
with telematics and micro-fleet demo presets. Shadow-mode simulation only.
Demonstration overlays — Meridian and Apex use calibrated simulation models. Not safety-certified.
Capability map
Cross-modal residual distance with fleet-normalized gates.
NOMINAL / CAUTION / CRITICAL with confidence bands.
Push tier transitions to maintenance or telematics systems.
Rate-limit buckets tuned for 10k+ vehicles per org.
Simplified fleet queue + weekly PDF digest on micro pilot.
Interactive demo mode mirrors Pulse scoring path.
Commercial
Indicative USD pricing · shadow-mode on every tier · binding terms in LOI or MSA.
Pulse
$3–5
per vehicle / month
$750 · 4 weeks · 50–200 vehicles
Build LOI →Model annual NADIR cost vs calibration-incident avoidance for buyer conversations.
Developer surface
Org-scoped Bearer API keys · RBAC scopes gate algorithm depth · OpenAPI v1 contract.
telemetry:ingest
Batch and streaming telemetry POST
drift:pulse
Mahalanobis scoring lane only
fleet:read
Health summary + tier counts
platform:webhooks
Tier transition events
Go-to-market
Telematics platform VP
“We need a sensor-health module we can white-label without 18 months of perception R&D.”
Typical buyer on NADIR Pulse.
Regional fleet safety mgr
“I need to know which vans crossed CAUTION this week — not a 14-day forecast.”
Typical buyer on NADIR Pulse.
Compliance officer
“Prove we continuously monitor ADAS calibration post-repair.”
Typical buyer on NADIR Pulse.
DSP operations lead
“High volume, tight margins — tier gates only.”
Typical buyer on NADIR Pulse.
Onboarding
12-vehicle sample org · all scopes for integration testing · make dev-api local stack.
Wire POST /v1/telemetry/ingest from telematics or batch replay · validate tier gates.
Console or webhook alerts · weekly digest · Exhibit A metrics for LOI conversion.
Per-vehicle billing at Pulse rate · optional API add-ons per integration depth.
Compare
| Capability | Pulse | Meridian | Apex |
|---|---|---|---|
| Tier gates (NOMINAL/CAUTION/CRITICAL) | ✓ | ✓ | ✓ |
| Survival / time-to-CRITICAL | — | ✓ | ✓ full |
| HORIZON Command Deck | — | ✓ | ✓ |
| 3D Fleet Twin + CRLB | — | — | ✓ |
| Signed evidence exports | — | Limited | Unlimited |
| Typical latency | <200ms | 0.5–2s | 2–8s |
| Per-vehicle / mo | $3–5 | $3.75 | $8.50 |
SDK reference
Install: pip install -e "NADIR_SDK/python[dev]" · TypeScript client at NADIR_SDK/typescript
from nadir_sdk.scoring.pulse import score_pulse, SensorReadings
result = score_pulse(
"van-0142",
SensorReadings.from_mapping(payload["sensors"]),
baseline_camera_rotation=baseline_R,
)
# drift_tier: NOMINAL | CAUTION | CRITICAL
# mahalanobis_distance, probable_fault_source
Telemetry contract
Same JSON schema across tiers — algorithm depth is selected by org plan and ?tier= routing.
{
"vehicle_id": "van-0142",
"timestamp": "2026-06-10T14:22:01Z",
"sensors": {
"camera_rotation_matrix": [1.0, 0.01, 0.0, -0.01, 1.0, 0.0, 0.0, 0.0, 1.0],
"radar_range_bias_m": 0.002,
"radar_azimuth_bias_deg": 0.15,
"lidar_registration_error_m": 0.001
},
"timestamp_quality": { "sync_ok": true, "jitter_ms": 4 }
}
9-element row-major rotation vs baseline. Primary signal for extrinsic drift.
Range systematic error in meters — converted to mm in residual vector.
Cross-modal registration residual for fusion disagreement detection.
sync_ok and jitter_ms — gates unreliable frames before scoring on Meridian+.
Resolved from API key context — strict org isolation on every fleet record.
Deployment patterns
Partner sends CAN + camera metadata batches nightly; Pulse returns tier counts for their dashboard widget.
High-volume ProMaster fleet — webhook on CAUTION after loading-dock impacts.
MSO subsidiary proves continuous monitoring without forecast SLA.
Fleet demonstrates monitoring program exists for ADAS-equipped vans.
On-depot gateway aggregates 500 vehicles; single ingest burst under rate limits.
City vendor supplies weekly tier JSON for procurement review.
Operations
Terminology
Multi-sensor drift vector fused into one statistical distance — core signal on every tier.
6-DOF misalignment of camera/radar/lidar relative to vehicle frame.
Advisory analytics only — no ECU writes or in-loop vehicle control.
NOMINAL / CAUTION / CRITICAL classification from residual thresholds.
Signed evidence bundle metadata for insurer and auditor review.
Time-to-tier exceedance probabilities (Meridian+).
Fisher-information uncertainty glyph for 3D twin (Apex).
POST replay protection — cached response on duplicate ingest.
API key from Org A cannot read Org B fleet records.
LOI attachment with week-1 pilot metrics JSON.
Quick integration
curl -sS -X POST "https://api.nadirai.net/v1/telemetry/ingest?tier=pulse" \ -H "Authorization: Bearer $NADIR_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: ingest-van-0142-20260610" \ -d @telemetry_frame.json
{
"event": "tier.changed",
"vehicle_id": "van-0142",
"previous_tier": "NOMINAL",
"drift_tier": "CAUTION",
"mahalanobis_distance": 3.42,
"probable_fault_source": "camera_extrinsics",
"algorithm_tier": "pulse",
"organization_id": "org-acme-regional"
}
Extended FAQ
FAQ
$750 · 4 weeks · 50–200 vehicles · same claim boundary on every tier · upgrade path without re-architecture.