Shipments
Shipmentsshipments
Providers using this tag (81)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Developing 26 Usable, with meaningful gaps to close
Thin 32 Limited public surface area
Emerging 15 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (87)
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 3 Complete, well-documented, and agent-ready
Strong 4 Solid coverage with minor gaps
Developing 25 Usable, with meaningful gaps to close
Thin 36 Limited public surface area
Emerging 18 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 81 providers in the APIs.io catalog tagged Shipments, 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 | 50.2 | 17.5 | +32.7 | 81 |
| Developer Ergonomics | 34.1 | 17.9 | +16.2 | 81 |
| Operational Transparency | 24.6 | 11.3 | +13.3 | 81 |
| Discoverability | 70.8 | 60.4 | +10.4 | 81 |
| Access Clarity | 31.5 | 22.3 | +9.2 | 81 |
| Contract Governance | 12.1 | 6.4 | +5.7 | 81 |
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) | 4% | 7% | -3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 25% | 9% | +16 |
| Security | 98% | 88% | +10 |
| Arazzo workflows | 6% | 2% | +4 |
| Governance rules | 35% | 13% | +22 |
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 Salla 72.5
- 2 Commerce Layer 72.4
- 3 Rye 67.5
- 4 Swell 65.8
- 5 Sendcloud 65.7
- 6 Resolve 58.1
- 7 MVMNT 57.3
- 8 OTO Global 52
- 9 PackageX 49.4
- 10 Shippo 49.1
- 1 Boxc 50.1
- 2 Xentral 46.4
- 3 Spree Commerce 45
- 4 Sendcloud 42.9
- 5 Resolve 42.2
- 6 Spree Commerce 41.4
- 7 Rye 39.7
- 8 MVMNT 38.3
- 9 99 Minutos 35.8
- 10 United States Steel 35.4
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/shipments"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/shipments"
curl "https://apis.io/api/v1/cohorts/tag/shipments/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.