Automotive
Providers using this tag (415)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 6 Solid coverage with minor gaps
Developing 34 Usable, with meaningful gaps to close
Thin 39 Limited public surface area
Emerging 115 Early or largely undocumented
Minimal 217 Almost no public developer surface
Unrated 2 Not yet scored
APIs with this tag (56)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Exemplar 1 Complete, well-documented, and agent-ready
Developing 31 Usable, with meaningful gaps to close
Thin 9 Limited public surface area
Emerging 10 Early or largely undocumented
Minimal 5 Almost no public developer surface
Companies reaching this through an API (10)
These companies publish an API, specification or operation carrying “Automotive” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Where this tag sits
415 providers carry this tag directly, and 615 counting the 8 narrower tags below and the 4 beneath them — 200 more to reach.
Related tags
Where this tag comes from
Markets provisional
Kin Score markets whose measured providers carry this tag. Share is the fraction of the market's measured providers that carry it — it describes the market, not this tag.
| Market | Share of the market's providers |
|---|---|
| Automotive and Mobility | 44% |
| FMCSA Registered Electronic Logging Devices | 30% |
| Autonomous Vehicles (self-driving testing, deployment, robotaxi service) | 24% |
Cohort brief
Auto-generatedThe 386 providers in the APIs.io catalog tagged Automotive, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Discoverability | 55.7 | 57.9 | -2.2 | 386 |
| Contract Governance | 4.2 | 6.5 | -2.3 | 386 |
| Operational Transparency | 8.5 | 13 | -4.5 | 386 |
| Access Clarity | 17.3 | 23.9 | -6.6 | 386 |
| Developer Ergonomics | 16.2 | 23.2 | -7 | 386 |
| Contract Quality | 9.7 | 17.2 | -7.5 | 386 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 9% | 13% | -4 |
| MCP server (first-party) | 6% | 12% | -6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 10% | 11% | -1 |
| Security | 99% | 98% | +1 |
| Arazzo workflows | 1% | 2% | -1 |
| Governance rules | 5% | 16% | -11 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 CarsXE 72.4
- 2 HERE 70.2
- 3 iwant.fyi 60.1
- 4 Apibara.tech 58.7
- 5 TheCarApi 58.2
- 6 UVeye 57.1
- 7 Shop-Ware 56.6
- 8 Amazon IoT FleetWise 54.9
- 9 PartsTech 52.6
- 10 AutoFi 52
- 1 CarsXE 69.1
- 2 HERE 55.5
- 3 Auto.dev 52.6
- 4 Apibara.tech 50.8
- 5 ADRO 49.6
- 6 AutoFi 48.4
- 7 iwant.fyi 44.2
- 8 Mercedes-Benz Mercedes me 43
- 9 Meero 42.4
- 10 Renesas 42
Coverage caveat. 365 of 386 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 24 October 2026, across 31984 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.