In case folks are curious about the underlying technical details, LADOT along with the Open Mobility Foundation (OMF) built the Mobility Data Specification (MDS

In case folks are curious about the underlying technical details, LADOT along with the Open Mobility Foundation (OMF) built the Mobility Data Specification (MDS) which are "RESTful APIs used to specify the digital relationship between mobility as a service Providers and the Agencies that regulate them." API Spec: https://github.com/CityOfLosAngeles/mobility-data-specification/tree/dev/agency https://github.com/CityOfLosAngeles/mobility-data-specificat... Uber, as they do, is refusing to comply with laws/provide data that would enable local governments to actually regulate them. As I understand it, the pilot phase was for Bikes/Scooters, but the intention is to require use of similar APIs by car based rideshare companies in the future. Which explains some of Uber's resistance despite this only currently covering JUMP Bike Share. There's a number of other cities (NYC, Miami, Philly, SF, SJ, SEA, etc) involved with OMF/MDS. LADOT is one of the first implementations but they aren't doing it all in house. Much of the design/development of the mobility API spec and open source implementation[2] has been contracted out to Lacuna.ai (via Ellis & Associates, a wholly owned subsidiary)[3]. [2]: https://github.com/CityOfLosAngeles/mds-core https://github.com/CityOfLosAngeles/mds-core [3]: http://clkrep.lacity.org/onlinecontracts/2019/C-130956_c_7-26-19.pdf#page=10 http://clkrep.lacity.org/onlinecontracts/2019/C-130956_c_7-2...