Zendrive

Zendrive Inc. was a San Francisco mobility risk intelligence company that turned an ordinary smartphone into a telematics sensor. Its product was a mobile SDK, not an HTTP API: an app embedded the Zendrive SDK, which automatically detected the start and end of every drive, collected accelerometer, gyroscope and GPS data with minimal battery impact, raised in-process callbacks for trip and collision events, and uploaded the drive for scoring. Fleets, rideshare operators and auto insurers consumed the resulting analytics — collision detection and severity, distracted driving, speeding, star ratings — through a dashboard and an Analytics REST API, with rideshare insurance-period modelling and a US/EU data-residency selector. Intuit acquired Zendrive's technology for Credit Karma's Karma Drive in 2024 and the developer program was shut down: as probed 2026-09-05 every Zendrive host is dead. Only the SDK reference, sample apps and published packages survive.

Zendrive is profiled on the APIs.io network. Tagged areas include Company, Telematics, Mobility, Insurance, and Automotive.

Zendrive’s developer surface includes documentation, API reference, getting-started guide, changelog, authentication, sandbox, and 11 more developer resources.

20.7/100 emerging Agent 11/100 agent aware Full breakdown ↓
scored 2026-09-05 · rubric v0.18.3
0 APIs
CompanyTelematicsMobilityInsuranceAutomotiveFleet ManagementDriving BehaviorMobile SDKRiskAcquired

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-05 · rubric v0.18.3
Regulatory Posture applies to this provider. Its tags matched the Insurance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/zendrive: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Zendrive Rate Limits

0 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Zendrive Authentication

2 schemes

SECURITY

Zendrive Domain Security

no transport/DNS hardening detected

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Source (apis.yml)

apis.yml Raw ↑
aid: zendrive
name: Zendrive
description: 'Zendrive Inc. was a San Francisco mobility risk intelligence company that turned an ordinary smartphone into
  a telematics sensor. Its product was a mobile SDK, not an HTTP API: an app embedded the Zendrive SDK, which automatically
  detected the start and end of every drive, collected accelerometer, gyroscope and GPS data with minimal battery impact,
  raised in-process callbacks for trip and collision events, and uploaded the drive for scoring. Fleets, rideshare operators
  and auto insurers consumed the resulting analytics — collision detection and severity, distracted driving, speeding, star
  ratings — through a dashboard and an Analytics REST API, with rideshare insurance-period modelling and a US/EU data-residency
  selector. Intuit acquired Zendrive''s technology for Credit Karma''s Karma Drive in 2024 and the developer program was shut
  down: as probed 2026-09-05 every Zendrive host is dead. Only the SDK reference, sample apps and published packages survive.'
url: https://raw.githubusercontent.com/api-evangelist/zendrive/refs/heads/main/apis.yml
image: https://avatars.githubusercontent.com/u/9817922?v=4
x-type: company
x-source: harvest:secondary-market
x-harvest-source-url: https://forgeglobal.com/zendrive_stock/
x-tier: stub
x-tier-reason: end-of-life-sdk-only
x-status: acquired-eol
x-acquirer: Intuit Inc. / Credit Karma
x-acquisition-announced: '2024-06-13'
x-acquisition-note: Intuit acquired technology from Zendrive to power Credit Karma's Karma Drive usage-based auto insurance
  product, along with CEO Dennis Ellis, co-founder/CTO Pankaj Risbood and certain employees. Terms were not disclosed. Announced
  2024-06-13, closed Q4 FY24.
x-domain-status: decommissioned
x-domain-note: 'zendrive.com and www.zendrive.com have NO A/AAAA record — the zone is still on Cloudflare nameservers and
  still carries Google Workspace MX records, but nothing answers on HTTP. developers.zendrive.com, app.zendrive.com, api.zendrive.com,
  iql.zendrive.com and status.zendrive.com are NXDOMAIN. docs.zendrive.com is a dangling Cloudflare CNAME and returns HTTP
  403 with the 17-byte body "error code: 1014" on every path, including every /.well-known/ and spec path. None of those 403s
  is a document. No Website pointer is wired, because the company has no live site; the Forge Global secondary-market listing
  that seeded this record is kept under x-harvest-source-url rather than as a Website, since a trading venue page is not a
  company web presence. See well-known/zendrive-well-known.yml.'
specificationVersion: '0.20'
created: '2026-09-05'
modified: '2026-09-05'
tags:
- Company
- Telematics
- Mobility
- Insurance
- Automotive
- Fleet Management
- Driving Behavior
- Mobile SDK
- Risk
- Acquired
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: GitHubOrganization
  url: https://github.com/zendrive
- type: Documentation
  url: https://zendrive-root.bitbucket.io/ios/docs/latest/index.html
- type: APIReference
  url: https://react-native-zendrive-api-v2.netlify.app/
- type: GettingStarted
  url: https://react-native-zendrive-guide-v2.netlify.app/readme
- type: SourceCode
  url: https://github.com/zendrive/zendrive-sdk-ios-sample
- type: Packages
  url: packages/zendrive-packages.yml
- type: SDKs
  url: packages/zendrive-packages.yml
- type: ChangeLog
  url: changelog/zendrive-changelog.yml
- type: Lifecycle
  url: lifecycle/zendrive-lifecycle.yml
- type: Authentication
  url: authentication/zendrive-authentication.yml
- type: ErrorCatalog
  url: errors/zendrive-error-codes.yml
- type: Sandbox
  url: sandbox/zendrive-sandbox.yml
- type: Conformance
  url: conformance/zendrive-conformance.yml
- type: Plans
  url: plans/zendrive-plans-pricing.yml
- type: RateLimits
  url: rate-limits/zendrive-rate-limits.yml
- type: LLMsTxt
  url: llms/zendrive-llms.txt
- type: DomainSecurity
  url: security/zendrive-domain-security.yml
x-enrichment:
  date: '2026-09-05'
  status: enriched
  artifacts_added: 13
  pass: local-v3

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/zendrive"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/zendrive/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/zendrive/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.