Shopify indexes at apis.io/providers/shopify/ with 213 APIs and 197 API specifications, a Kin Score of 68.7 (strong), and an Agent Readiness score of 53.8 in the agent-ready band.
It is the largest commerce surface on the network, and the gap between its composite and its agent readiness is where the interesting reading is.
What’s in the surface
The catalog resolves Shopify into five named collections, mirrored across Postman and open sets:
- Admin REST API — the operational surface: products, orders, inventory, fulfillment, customers
- Ajax API — the storefront-side surface for cart and checkout interactions in the browser
- Multipass API — single sign-on handoff from an external system into a Shopify storefront
- Webhooks API — the event surface
- Shopify API — the general umbrella entry
Five named boundaries across 213 APIs is a much coarser decomposition than Adyen’s twenty across 202. That is not sloppiness; it reflects a platform where the Admin API genuinely is one enormous surface.
What’s interesting
The Ajax and Multipass pair is the tell that Shopify is two products wearing one name. Ajax is a browser-facing, session-scoped, unauthenticated-ish surface for storefront interactivity. Admin REST is a server-to-server, token-scoped, permission-heavy operational surface. Almost no other provider in the catalog ships both a public client-side API and a privileged backend API under the same brand and expects developers to reason about which is which.
Multipass is the third leg: it exists so a merchant with an external identity system can drop a customer into a Shopify session without re-authentication. That is an API built for the migration path, not for the happy path — a sign of a platform absorbing customers who already have systems.
The Webhooks API appearing as a named, collected surface rather than an appendix matters. As covered in this week’s AsyncAPI piece, most providers document webhooks in prose. Shopify treats the event surface as a thing you can enumerate.
The agent-readiness gap
68.7 composite against 53.8 agent readiness is a wider spread than Adyen (77.8 / 73.1) or FactSet (73.5 / 76.0). Shopify is well described for humans and less consumable for agents.
The likely cause is exactly the Admin/Ajax split. An agent hitting this catalog has to know that two APIs with overlapping vocabulary — cart, product, customer — live at different trust boundaries with different auth models. That is legible in documentation and hard to infer from specification alone.
Takeaway
213 APIs, 197 specifications, and a strong-band score built on a genuinely difficult two-sided architecture: a storefront surface and an operations surface under one roof. The agent-readiness gap is the cost of that design, and it is the thing worth closing.
Browse it at apis.io/providers/shopify/.