Adyen sits at apis.io/providers/adyen/ with 202 APIs and 202 API specifications — a one-to-one ratio that is rarer than it sounds. Most payment providers in the catalog ship a documentation site and a handful of specs. Adyen ships a machine-readable definition for every single API it publishes.
That discipline shows up in the score. Adyen carries a Kin Score of 77.8 (exemplar) and an Agent Readiness score of 73.1, landing in the agent-native band. Among the payment providers we index, that combination — full spec coverage plus agent-native readiness — is the exception rather than the rule.
What’s in the surface
The catalog resolves Adyen’s surface through two parallel collection sets: 20 Postman collections and a matching set of open collections. The named boundaries are the interesting part, because they map cleanly onto how a payments business actually decomposes:
- Money movement — Checkout, Payments, Payouts, Transfers, Recurring, Stored Value
- Account and entity — Account, Legal Entity Management, Hosted Onboarding, Balance Control
- Physical presence — Terminal, POS Terminal Management, Test Cards
- Operations and risk — Disputes, Data Protection, BinLookup, Management, Configuration
- Event delivery — Authentication Webhooks, Configuration Webhooks
That last group matters more than its size suggests. Adyen publishes webhook surfaces as first-class, separately-defined APIs rather than burying callback payloads in prose. If you have ever tried to reconcile a payments integration against undocumented webhook shapes, you know what that is worth.
What’s interesting
The Legal Entity Management and Hosted Onboarding APIs are the tell that this is a platform, not a gateway. Those are the surfaces a marketplace uses to onboard its own sellers — KYC, entity structure, verification state. A provider only builds those when other companies are building payment businesses on top of it.
The split between Configuration and Management is the second tell. Configuration handles the merchant-facing setup; Management handles the account-structure operations above it. Keeping those separate is a control-plane decision, and it is why Adyen’s surface reads as coherent at 202 APIs when most providers get muddy past 50.
The Data Protection API is worth calling out on its own. A dedicated, specified API for data-subject operations is a compliance surface most providers handle through a support ticket.
Takeaway
Adyen is what full spec coverage looks like at scale: 202 APIs, 202 specifications, clean control-plane and data-plane separation, and webhooks treated as defined APIs rather than documentation footnotes. The 77.8 composite is earned on completeness, not marketing.
Browse the full surface at apis.io/providers/adyen/.