Launch HN: Telematica (YC W22) – Plaid for Electric Vehicles
For better or worse, all modern EVs include built-in internet connectivity and send all vehicle data to the manufacturer’s cloud servers, effectively eliminating the need for external hardware devices and OBD II dongles. The problem is that all of this information is locked inside the car dashboard or the manufacturer’s mobile app—technologies that car companies are not the greatest at building. There is no official Tesla or Volkswagen API available for developers to use to create apps and services based on vehicle data.
Some car APIs exist, but don’t focus on EVs. The fundamental problems in EVs—range anxiety and charging management—are absent in ICE vehicles. This means that developers have to build a lot of tools on top of the car API before they can solve their actual business problems. For example, (1) charging point operators must be notified when the charging begins and receive live SoC (State of Charge) every 1 minute; (2) fleet operators need to poll data to manage their operations or perform predictive maintenance; and (3) smart charging companies and utilities must manage charging based on live charging data and energy prices.
We eliminate the need to build and maintain an additional layer of infra on top of the car API for each of the above use cases by providing webhooks, data logging, and a plug-and-play smart charging module. Our product is divided into two parts: an authorization flow to obtain user consent from the EV owner to connect their car with a third-party app, and a developer API that allows our customers to query live EV data, manage EV charging, and log data for specific endpoints.
We came up with the idea for Telematica while working on a Tesla-like trip planner for the Indian market to reduce range anxiety among EV drivers. Unlike in the US, where Tesla controls both the car and the superchargers, the Indian market is fragmented - car manufacturers lack a robust charging network. Controlling both the car and the charger allowed Tesla to answer a variety of questions, such as "Will I be able to reach my destination with my current SoC?" How many charging stops should I take? My ETA, including the charging time? and so forth.
We needed access to real-time battery and location data in order to build a smart route planner. And, to our surprise, there was no Tata API (India's largest EV OEM) that we could use directly. To address this, we reverse engineered the Tata mobile app and identified the API endpoints before developing a Plaid-like product that relies on EV owners' consent to share their data with a third party app. We had to figure out the API for each OEM separately, which was time-consuming and difficult. This made us realise that instead of building the end user app let's build a developer API that anyone in the future can use to build powerful EV apps.
Our customers range across various industries. Companies that are building the charging infrastructure or mobility apps use our API to get access to real-time battery data (SoC, range, charging status). We are used by utilities and companies that offer demand response programs to manage EV charging during peak hours. Finally, instead of purchasing expensive OBD dongles, fleet operators use us to manage their fleets and optimize their charging schedules and routing.
We charge $0.25 per EV connected with up to 10,000 API calls allowed per month. Connecting up to 10 EVs is free of charge.
We collect the account credentials to the OEM (manufacturer) account as most of the EV brands don’t have their own OAuth2. We try to only store tokens...
48 comments
[ 4.5 ms ] story [ 109 ms ] threadI wish that were just a joke.
A lot of people in the community use Teslamate and Teslafi. The Tesla unofficial API is actually pretty good too.
Anyway, congrats on shipping and I will def. try it out since I have a product on a similar vertical. Actually, how may I get in touch?
I tested out the Renault reverse engineered API and BMW Cardata -> each one of them has it's (major) downsides. Especially unfortune for BMW Cardata, which is an official product that had a lot of downtime and really irregular data updates (at least for older cars).
So hats off to the Telematica guys for trying to bridge all this together.
How do they control the rate of api calls?
Thanks.
Almost every major platform I can think of was slow to provide what it's innovation community wanted - I remember giving countless apps my Twitter or LinkedIn passwords in order to access 3rd party functionality and value. Blackberry/RIM held a frightening number of email address and passwords in order for the service to work.
But there's something very uncomfortable about surrendering my EV's credentials to the point that I just won't do it.
I bristle not only at giving away access to my current location but also where I'm going. I don't especially like the idea of Tesla having all this data but I'm certainly not comfortable with small startups having it.
In the event that security is compromised there's also too much opportunity for mass-griefing and inconveniencing - locking me out of my car, heating my car at the highest temperature (I won't go on, but you get the point).
My take is that the engineers at Tesla know how to build OAuth - they intentionally are not doing this because the company is not ready for this world or prepared to accept it - yet. By requiring you to give away the farm with your username and password it maintains a high stakes 'all or nothing' which I'm sure they hope will put off most of their customers.
Give it time, but once these companies do have petitioned permissioning I'm not sure what the value add will be for these startups like Telematica.
The government can toss you in jail if they don’t like the cut of your jib, and this data lets them find a way to do so quasi-legally. Small data-hungry startups can’t really damage you with this data by comparison.
The privacy ship has sailed. If you want location privacy, rip out the GSM transceiver in your car and turn location services off on your phones.
Even then the GSM towers are following you and selling your location tracks, but at least it’s slightly harder to tie to your other data then.
The difference is Tesla has a lot to lose if they can't demonstrate adequate consumer protection of the data from theft/unauthorized access - and significant consequences if a breach does occur. They should also have high quality engineering talent to make sure exploits don't occur.
A small startup doesn't have the same burdon on penalty for breach and probably far lower quality of eng talent.
This is why I reluctantly concede to Google and Tesla tracking my location, but not random startups.
What was the process of reverse engineering the APIs like?
- 2016 YC invests in Smartcar.
- 2019 Otonomo lost lawsuit to Smartcar after stealing/copying them. https://news.ycombinator.com/item?id=19719380
- 2021 YC decides to invest in Enode which cloning Smartcar. https://news.ycombinator.com/item?id=26468448
- 2022 YC decides to invest in Telematica which cloning Smartcar.
I give this another 12 months for YC to invest in the next clone.