If you are evaluating Smartcar, you are almost certainly trying to do one of two things: read vehicle data across many brands, or build a product that acts on vehicles: unlock, grant access, cap spend, and cleanly end it all. Smartcar is excellent at the first. DIMO is built for the second. Smartcar is a window into the car; DIMO is the checkout desk.
Smartcar reads data and issues commands through a clean API. What it does not provide is a session: a single object that bundles identity, a digital key, a scoped data grant, a spend cap, and atomic revocation, with a verifiable record when it ends. For a dashboard or an analytics feature, you may never need that. For a rental, a carshare, or any case where a stranger temporarily uses a vehicle, the session is the whole job.
Side by side
| Capability | Smartcar | DIMO |
|---|---|---|
| Read vehicle data across brands | Yes | Yes (50+ OEM brands) |
| Issue commands (lock/unlock) | Yes | Yes |
| Digital key as part of a session | — | Yes |
| Per-session spend cap | — | Yes |
| Atomic revocation of a whole session | — | Yes |
| Verifiable, signed access audit trail | — | Yes |
When to choose which
Choose Smartcar when your product is fundamentally about reading data: usage analytics, EV charging insights, a service that needs odometer or battery state. Choose DIMO when your product governs access: unmanned rental, carshare, fleet dispatch, per-session insurance. It needs identity, keys, data, spend, and revocation to behave as one consented, auditable unit.
The model behind that is vehicle session infrastructure; see it applied to rental operations, and start in the developer docs.