Freight
Providers using this tag (152)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 6 Solid coverage with minor gaps
Developing 23 Usable, with meaningful gaps to close
Thin 25 Limited public surface area
Emerging 53 Early or largely undocumented
Minimal 45 Almost no public developer surface
APIs with this tag (37)
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 4 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 23 Early or largely undocumented
Minimal 4 Almost no public developer surface
Companies reaching this through an API (4)
These companies publish an API, specification or operation carrying “Freight” 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
152 providers carry this tag directly, and 181 counting the 6 narrower tags below — 29 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 |
|---|---|
| Shipping and Logistics | 32% |
| Rail Sales and Distribution (OSDM, railway union, EU railway licences) | 24% |
Cohort brief
Auto-generatedThe 143 providers in the APIs.io catalog tagged Freight, 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 | 22.3 | 17.2 | +5.1 | 143 |
| Discoverability | 62.2 | 57.9 | +4.3 | 143 |
| Developer Ergonomics | 24.7 | 23.2 | +1.5 | 143 |
| Operational Transparency | 12.4 | 13 | -0.6 | 143 |
| Access Clarity | 22.7 | 23.9 | -1.2 | 143 |
| Contract Governance | 4.5 | 6.5 | -2 | 143 |
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) | 8% | 13% | -5 |
| MCP server (first-party) | 8% | 12% | -4 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 9% | 11% | -2 |
| Security | 96% | 98% | -2 |
| Arazzo workflows | 1% | 2% | -1 |
| Governance rules | 7% | 16% | -9 |
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 AlphaLoops FMCSA Carrier Data API 64
- 2 Rose Rocket 60.5
- 3 MVMNT 60.1
- 4 Augment 59.1
- 5 MyCarrier 57.8
- 6 C.H. Robinson 55.3
- 7 Kargo 54
- 8 FRAYT 49.7
- 9 Airspace Technologies 48.3
- 10 Emerge 48.3
- 1 Kargo 50.9
- 2 Loadsmart 49.2
- 3 Happyrobot 48.4
- 4 Freight Waves 48.1
- 5 Terminal49 45.8
- 6 Flexport 42.4
- 7 Rose Rocket 42
- 8 AlphaLoops FMCSA Carrier Data API 40
- 9 Greenbrier Companies 40
- 10 MyCarrier 39.3
Coverage caveat. 137 of 143 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.