If you are such a brilliant REST API architect, please RTFA and explain it to us all for him.
I already have explained the difference between a public REST API and a closed API - that just happens to use REST-like syntax. I already explained how it's similar to how my mail transport interacts with the virus scanner, or the IMAP server - that it isn't intended to be open. I already explained that I'd happily upvote every one of your posts IF Tesla had said it was an open API to be used for third parties to provide capabilities to your car. But it's not.
I don't see anyone supporting your position here. If you choose to believe that's because TMC has no one critical of Tesla, perhaps you'd better read that last paragraph again, where I say that you have a supportable position and I'd add to your position if and only if Tesla advertises this as an open API.
Tesla's API just doesn't fit your religion, and that's ok. You have a right to believe every API should be an open API that uses OAUTH. That's okay, in my early days of IT architecture I used to believe everything should be 100% modular and should use very expensive integration capabilites; that compilers shouldn't have loop unrolling or use inline code. Someone might use that snippet of code one day and keeping it modular is the only way, etc., etc.
I don't believe that anymore. I've moved on. And I can admit that I was wrong back then, that there are places for single-use code, closed API's, and narrow optimizations. Moreover, in my daytime job, I am responsible for application integration services and API's, and the budget I'm responsible for doesn't leave room for such overly complex architectures.
Absent anything new, I'm moving on, and you have near-zero credibility in my eyes.