Question 1

What is DIMO?

Accepted Answer

DIMO is vehicle data infrastructure that connects vehicles, drivers, and on-demand services. It provides a unified, permissioned data-access layer for vehicle identity, real-time telemetry, and owner consent, allowing service providers to avoid establishing separate integrations with each automotive brand. This definition focuses on data and access infrastructure, rather than DIMO owning vehicles or driving them for users. Whether vehicle-related services can operate depends on the vehicle's connection status, available signals, and whether the owner grants the corresponding permissions.

Question 2

How do owners control access to vehicle data?

Accepted Answer

Vehicle owners use granular, auditable permissions to control who can access vehicle data, and can grant or revoke access. DIMO permissions can be enabled for a session and expire when the session ends, so authorization does not have to mean continuously open access. The actual process is as follows: a service or application requests the data access it needs, and the owner consents within the permitted scope; only while the permission is valid can the application read the corresponding information as authorized; after the owner revokes permission or the session expires, that access should no longer remain valid. Permission controls concern data access and do not change vehicle ownership.

Question 3

How can developers use vehicle data through DIMO?

Accepted Answer

After receiving owner authorization, developers can use DIMO interfaces to query vehicle identity and real-time telemetry, such as location, battery or fuel level, mileage, tire pressure, and diagnostic trouble codes. DIMO also provides GraphQL and REST interfaces as well as corresponding SDKs. “Queryable” does not mean developers automatically have all vehicle data. Returned content must be constrained by signals the vehicle can provide and the scope of owner authorization; developers should request only the data required to complete their services and handle situations where data can no longer be read after authorization expires or is revoked.

Question 4

What service scenarios can the DIMO network support?

Accepted Answer

DIMO is suited to services that need data and permissions that change over the course of a vehicle-use session, such as rentals and fleet turnover, usage-based billing or subscriptions, session-based insurance and risk management, reservations and handoffs, and maintenance triggered by usage conditions. The common process in these scenarios is that a service confirms vehicle and driver identity and obtains permission at the beginning of a session, reads the required telemetry during the session, and completes the service or settlement according to rules at the end. Whether it can be used for a specific vehicle or service still depends on connectivity, data availability, and authorization status.

Question 5

What is the difference between DIMO and DIMO Credit (DCX)?

Accepted Answer

DIMO is the network's utility and governance token, while DIMO Credit (DCX) is a different in-network payment token. DIMO governance materials from 2024 state that DCX can be created by burning DIMO, so converting DIMO to DCX reduces the corresponding DIMO balance. This distinction is important: holding DIMO is not the same as holding DCX, and paying with DCX is not the same as directly paying DIMO. Users need to confirm conversion availability, conversion conditions, and payment scenarios under current product rules; descriptions in historical materials should not be treated as a commitment that all services are currently available.

Question 6

Will sharing vehicle data always earn DIMO?

Accepted Answer

DIMO developer documentation states that users can receive DIMO token rewards when they share vehicle data with service providers. These rewards connect data sharing with participation in network services, but they do not necessarily arise merely from holding tokens or connecting a vehicle. To receive rewards, there must at least be an applicable service, the user must complete data sharing as required by that service, and the user must meet its settlement rules. Reward eligibility, amount, timing, and whether rewards continue to be offered should be determined by the rules publicly available when participating in the service, and should not be understood as a fixed annualized return.

Question 7

How can DIMO tokens participate in governance?

Accepted Answer

A 2024 DIMO Foundation governance page records that DIMO holders on Polygon or Ethereum could register to vote or delegate their votes. This shows that DIMO was previously used in specific governance-voting arrangements. That page is historical material and cannot automatically prove that the same eligibility, supported-chain scope, or delegation process remains open today. Whether governance rights can actually be exercised depends on new proposals, snapshots, registration, and voting rules; users should rely on current official governance announcements when participating.

DIMO (DIMO) Price

DIMO (DIMO) Price Performance

Fear & Greed Index

Why Did DIMO (DIMO) Rise in the Last 24 Hours?

About DIMO (DIMO)

Use Cases and Features

Supply and Issuance Mechanism

How to Buy and Use DIMO (DIMO)

How to Buy

Related Markets

DIMO (DIMO) Basics & Market Insights

Fundamentals

Frequently Asked Questions About DIMO (DIMO)