Fleet Management
Providers using this tag (181)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 8 Solid coverage with minor gaps
Developing 28 Usable, with meaningful gaps to close
Thin 31 Limited public surface area
Emerging 49 Early or largely undocumented
Minimal 63 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (39)
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
Strong 2 Solid coverage with minor gaps
Developing 11 Usable, with meaningful gaps to close
Thin 9 Limited public surface area
Emerging 15 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (14)
These companies publish an API, specification or operation carrying “Fleet Management” 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
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 176 providers in the APIs.io catalog tagged Fleet Management, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 18.7 | 17.6 | +1.1 | 176 |
| Developer Ergonomics | 24 | 23.2 | +0.8 | 176 |
| Discoverability | 58.5 | 58.1 | +0.4 | 176 |
| Contract Governance | 6.7 | 6.3 | +0.4 | 176 |
| Access Clarity | 26.2 | 26.5 | -0.3 | 176 |
| Operational Transparency | 11.8 | 13.7 | -1.9 | 176 |
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) | 6% | 14% | -8 |
| MCP server (first-party) | 5% | 12% | -7 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 11% | 11% | 0 |
| Security | 99% | 98% | +1 |
| Arazzo workflows | 2% | 2% | 0 |
| Governance rules | 12% | 14% | -2 |
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 HERE 71.2
- 2 Particle 62.2
- 3 Nash 61.4
- 4 Onfleet 60.7
- 5 Viam 60.2
- 6 Foxglove Technologies 59.4
- 7 Amazon IoT Device Management 58.6
- 8 UVeye 57
- 9 Bringg 55
- 10 Track-POD 54.1
- 1 HERE 55.9
- 2 Decisiv 49
- 3 Onfleet 48.7
- 4 Lytx 48
- 5 Mercedes-Benz Mercedes me 43.3
- 6 Nash 42.1
- 7 OneRail 40.8
- 8 Avis Budget Group 39.7
- 9 Autopay 36.4
- 10 UVeye 36.2
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.