The State of Supply Chain APIs

About this paper

For years, API Evangelist has used the supply chain as the analogy for explaining API contracts to business people. Inventory your warehouses. Know what you take from your suppliers. Get contracts in place, because you would never run a physical business without them. This report turns the analogy around and scores the industry it was borrowed from, on exactly the thing it was borrowed to explain — and the industry that supplies the metaphor comes in below the catalog average on it.

Thirteen companies out of 1,124 publish idempotency. Every market in this series is bad at this. This is the one where being bad at it has a physical consequence: a retried request does not create a duplicate row, it dispatches a second truck and sends a second purchase order to a supplier who will ship against it.

The standards chapter lands in the same place from a different direction. Procurement is the largest segment here, and its integrations still run on two specifications from 1999 — cXML and SAP’s OCI punchout. Punchout is a round trip through a browser: a person clicks out to the supplier’s catalog, shops, and clicks back. It works, it is universally adopted, and an agent cannot punch out. The segment that spends the most money in this industry has standardized on the one integration pattern that structurally excludes the buyer everyone is now building for. Meanwhile 69.1% of the market has no fetchable contract at all, the only facet above the catalog average is the one measuring whether you can be found, and the sharpest predictor of a company’s score turns out to be how close it sits to a package somebody is waiting for. What the leaders publish, what nobody publishes, and what each of those artifacts is worth is laid out company by company.

What's inside

1. Executive summary — below the catalog average, and a ceiling of 68.3
2. How this cohort was built, and why it matters
3. The state of the market — distance from the parcel predicts the score
4. The resource taxonomy — what this industry actually models
5. The composite Kin Score, and why it's the foundation
6. Agent-readiness — the physical-consequence gap
7. The blueprint
8. The standards layer — the one that worked isn't an API
9. The regulatory layer — a wave of mandates, none of which asks for an API
10. Standards and artifacts for the agentic turn
11. Security, auth, scopes and compliance
12. Provider-by-provider intelligence
13. The investable thesis
14. Where this is going

What you get for $500.00