Choose between embedding Cambridge Mobile Telematics' DriveWell SDK and integrating via DriveWell Fleet's BYOD API when building a UBI program for an insurer
domain: cmtelematics.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Use the DriveWell SDK when the insurer wants trip detection, driver-vs-passenger classification, and risky-event scoring embedded directly inside its own branded mobile app
Use DriveWell Fleet's BYOD (Bring Your Own Device) integration instead when drivers already use third-party telematics hardware/platforms (confirmed named partners include Samsara, Verizon Connect, Lytx, Netradyne, Linxup, and GPS Insights) and no CMT SDK should be embedded
Under the BYOD model, integrate against CMT's suite of APIs that ingest and normalize the existing third-party telematics data, then enrich it with CMT's own risk scoring
For vehicles or drivers with no connected telematics source at all, plan for CMT's physical hardware (DriveWell Tag Pro for light-duty, Tag Max for heavy-duty) to cover the gap
Map the chosen integration path to the right CMT product line — DriveWell Risk (Premium Score, DriveWell Fleet) vs DriveWell Crash & Claims (DriveWell Crash, DriveWell Claims) vs DriveWell Engage — since these are separate product suites with different data contracts
Known gotchas
There is no CMT product literally named 'Tap' — the actual non-SDK hardware option is 'DriveWell Tag' (Pro/Max variants); don't build integration docs around a product name that doesn't exist in CMT's current lineup
BYOD integration depends on CMT already having a named partnership with the specific third-party telematics provider in use — an unlisted provider's data won't flow through the BYOD APIs without a separate integration agreement
DriveWell Risk, DriveWell Crash & Claims, and DriveWell Engage are separate product suites — assuming 'DriveWell' is one monolithic API leads to requesting data from the wrong product line's endpoints
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?