Adyenadyen.com

ScoredJul 24, 2026, 08:58 AM

Adyen's API program leads in design quality — the contract is machine-readable, well-typed, and parseable — but two gaps put partner and agent adoption at risk. First, agents have no structured instructions or semantic metadata to orient themselves, meaning AI-powered integrations will misread or skip Adyen's docs entirely.

API DesignA clean, typed, well-governed API contract agents can reason about3 pass2 warn0 fail90A+

Signal	Points	Findings	Rationale
Auth declared & discoverablevia docs	25/25	Authentication required (global or on every operation). Investigated: docs 100%, spec 50%.	Agents can only authenticate when auth is declared, scoped, and discoverable.
Machine-readable, versioned contractvia spec	23.8/25	info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 95%, docs 90%.	A current OpenAPI version with a declared versioning scheme lets agents reason about the contract.
Schema coverage & depthvia sdk	15/25	0/1123 (0%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 60%, spec 55%.	Typed, complete request/response schemas are what make agent function-calling possible.
Security & governance hygienevia spec	15/15	No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.	No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel.
Example coveragevia spec	10/10	100% example coverage across params + responses. Investigated: spec 100%, docs 100%, sdk 100%.	Examples carry shape semantics schemas under-specify — for humans and agents alike.

Developer ExperienceThe context both developers and agents need to integrate fast — onboarding, code samples, complete descriptions and worked examples4 pass0 warn1 fail79B

Signal	Points	Findings	Rationale
Self-service developer portalvia docs	29/29	Signup page at https://www.adyen.com/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.	Self-serve key/account creation is the fast first call for partners, with no sales gate.
Code samples in docsvia docs	18/18	Code samples in 10 language(s) across docs (top: java, shell, php); 5/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%.	Multi-language samples shorten time-to-first-call.
Description completenessvia spec	15/15	56% description completeness. Investigated: spec 100%, sdk 100%.	Complete descriptions are the context humans and agents need to use endpoints.
Changelog publishedvia spec	13/13	changelog documented in the docs site at https://docs.adyen.com/release-notes. Investigated: spec 100%, docs 100%, sdk 100%.	A published changelog lets partners track changes without surprise.
Quickstart presentvia docs	0/25	No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.	A quickstart is the fastest path from landing page to first successful call.

Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs1 pass3 warn0 fail86A

Signal	Points	Findings	Rationale
Registry & SDK presencevia docs	28/28	Indexed on Context7 (websites/adyen, 101312 snippets). Investigated: docs 100%, cli 100%, sdk 67%.	Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look.
llms.txt present, valid & comprehensivevia docs	24.4/30	llms.txt is 404,939 characters (exceeds 100,000 threshold; will be truncated by most agents). Investigated: docs 81%, sdk 0%.	A valid, comprehensive llms.txt is the machine-readable entry point for agents.
Docs reachable, not hard auth-gatedvia docs	22.5/30	Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.	Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics.
Crawlable / AEOvia wellknown	9/12	Sitemap present (2506 entries) but carries no lastmod values. Investigated: wellknown 75%.	Bots allowed plus a fresh sitemap make docs findable by agent crawlers.

Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs2 pass1 warn2 fail73B

Signal	Points	Findings	Rationale
Machine-readable errors (RFC 9457)via docs	28/28	error codes documented in the docs site at https://docs.adyen.com/errors. Investigated: docs 100%, sdk 100%, spec 50%.	RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens.
Operation purpose clarityvia spec	25/25	100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.	Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice.
Agent-navigable, token-efficient docsvia docs	9.9/22	1 of 50 sampled pages appear to be client-side rendered SPA shells (__nuxt detected); agents using HTTP fetches will see no content. Investigated: docs 45%.	Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly.
Agent instructions file (AGENTS.md)via wellknown	0/10	No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.	An AGENTS.md gives coding agents explicit setup, auth, and usage instructions to interpret and operate the API — beyond llms.txt's link index.
Docs structured datavia docs	0/8	Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.	Structured data (JSON-LD/schema.org) on docs pages gives agents an unambiguous parse target and is what answer engines cite. Detected on the JS-rendered head (Firecrawl) for a bounded page budget, so JS-injected JSON-LD is now caught; pages we can't render are excluded rather than failed.
Description consistency across surfaces	—/7	Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.	Every surface tells the same story about what the product is.

Agent UsabilityAgents have the context to use your APIs reliably, not just find them2 pass2 warn1 fail74B

Signal	Points	Findings	Rationale
Idempotency documentedvia spec	27/27	idempotency documented in the docs site at https://docs.adyen.com/development-resources/api-idempotency. Investigated: spec 100%, docs 100%, sdk 0%.	Documented idempotency lets agents retry safely.
Sandbox separationvia spec	20/20	sandbox documented in the docs site at https://docs.adyen.com/development-resources/logs-resources/webhook-event-logs. Investigated: spec 100%, docs 100%, sdk 100%.	An isolated environment lets agents exercise destructive operations safely.
Pagination documented & consistentvia spec	16.5/22	2 list endpoint(s) exist but no pagination params found. Investigated: spec 75%, docs 75%.	Consistent, documented pagination lets agents traverse collections.
Runnable collection with test scriptsvia platform	4.5/9	No test scripts found in the workspace's collections. Investigated: platform 50%.	A public, maintained collection with assertions is runnable truth agents validate against.
Rate-limit signalingvia spec	0/22	No rate-limit response headers documented. Investigated: spec 0%, docs 0%.	Machine-readable rate-limit headers let agents throttle adaptively.

Resources Discovered

The public resources we found for Adyen — the evidence behind the score. All discovered from public sources; nothing here requires access to your systems.

Agent hints	Context7 (101,312)
APIs analyzed	10 — Management API (v3), Configuration API (v2), Legal Entity Management API (v4), Adyen Checkout API (v72), Capital API (v1), Transfers API (v4), FLOWS E-commerce Plugins, FLOWS AfP, Adyen Payout API (v68), Adyen Recurring API (v68)

Want to improve your results?