emerging · 0.2 capabilitymarket actiondomain

Couriers

Score 20.3 / 100 29 providers +9 via APIs 21 APIs Search apis.io →
Business capabilities this tag reaches
Supply Chain Management 1
Variants seen in the corpus: CourierCouriers

Providers using this tag (29)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Strong 3 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 4 Early or largely undocumented
Minimal 9 Almost no public developer surface

APIs with this tag (19)

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 5 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 3 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Minimal 1 Almost no public developer surface

Companies reaching this through an API (9)

These companies publish an API, specification or operation carrying “Couriers” 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.

AfterShip Deliverect GoTo Group (Gojek + Tokopedia) Grab Grubhub Ory Parcel Perform Shiprocket TrackingMore

Score breakdown

Frequency
47.7
log-scaled weighted occurrences
Breadth
0.8
spread across providers
Quality lift
34.1
mean composite of providers using it
Cohesion
9.3
strength of nearest seed neighbor

Where this tag sits

Logistics broader Delivery broader

Related tags

Last Mile Delivery 26 co-occurrences Route Optimization 6 co-occurrences Delivery 20 co-occurrences Shipping 19 co-occurrences Fulfillment 12 co-occurrences Tracking 10 co-occurrences Menus 5 co-occurrences Food Delivery 7 co-occurrences

Where this tag comes from

Api tag19
Provider tag29
Openapi tag9
Openapi op tag13

Cohort brief

Auto-generated

The 26 providers in the APIs.io catalog tagged Couriers, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
26
of 29 in the catalog
Mean Kin Score
30.5
+7.6 vs catalog 22.9
Mean Agent Readiness
19.8
+7.9 vs catalog 11.9
Spread
0–61.4
median 33.3 · σ 18.5
How the 26 split by band
Exemplar 0Strong 3Developing 6Thin 7Emerging 4Minimal 6
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Contract Quality 33.5 17.6 +15.9 26
Developer Ergonomics 33.9 23.2 +10.7 26
Discoverability 63 58.1 +4.9 26
Operational Transparency 15.2 13.7 +1.5 26
Access Clarity 27.5 26.5 +1 26
Contract Governance 6.9 6.3 +0.6 26

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.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 12% 14% -2
MCP server (first-party) 12% 12% 0
Agent Skills 0% 0% 0
OAuth scopes 8% 11% -3
Security 100% 98% +2
Arazzo workflows 4% 2% +2
Governance rules 15% 14% +1

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.

Top by Kin Score
  1. 1 Nash 61.4
  2. 2 Onfleet 60.7
  3. 3 Uber Eats 54.3
  4. 4 Track-POD 54.1
  5. 5 Circuit 52.5
  6. 6 Komerce 45.9
  7. 7 Lalamove 43.3
  8. 8 FRAYT 42.4
  9. 9 Metrobi 41.8
  10. 10 Ship24 37.8
Top by Agent Readiness
  1. 1 Onfleet 48.7
  2. 2 Nash 42.1
  3. 3 Ship24 38.1
  4. 4 Barogo 37.9
  5. 5 Komerce 35
  6. 6 FRAYT 35
  7. 7 Uber Eats 33.3
  8. 8 Track-POD 31.9
  9. 9 Metrobi 30
  10. 10 Circuit 26.9
All 29 members of this roster resolve to a provider in the catalog; 26 carry a score (90%). The figures above describe the scored members only.
Coverage caveat. 21 of 26 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 5 October 2026, across 29093 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.

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.
All 92 tools →

Call it yourself

curl for this page
This tag
curl "https://apis.io/api/v1/tags/couriers"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort
curl "https://apis.io/api/v1/cohorts/tag/couriers"
The distribution (Pro)
curl "https://apis.io/api/v1/cohorts/tag/couriers/stats" \
  -H "X-API-Key: $APIS_IO_KEY"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.