Fleet
Fleetfleet
Providers using this tag (59)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 1 Solid coverage with minor gaps
Developing 13 Usable, with meaningful gaps to close
Thin 19 Limited public surface area
Emerging 11 Early or largely undocumented
Minimal 15 Almost no public developer surface
APIs with this tag (34)
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 →
Strong 1 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 18 Limited public surface area
Emerging 7 Early or largely undocumented
Minimal 2 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 59 providers in the APIs.io catalog tagged Fleet, 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 | 28.7 | 17.5 | +11.2 | 59 |
| Developer Ergonomics | 24.8 | 17.9 | +6.9 | 59 |
| Discoverability | 65.2 | 60.4 | +4.8 | 59 |
| Operational Transparency | 15.6 | 11.3 | +4.3 | 59 |
| Access Clarity | 25.6 | 22.3 | +3.3 | 59 |
| Contract Governance | 8.8 | 6.4 | +2.4 | 59 |
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) | 24% | 16% | +8 |
| MCP server (first-party) | 7% | 7% | 0 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 14% | 9% | +5 |
| Security | 97% | 88% | +9 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 15% | 13% | +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 Fleet 55.1
- 2 Circuit 53.1
- 3 Nash 51.2
- 4 Google Maps Platform 49.8
- 5 INRIX 49.2
- 6 MileIQ 47.3
- 7 RunBuggy 47.3
- 8 Rollee 46.8
- 9 GenLogs 45.5
- 10 OpenRouteService 45.1
- 1 Kibana 41.7
- 2 MileIQ 39.8
- 3 RunBuggy 33.9
- 4 Nash 32.7
- 5 Rollee 32.2
- 6 Google Maps Platform 29.9
- 7 Calyptia 29.7
- 8 Airlabs 29.6
- 9 Circuit 29.1
- 10 FinditParts 28.6
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/fleet"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/fleet"
curl "https://apis.io/api/v1/cohorts/tag/fleet/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.