Supply Chain & Procurement indexes 1,218 providers publishing 4,880 APIs on the network — the software layer over sourcing, moving, tracking and paying for physical things.
The distinguishing feature of this vertical is how tightly the top of it clusters.
The cohort
| Provider | APIs | Band | Score |
|---|---|---|---|
| Hubble Network | 1 | exemplar | 72.9 |
| Boomi | 20 | exemplar | 72.4 |
| Commerce Layer | 148 | exemplar | 69.5 |
| Affinda | 16 | exemplar | 69.3 |
| Onfleet | 9 | exemplar | 68.3 |
| parcelLab | 8 | exemplar | 67.5 |
Six exemplars inside 5.4 points, with surface areas from 1 API to 148.
Hubble Network scores 72.9 on a single API. Commerce Layer scores 69.5 on 148. A 148-fold difference in surface area produces a 3.4-point difference in score, in favour of the smaller one.
If you want a single illustration that the Kin Score is not counting endpoints, this vertical is it.
What the flatness means
A tight cluster at the top usually indicates a mature category where the practices are settled and widely copied. Everyone in this band publishes an OpenAPI, documents auth clearly, signals rate limits, and keeps the contract callable. Nobody has a differentiating advantage in describing their API, because describing it well is table stakes.
That is a healthy sign, and it is not the norm. Telecommunications, covered earlier this week, runs a 35-point spread across its named cohort.
What has shifted
Integration platforms count as supply chain now. Boomi is an iPaaS, not a logistics company, and it sits second in the vertical. When most of the supply-chain problem is connecting systems that were never designed to talk, the integration layer becomes the category.
Document processing crept in. Affinda at 69.3 does document extraction — invoices, purchase orders, bills of lading. Procurement runs on documents that were designed to be read by humans, and turning them into structured data is now a supply-chain primitive rather than an OCR curiosity. It is also why Affinda appears in three verticals on the network.
Post-purchase became its own layer. parcelLab and Onfleet occupy the stretch between “order placed” and “package in hand” — tracking, delivery orchestration, customer communication. That stretch used to be a carrier’s problem and is now a software category with its own exemplars.
Where to start
Browse the vertical at apis.io/industries/supply-chain/. Related verticals — Mobility & Fleet, Robotics & Autonomous Systems, Climate & Sustainability, and Artificial Intelligence — carry genuine overlap, particularly around fleet telemetry and emissions reporting.
Takeaway
4,880 APIs across 1,218 providers, with the top six inside 5.4 points and the highest score belonging to a company that publishes exactly one API. Supply chain is one of the most evenly-practiced verticals on the network — and the clearest proof that the rubric rewards description over surface area.
Browse it at apis.io/industries/supply-chain/.