# Adyen — API Agent Score

> Score: 80/100 (Grade: A) | Domain: adyen.com | Rubric: 1.0.0 | Checked: July 24, 2026

Adyen scored 80/100 (A), classified "ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/adyen)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 80/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 90/100 (A+)
- Developer Experience: 79/100 (B)
- Agent Discovery: 86/100 (A)
- Agent Understanding: 73/100 (B)
- Agent Usability: 74/100 (B)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: docs 100%, spec 50%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 95%, docs 90%.
- [warn] Schema coverage & depth — 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%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [pass] Example coverage — 100% example coverage across params + responses. Investigated: spec 100%, docs 100%, sdk 100%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.adyen.com/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Code samples in docs — 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%.
- [pass] Description completeness — 56% description completeness. Investigated: spec 100%, sdk 100%.
- [pass] Changelog published — changelog documented in the docs site at https://docs.adyen.com/release-notes. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/adyen, 101312 snippets). Investigated: docs 100%, cli 100%, sdk 67%.
- [warn] llms.txt present, valid & comprehensive — llms.txt is 404,939 characters (exceeds 100,000 threshold; will be truncated by most agents). Investigated: docs 81%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — Sitemap present (2506 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — error codes documented in the docs site at https://docs.adyen.com/errors. Investigated: docs 100%, sdk 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 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%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — idempotency documented in the docs site at https://docs.adyen.com/development-resources/api-idempotency. Investigated: spec 100%, docs 100%, sdk 0%.
- [pass] Sandbox separation — 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%.
- [warn] Pagination documented & consistent — 2 list endpoint(s) exist but no pagination params found. Investigated: spec 75%, docs 75%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.

## Executive Summary

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. Second, partners lack a guided quickstart and runnable examples, slowing the path from evaluation to a first successful call. Closing these two gaps should be the immediate priority to make Adyen's program fully self-serve for both human developers and their AI agents.