DIMO is the most open and secure mobility platform in the world, powering the next generation of connected car applications and services. DIMO stands for 

Digital Infrastructure for Moving Objects

, obviously, our vision applies to all moving objects despite the current focus on vehicles. DIMO is part of the 

 that aims to connect your real world assets (RWA) with the blockchain.

With the use of web3 technology and built on the 

, DIMO guarantees openness, fairness, and performance in ways that are impossible for traditional mobility platforms. The DIMO Protocol utilizes cryptography and on-chain permissions to put users in full control of their vehicle and its data, revolutionizing how vehicle data is shared.

Automakers are spying on drivers and selling driving data to insurance companies without the user's consent or permission. Read more on how automakers abuse consumers' data ownership and treat user privacy:

Your Car Is 'The Worst' At Protecting Your Data

🤑 Automakers Sold Driver Data To Insurance Companies For Next To Nothing

🔓 It’s Official: Cars Are the Worst Product Category We Have Ever Reviewed for Privacy

The worst part is where many of the mobility solutions are now using GPS and sensors on mobile phones to act as the source of truth for your vehicles, which introduces more issues such as location-spoofing and 

💥 The car is usually one of the more expensive assets that one may purchase throughout their lifetime, the true cost of owning a vehicle in the US today exceeds $10,000 annually. Even with car prices dipping, the cost of insurance, maintenance, financing (fees & interest), license & registration, and simply gas price have been on the rise. With carmakers charging for data subscriptions in a siloed setup, innovative builders like you are staying ahead of the curve by embracing web3 and building on DIMO.

We can discuss all day about how slow the legacy automobile industry has responded to these user privacy concerns, and how traditional B2B mobility solutions have used their creativity to partially solve these problems by stacking tech on tech. At the end of the day, these solutions are still plagued by inefficiencies and bulky legacy software, moving "

At DIMO, we look to make things easier for developers starting from the source: 

. All car makes and models are decoded and defined in what we called 

 on the blockchain, stored using Tableland. Once a vehicle owner registers their vehicle on-chain, the publicly known data such as make model year are made available via our 

. And when a vehicle sends over its corresponding data to DIMO, where we then process, normalize, and served to developers via our 

But wait a minute, what makes DIMO different?

Before developers can get their hands on the private driving data, the 

 ensures that vehicle owners have full control over what they share with the application builders. The vehicle owners that own the vehicle NFT, will need to grant privileges to the apps by signing a blockchain transaction.

Imagine a world where you have 3 cars: a BMW 🇩🇪, a Tesla 🇺🇸, and a Toyota 🇯🇵. You use the DIMO Mobile app and onboarded all 3 cars, seeing data for yourself and your family members that drive those cars. You can also explore and find new services that work seamlessly with all 3 cars, get notified for small issues that you wouldn't notice (unless you did data and signal analysis), check for answers with an AI mechanic, book maintenance appointment, and file for an insurance claim - all powered by the 

https://console.dimo.xyz/

 and register for an account. Follow the steps below to get yourself API credentials:

Connect your wallet at some point, either during the registration process or after

 and fill in details to provision a Developer License (in 

Approve the spending amount & sign the transactions to obtain your Developer License

Generate a signer, acting as the API key (aka 

Once completed, you should see your app shown in the home screen. Click on the app to configure the following:

 that is issued to a developer or an organization. The license, when configured properly, allows the developer to 

The Developer License consists of several fields that you will need to know about:

With the combination of these 3 parameters, you can then head over to the 2nd section to learn more about accessing data using the 

Introduction

Postman requests and cURL commands are nice when testing your API access, but given the fact that there's a signing challenge step in the auth process, it's quite the pain. So, we've built several different SDKs to assist with getting API access and making API requests!

In one of code in your preferred language, you'll be able to authenticate with the DIMO Auth server and get back an 

 and start interacting with the API endpoints.

DIMO offers a publicly available entry point in our 

. This is an open directory to the DIMO Network, showcasing all the vehicles that currently exist in the network. The Identity API is a GraphQL API with on-chain data, from DIMO vehicle data like the make, model, year - all the way to device definitions in Tableland.

https://identity-api.dimo.zone/

 and start exploring the documentation and write your own queries in the interactive interface. To help you get started, we've made a few 

Once you have an idea on how to access data via the SDK and the public API endpoint, let's proceed to getting access to driving data. Vehicle owners have full control over how they want to share their vehicle NFT's driving data to, and the 

 of your Developer License would be where vehicles are shared to.

Granted that your license has vehicles granting you privileges (run the following query in Identity API to check), you now have the keys to accessing private data:

query GetVehicleByDevLicense {
  vehicles(filterBy: { privileged: "<your_client_id>" }, first: 100) {
    nodes {
      tokenId
      definition {
        make
        model
        year
      }
  }
}

To query for private vehicle data, you're going to need to get a 

 before deciding on which APIs you'll want to access. 

 you got back from the Auth server, you'll need to then hit our 

with the vehicle of your interest. This goes back to how DIMO helps protect the user's privacy and therefore the two-step security design (

The SDKs have built-in functions to help you obtain a 

 for a shared vehicle without needing to go through the hassle.

, you have now fully-unlocked the world of DIMO.

DIMO offers an abundance of API endpoints that provide app builders with data insights, ranging from things like vehicle sensor data in our 

. To get started with querying these APIs, simply plug the 

 in an auth header as seen below before issuing a query:

{ Authorization: "Bearer <privilege_token>" }

https://telemetry-api.dimo.zone/

 and add in your auth header to get started. Try querying for a vehicle that you have been granted access to and see the vehicle in action.

Accessing Data

In summary, cars are essential tools that's been around for too long, but the utilization rate of the car has been stagnant due to centralization. Not to mention that cars depreciate in value the moment it hits the road. 

To help the decentralization movement, DIMO is looking for developers to build on DIMO and create values for the drivers and vehicles that are connected. Come build the network of IoT devices and moving objects!