Cambridge Mobile Telematics

Cambridge Mobile Telematics (CMT) is the world's largest telematics service provider, on a mission to make roads and drivers safer. Its AI-driven DriveWell Fusion platform gathers sensor data from millions of IoT devices — smartphones, proprietary Tags, connected vehicles, dashcams, and third-party devices — and fuses it with contextual data to build a unified view of vehicle and driver behavior. CMT powers usage-based insurance (UBI), crash detection and assistance, distracted-driving programs, fleet safety, and public-sector road-safety initiatives for insurers, automakers, rideshare, and government customers worldwide. Developers integrate via the gated DriveWell Mobile SDK (iOS/Android) and the DriveWell Portal; the platform is ISO 27001, ISO 27701, and SOC 2 Type II aligned. Backed by SoftBank Vision Fund and General Catalyst.

Cambridge Mobile Telematics is profiled on the APIs.io network. Tagged areas include Company, Enterprise, Telematics, Insurance, and Mobility.

Cambridge Mobile Telematics’ developer surface includes developer portal, documentation, engineering blog, support, and 9 more developer resources.

🌐 Visit website 📡 Source on GitHub

25.4/100 emerging ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-07-27 · rubric v0.5

0 APIs

CompanyEnterpriseTelematicsInsuranceMobilityUsage-Based InsuranceFleet SafetyConnected VehicleSDKCrash Detection

Kin Score

Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5

Composite quality — 25.4/100 · emerging

Contract Quality 0.0 / 25

Developer Ergonomics 4.8 / 20

Commercial Clarity 8.4 / 20

Operational Transparency 0.7 / 13

Governance 0.0 / 12

Discoverability 6.8 / 10

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 15

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/cambridge-mobile-telematics: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Get Started 2

Portal, sign-up, and the first successful call

Portal

Portal

Login

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Compliance

Compliance

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: cambridge-mobile-telematics
name: Cambridge Mobile Telematics
description: Cambridge Mobile Telematics (CMT) is the world's largest telematics service provider, on a mission to make roads
  and drivers safer. Its AI-driven DriveWell Fusion platform gathers sensor data from millions of IoT devices — smartphones,
  proprietary Tags, connected vehicles, dashcams, and third-party devices — and fuses it with contextual data to build a unified
  view of vehicle and driver behavior. CMT powers usage-based insurance (UBI), crash detection and assistance, distracted-driving
  programs, fleet safety, and public-sector road-safety initiatives for insurers, automakers, rideshare, and government customers
  worldwide. Developers integrate via the gated DriveWell Mobile SDK (iOS/Android) and the DriveWell Portal; the platform
  is ISO 27001, ISO 27701, and SOC 2 Type II aligned. Backed by SoftBank Vision Fund and General Catalyst.
url: https://raw.githubusercontent.com/api-evangelist/cambridge-mobile-telematics/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- general-catalyst
- softbank-vision-fund
x-tier: stub
x-tier-reason: portfolio-lead
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-18'
image: https://portal.cmtelematics.com/static/home/v2/logo.png
tags:
- Company
- Enterprise
- Telematics
- Insurance
- Mobility
- Usage-Based Insurance
- Fleet Safety
- Connected Vehicle
- SDK
- Crash Detection
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/cambridge-mobile-telematics-domain-security.yml
- type: Website
  url: https://www.cmtelematics.com
- type: Portal
  url: https://portal.cmtelematics.com
- type: Documentation
  url: https://www.cmtelematics.com/cmt-mobile-sdk/
- type: Login
  url: https://portal.cmtelematics.com
- type: Blog
  url: https://www.cmtelematics.com/news-and-insights/
- type: Support
  url: https://www.cmtelematics.com/customer-support/
- type: GitHubOrganization
  url: https://github.com/Censio
- type: PrivacyPolicy
  url: https://www.cmtelematics.com/privacy-policy/
- type: TermsOfService
  url: https://www.cmtelematics.com/mobilelicense/
- type: Compliance
  url: conformance/cambridge-mobile-telematics-conformance.yml
- type: Conformance
  url: conformance/cambridge-mobile-telematics-conformance.yml
- type: LLMsTxt
  url: llms/cambridge-mobile-telematics-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence