The Automotive vertical at apis.io/industries/automotive/ tracks 42 providers and 94 APIs across four sub-sectors — vehicle manufacturing, truck leasing and rental, connected vehicles and mobility, and fleet servicing.
At 2.2 APIs per provider it is denser than retail or consumer goods. It is also, for an industry that has spent a decade calling itself a software business, remarkably thin at the top.
The bands
| Band | Providers | APIs |
|---|---|---|
| Developing | Volkswagen 59.4, Visteon 50.1, Tesla 48.2, Lyft 47.0, Dana 46.9, Ryder System 46.1 | 3–13 |
| Thin | Mercedes-Benz 43.3, Ford 35.5, Rush Enterprises 35.4, Goodyear 34.9, Carvana 31.0, BMW 30.9 | 1–18 |
| Emerging | Hyundai 22.4 | 1 |
Volkswagen leads at 59.4 — on three APIs. Mercedes-Benz publishes 18, the largest surface in the vertical, and scores 43.3 in the thin band. BMW publishes 6 and scores 30.9. Hyundai publishes one.
Volume and quality diverge sharply here
Mercedes-Benz is the clearest case in this week’s sweep of surface size and description quality moving in opposite directions. Eighteen APIs is a real developer program — vehicle status, remote functions, fuel data, telematics. Scoring 43.3 on them means they are published without the specification depth that would make them straightforwardly consumable.
Volkswagen’s three APIs scoring 59.4 is the inverse: a smaller surface, better described.
For a developer, the smaller well-described program is the more usable one. For an agent, it is not close.
What’s shifted
Three patterns:
- Suppliers outscore manufacturers. Visteon (50.1) and Dana (46.9) — both component suppliers — sit above Ford (35.5), BMW (30.9), and Hyundai (22.4). Suppliers integrate with manufacturers’ systems for a living; that pressure produces described interfaces.
- Fleet is the quiet leader in depth. Ryder System publishes 13 APIs at 46.1. Commercial fleet customers demand telematics integration as a contract term, which forces a real API rather than a demo.
- Consumer-facing connected-car APIs are gated, not open. Tesla (48.2, 4 APIs) is the highest-profile connected-vehicle program and still a modest surface. Manufacturers treat vehicle data as an asset to license rather than a surface to publish.
The data that is not here
Modern vehicles generate continuous telemetry — location, battery state, diagnostics, driver behaviour. Almost none of it appears in this catalog as a described API. Where it is exposed, it is behind partner agreements rather than public specifications.
That is the same shape as this week’s energy finding: the data exists at enormous scale, the business case is obvious, and the public API layer was never built.
Takeaway
42 providers, 94 APIs, a ceiling of 59.4 on three endpoints, and the biggest publisher sitting in the thin band. Automotive has more API surface than most legacy verticals and less description quality than nearly all of them — a decade of software talk that has not reached the specification.