Carriers
Carrierscarriers
Providers using this tag (38)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 11 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 3 Almost no public developer surface
APIs with this tag (26)
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 8 Usable, with meaningful gaps to close
Thin 9 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 38 providers in the APIs.io catalog tagged Carriers, 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 | 41.7 | 17.5 | +24.2 | 38 |
| Access Clarity | 38.2 | 22.3 | +15.9 | 38 |
| Developer Ergonomics | 31.2 | 17.9 | +13.3 | 38 |
| Operational Transparency | 22.9 | 11.3 | +11.6 | 38 |
| Discoverability | 71 | 60.4 | +10.6 | 38 |
| Contract Governance | 10.2 | 6.4 | +3.8 | 38 |
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) | 26% | 16% | +10 |
| MCP server (first-party) | 8% | 7% | +1 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 11% | 9% | +2 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 24% | 13% | +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.
- 1 Mirakl 68.7
- 2 Sendcloud 65.7
- 3 AlphaLoops FMCSA Carrier Data API 59.8
- 4 MVMNT 57.3
- 5 OTO Global 52
- 6 Nayya 51.8
- 7 Ascend 50.3
- 8 ShipStation 47.9
- 9 Vooma 47.7
- 10 Narvar 46.3
- 1 Mirakl 59.7
- 2 Sendcloud 42.9
- 3 MVMNT 38.3
- 4 VAST Data 35.1
- 5 Ascend 32.5
- 6 VTEX 32.3
- 7 OTO Global 30.3
- 8 Noyo 28.6
- 9 AlphaLoops FMCSA Carrier Data API 27.4
- 10 Nayya 23.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/carriers"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/carriers"
curl "https://apis.io/api/v1/cohorts/tag/carriers/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.