niche · -0.8 market industry

Connected Vehicles

Score 18.1 / 100 67 providers 16 APIs Search apis.io →
Variants seen in the corpus: Connected VehicleConnected CarConnected CarsConnected Vehicles

Providers using this tag (67)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Exemplar 1 Complete, well-documented, and agent-ready
Developing 5 Usable, with meaningful gaps to close
Thin 16 Limited public surface area
Emerging 22 Early or largely undocumented
Minimal 23 Almost no public developer surface

APIs with this tag (16)

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 →

Developing 8 Usable, with meaningful gaps to close
Thin 1 Limited public surface area
Emerging 3 Early or largely undocumented
Minimal 4 Almost no public developer surface

Score breakdown

Frequency
48.6
log-scaled weighted occurrences
Breadth
0.9
spread across providers
Quality lift
19.6
mean composite of providers using it
Cohesion
12.3
strength of nearest seed neighbor

Related tags

Telematics 39 co-occurrences Vehicle Data 19 co-occurrences Automotive 51 co-occurrences Electric Vehicles 23 co-occurrences Automobiles 7 co-occurrences Mobility 27 co-occurrences Vehicles 14 co-occurrences Cars 7 co-occurrences

Where this tag comes from

Provider tag67
Api tag16

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.

MarketShare of the market's providers
Automotive and Mobility40%
FMCSA Registered Electronic Logging Devices34%

Cohort brief

Auto-generated

The 63 providers in the APIs.io catalog tagged Connected Vehicles, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
63
of 67 in the catalog
Mean Kin Score
20.3
-3.8 vs catalog 24.1
Mean Agent Readiness
9.4
-4.7 vs catalog 14.1
Spread
0–74.9
median 15.9 · σ 15.1
How the 63 split by band
Exemplar 1Strong 0Developing 5Thin 15Emerging 22Minimal 20
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Contract Governance 9 9.7 -0.7 63
Discoverability 57.7 59.1 -1.4 63
Operational Transparency 10.7 13.2 -2.5 63
Developer Ergonomics 21.4 24.5 -3.1 63
Contract Quality 14.3 18.6 -4.3 63
Access Clarity 22.3 30 -7.7 63

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.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 3% 18% -15
MCP server (first-party) 3% 16% -13
Agent Skills 0% 0% 0
OAuth scopes 13% 13% 0
Security 100% 99% +1
Arazzo workflows 0% 1% -1
Governance rules 25% 36% -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.

Top by Kin Score
  1. 1 Amazon IoT FleetWise 74.9
  2. 2 INRIX 51.8
  3. 3 Volteras 51.5
  4. 4 Hyundai 49.5
  5. 5 Mercedes-Benz Mercedes me 48.9
  6. 6 Sheeva 44.4
  7. 7 Telenav 39
  8. 8 Smartcar 37.6
  9. 9 High Mobility 35.3
  10. 10 Porsche 33.1
Top by Agent Readiness
  1. 1 Mercedes-Benz Mercedes me 43
  2. 2 Amazon IoT FleetWise 36.1
  3. 3 Fleetsu 36.1
  4. 4 Volteras 35.5
  5. 5 Otonomo 33.8
  6. 6 Sheeva 33.6
  7. 7 Hyundai 29.3
  8. 8 Federal Highway Administration 27.7
  9. 9 Ford 27.5
  10. 10 BMW ConnectedDrive 27.2
All 67 members of this roster resolve to a provider in the catalog; 63 carry a score (94%). The figures above describe the scored members only.
Coverage caveat. 59 of 63 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 14 November 2026, across 41591 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.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for tags

7 MCP tools reach this
  • find_tagsBrowse and filter every tag in the catalog.
  • get_cohortThis tag as a scored cohort — every provider carrying it, with scores.
  • cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.
  • cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This tag
curl "https://apis.io/api/v1/tags/connected-vehicles"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort (paid plan)
The distribution (Pro)

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.