Freight
Providers using this tag (140)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 4 Solid coverage with minor gaps
Developing 27 Usable, with meaningful gaps to close
Thin 22 Limited public surface area
Emerging 52 Early or largely undocumented
Minimal 29 Almost no public developer surface
Unrated 5 Not yet scored
APIs with this tag (45)
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 11 Usable, with meaningful gaps to close
Thin 16 Limited public surface area
Emerging 16 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (5)
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
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 131 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 | 23.8 | 19.8 | +4 | 131 |
| Discoverability | 64.3 | 61.2 | +3.1 | 131 |
| Developer Ergonomics | 23.9 | 23.4 | +0.5 | 131 |
| Operational Transparency | 13.6 | 13.9 | -0.3 | 131 |
| Access Clarity | 26.1 | 26.5 | -0.4 | 131 |
| Contract Governance | 4.2 | 6.4 | -2.2 | 131 |
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) | 4% | 10% | -6 |
| MCP server (first-party) | 7% | 13% | -6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 8% | 11% | -3 |
| Security | 94% | 96% | -2 |
| Arazzo workflows | 1% | 2% | -1 |
| Governance rules | 4% | 14% | -10 |
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 68.2
- 2 MVMNT 56.9
- 3 Augment 56.7
- 4 Rose Rocket 56.7
- 5 MyCarrier 56.1
- 6 Kargo 51.4
- 7 BNSF 50.8
- 8 Airspace Technologies 48.4
- 9 Vooma 47.8
- 10 Loop 47.7
- 1 Happyrobot 51.2
- 2 Freight Waves 50.9
- 3 Kargo 49.8
- 4 Greenbrier Companies 46
- 5 Rose Rocket 44.4
- 6 MyCarrier 40.5
- 7 Loadsmart 39.6
- 8 MVMNT 38.3
- 9 BNSF 36.8
- 10 Qargo 36.3
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.